all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Allan Sandfeld Jensen <kde@carewolf.com>
To: Uwe Brauer <oub@mat.ucm.es>, emacs-devel <emacs-devel@gnu.org>
Cc: KDE PIM <kde-pim@kde.org>
Subject: Re: Kmail: Gmail (less secure apps) advice for GNU emacs developers.
Date: Mon, 10 Aug 2020 18:46:55 +0200	[thread overview]
Message-ID: <3493658.MHq7AAxBmi@twilight> (raw)
In-Reply-To: <87zh728oco.fsf@mat.ucm.es>

On Montag, 10. August 2020 18:20:07 CEST Uwe Brauer wrote:
> >>> "ASJ" == Allan Sandfeld Jensen <kde@carewolf.com> writes:
> > On Montag, 10. August 2020 09:12:12 CEST Martin Steigerwald wrote:
> >> Dear Uwe.
> >> 
> >> Uwe Brauer - 10.08.20, 09:02:15 CEST:
> >> > Hello
> >> > 
> >> > I am writing on behalf of the GNU emacs developers, Richard Stallman
> >> > in particular, asking for advice.
> >> > 
> >> > The issue concerns an announcement by the gmail developers to drop the
> >> > option to connect to their IMAP service via name and password, known
> >> > as less-secure-apps. The main email reader of GNU Emacs, called gnus
> >> > relies on this method. Someone on the GNU emacs developer list
> >> > suggested that kmail solved the problem and is able to connect to the
> >> > GMAIL imap server using their OAuth2 method.
> >> > 
> >> > So the question is addressed to the kmail developers, but I could not
> >> > find an active mailing list just for kmail, so if this list is not the
> >> > right place to ask the question, I would appreciate a link to the
> >> > relevant one.
> > 
> > I would recommend  anyone concerned with privacy rights to not use Gmail.
> > OAuth2 is just a way for Google to force people to use Google Chrome for
> > logging into google services. Google currently block all privacy secured
> > forks of Chromium from using their login services (supposedly because
> > some spammers used CEF to log onto GMail). You can make it work at the
> > moment by pretending to be Firefox (or by using Firefox), but I am
> > guessing it is just a matter of time before Google also block Firefox for
> > "security" reasons.
> 
> Ah, well, in a perfect world fine, but for example, my university
> switched to Gmail some years ago and will stay.
> 
> Since I don't want to use any other email reader than gnus, and a lot of
> people feel this way, any advice on a _technical solution_ is very much
> appreciated.
> 
Sure. Only mentioned it because you brought up RMS, I know he is pretty 
passionate about stuff like that.

Btw, you can see an overview in https://developers.google.com/identity/
protocols/oauth2 which also links bindings for a number of programing 
languages (though not for EMACS LISP). As far as I know KMail uses the 
libkgapi library, which is a KDE implementation of the whole google client 
api.  I don't think you don't need that much to just do the authentication 
though, but I am a browser guy, don't know how things looks from the app side.

'Allan







  reply	other threads:[~2020-08-10 16:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o8njdlvs.fsf@mat.ucm.es>
     [not found] ` <1897936.H7q943mS67@merkaba>
     [not found]   ` <5532801.MhkbZ0Pkbq@twilight>
2020-08-10 16:20     ` Kmail: Gmail (less secure apps) advice for GNU emacs developers Uwe Brauer
2020-08-10 16:46       ` Allan Sandfeld Jensen [this message]
2020-08-10 22:37       ` Stefan Monnier
2020-08-11 18:15         ` Uwe Brauer
2020-08-11 18:53           ` Stefan Monnier
2020-08-13  6:57             ` Uwe Brauer
2020-08-13  8:13               ` Robert Pluim
     [not found]     ` <21978174.sr7ieKrsik@beastie.bionicmutton.org>
2020-08-13  8:49       ` Uwe Brauer
2020-08-14  2:55         ` Richard Stallman
2020-08-14  4:25           ` 황병희
2020-08-14 10:16           ` Lars Ingebrigtsen
2020-08-15  4:40             ` Richard Stallman
2020-08-15  9:14               ` Martin Steigerwald
2020-08-15  9:20                 ` Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3493658.MHq7AAxBmi@twilight \
    --to=kde@carewolf.com \
    --cc=emacs-devel@gnu.org \
    --cc=kde-pim@kde.org \
    --cc=oub@mat.ucm.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.