From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Bob Newell <bobnewell@bobnewell.net>, ding@gnus.org
Subject: Re: oauth to be required for gmail
Date: Tue, 17 Dec 2019 18:11:33 +0100 [thread overview]
Message-ID: <877e2uvpve.fsf@gnus.org> (raw)
In-Reply-To: <m2sgljtm3a.fsf@gmail.com> (Robert Pluim's message of "Tue, 17 Dec 2019 09:03:53 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> I think the canonical package for doing this is
> <https://github.com/ccrusius/auth-source-xoauth2>, although I haven't
> tried it yet.
It's comically convoluted to use oauth for open source software:
https://github.com/ccrusius/auth-source-xoauth2/blob/8cef77b0d390f8a45e7690eaf8772173e1995a9b/auth-source-xoauth2.el#L79
Here's a recipe for Mutt, which one Hackernews described as "you just
have to run a script":
https://luxing.im/mutt-integration-with-gmail-using-oauth/
Now, what closed source software does is do all the first steps for you:
Register an app on Google, get a secret key etc, so all the user has to
do it go through a web-based login thing.
I don't think this is much of an option for Gnus? Gnus Inc registering
an app that's allowed to access Gmail accounts? I'd have to go through
a security audit process (typically costing $50K, if I understand
correctly) and, still, it's pretty much impossible as the secret key
would have to be distributed some way, wouldn't it? Or... is that a
solved problem?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-12-17 17:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 19:48 Bob Newell
2019-12-16 20:49 ` Florian Weimer
2019-12-16 22:45 ` Bob Newell
2019-12-17 0:17 ` Jude DaShiell
2019-12-17 5:40 ` Pankaj Jangid
2019-12-18 5:52 ` 황병희
2019-12-21 10:26 ` Florian Weimer
2019-12-21 10:50 ` 황병희
2019-12-16 22:46 ` Bob Newell
2019-12-17 8:03 ` Robert Pluim
2019-12-17 17:11 ` Lars Ingebrigtsen [this message]
2019-12-17 17:41 ` David Engster
2019-12-18 5:31 ` Bob Newell
2019-12-23 10:50 ` Florian Weimer
2019-12-18 7:07 ` David Engster
2019-12-23 10:59 ` Florian Weimer
2019-12-23 12:09 ` David Engster
2019-12-24 5:16 ` Bob Newell
2019-12-24 16:53 ` Lars Ingebrigtsen
2019-12-26 7:03 ` Steinar Bang
2019-12-28 20:43 ` Jouni K. Seppänen
2019-12-26 10:04 ` David Engster
2020-01-07 17:07 ` Jorge A. Alfaro-Murillo
2020-01-07 18:44 ` Eric Abrahamsen
2020-01-07 19:52 ` David Engster
2020-01-08 3:24 ` Pankaj Jangid
2020-01-08 3:28 ` Pankaj Jangid
2019-12-17 17:33 ` David Engster
2020-08-03 3:19 ` just ping (Was: Re: oauth to be required for gmail) 황병희
2020-08-06 12:35 ` just ping 황병희
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=877e2uvpve.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=bobnewell@bobnewell.net \
--cc=ding@gnus.org \
--cc=rpluim@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).