From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Richard Stallman <rms@gnu.org>
Cc: 41386@debbugs.gnu.org
Subject: bug#41386: 28.0.50; Gnus nnimap OAuth 2.0 support
Date: Thu, 21 May 2020 10:30:55 -0400 [thread overview]
Message-ID: <m3k115mkbk.fsf@fitzsim.org> (raw)
In-Reply-To: <E1jbcAz-0007XM-DE@fencepost.gnu.org> (Richard Stallman's message of "Wed, 20 May 2020 23:47:21 -0400")
Richard Stallman <rms@gnu.org> writes:
> [[[ 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. ]]]
>
> > Two factor authentication can be implemented by a service without
> > requiring OAuth 2.0, and vice versa.
>
> Ok. But my concern is not about OAuth in particular. The crucial
> question is, will Gmail in the future permit access from the Free World
> in any manner whatsoever?
>
> In other words, if we look at all the ways of logging in that Gmail
> permits in the future, will _any_ of them be usable in the Free World?
>
> Can you help me find the answer? If it is no, we had better put all our
> strength into changing that answer.
OK, I'll try to help, but I don't know what Google or Gmail will do in
the future, in general, obviously. I wanted this bug report to be
specifically about Gnus, IMAP and OAuth 2.0 (which the responding
experts correctly inferred was more precisely about Gnus, IMAP and
Gmail's proposed OAuth 2.0 policy change).
Your question reminded me that Gmail provides "basic HTML view" which
does not require any Javascript whatsoever for sign-in or for the main
interface, and thus is fully useable with Emacs Web Wowser (eww). For
me that isn't a viable alternative to Gnus, so it's tangential to this
bug report, but that access method is feasible using entirely Free
Software. Hopefully that answers your question.
Will "basic HTML view" still be available after Gmail starts mandating
OAuth 2.0 for IMAP access (assuming they do, sometime in the future)? I
suspect it will, but I don't know.
Thomas
next prev parent reply other threads:[~2020-05-21 14:30 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 [this message]
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
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=m3k115mkbk.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=41386@debbugs.gnu.org \
--cc=rms@gnu.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).