From: Richard Stallman <rms@gnu.org>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: 41386@debbugs.gnu.org
Subject: bug#41386: 28.0.50; Gnus nnimap OAuth 2.0 support
Date: Thu, 23 Jul 2020 00:07:24 -0400 [thread overview]
Message-ID: <E1jySVw-0002Qc-Qv@fencepost.gnu.org> (raw)
In-Reply-To: <m31rnamz1t.fsf@fitzsim.org> (message from Thomas Fitzsimmons on Sat, 23 May 2020 11:49:34 -0400)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
I got this information from someone who knows
who says it is all from published information.
Does this enable us to cope with Google's planned changes?
======================================================================
GNUS could follow the same process of the the maintainers of KMail to
get approved:
https://www.reddit.com/r/kde/comments/gi5bol/kmailkontact_oauth_signin_with_gmail_enabled_again/
This had nothing to do with shutting off access to free MUAs. It's a
matter of hardening the security of GMail accounts and having all
3rd-party clients (free and non-free alike) publish a privacy policy
where they describe their usage of the GMail APIs, as described in this
thread:
https://www.reddit.com/r/kde/comments/cj7t7c/kmail_doesnt_let_me_sign_in_with_gmail/evchyih/
In particular:
Google is not concerned with the legal "significance", they just care
about the part about what features of their API we use and how, which
seems to be incomplete, judging from the last email I got from them
just yesterday, which is my responsibility to update, as I'm more or
less the Google integration maintainer in PIM, since I wrote most of
the stuff (silly me!) :D
The implementation details for XOAUTH2 are here, along with sample code
and links to the relevant RFCs:
https://developers.google.com/gmail/imap/xoauth2-protocol
--
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2020-07-23 4:07 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 2:05 bug#41386: 28.0.50; Gnus nnimap OAuth 2.0 support Thomas Fitzsimmons
2020-05-19 12:46 ` Lars Ingebrigtsen
2020-05-19 12:58 ` Noam Postavsky
2020-05-19 13:12 ` Lars Ingebrigtsen
2020-05-20 4:02 ` Richard Stallman
2020-05-19 15:37 ` Thomas Fitzsimmons
2020-05-19 16:00 ` David Engster
2020-05-19 16:12 ` Lars Ingebrigtsen
2020-05-20 3:59 ` Richard Stallman
2020-05-20 13:32 ` Stefan Kangas
2020-05-20 16:16 ` Thomas Fitzsimmons
2020-05-21 3:45 ` Richard Stallman
2020-07-19 1:29 ` Lars Ingebrigtsen
2020-07-20 2:40 ` Richard Stallman
2020-08-10 16:13 ` Simon Leinen
2020-08-11 3:28 ` Richard Stallman
2020-08-11 20:56 ` Simon Leinen
2020-05-22 3:07 ` Richard Stallman
2020-05-22 8:28 ` David Engster
2020-05-20 3:53 ` Richard Stallman
2020-05-20 14:05 ` Thomas Fitzsimmons
2020-05-21 3:47 ` Richard Stallman
2020-05-21 14:30 ` Thomas Fitzsimmons
2020-05-22 3:09 ` Richard Stallman
2020-05-23 15:49 ` Thomas Fitzsimmons
2020-05-24 3:54 ` Richard Stallman
2020-05-24 14:35 ` Thomas Fitzsimmons
2020-05-25 4:38 ` Richard Stallman
2020-07-23 4:07 ` Richard Stallman [this message]
2020-07-23 13:22 ` Lars Ingebrigtsen
2020-07-24 3:33 ` Richard Stallman
2020-07-24 14:54 ` Lars Ingebrigtsen
2020-07-25 3:49 ` Richard Stallman
2020-07-27 21:55 ` Lars Ingebrigtsen
2020-07-30 0:39 ` 황병희
2020-07-30 3:04 ` Richard Stallman
2022-10-29 15:36 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-30 12:22 ` Deus Max
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1jySVw-0002Qc-Qv@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=41386@debbugs.gnu.org \
--cc=fitzsim@fitzsim.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).