From: Dominique Martinet <email@example.com>
To: Karl Dahlke <firstname.lastname@example.org>
Subject: Re: [edbrowse-dev] Two Factor
Date: Sat, 21 Jul 2018 03:55:13 +0200 [thread overview]
Message-ID: <20180721015513.GA18666@nautica> (raw)
Karl Dahlke wrote on Fri, Jul 20, 2018:
> Chuck mentioned, off the group, that you can't access gmail through imap or pop3 unless you check a "allow less secure applications" button, and I have also experienced this.
> And when I wanted to tap into my daughter's gmail by email, she too had to enable this "less secure apps" feature.
> There are rumors that A) this option might go away, whence edbrowse access to gmail would go away, and
> B) it relates to two-factor.
> Without me doing a lot of research, can anyone explaain two-factor, and does curl support it, whence edbrowse could remain viable for gmail and other paranoid servers?
> I'm guessing it's out of our hands; either curl supports it or it does not; but that's a guess.
"two factor" in itself is easy and should work with edbrowse - the point
is that to log in to your gmail account on the web interface, you need
to enter your password, then the next page will ask you to enter the
text message you received (they also do voice call or "security keys"
like yubikey, the keys might not be trivial to get to work, but phone
call works) in the next prompt
For imap/smtp there apparently is an "application-specific" password
just like fastmail is doing, once you've logged in with 2-factor they'll
let you create new passwords on this page:
Now... while logging in with 2-factor enabled works, I couldn't get the
actual enabling from gmail, and similarily the app passwords page
doesn't load either. I just get a "Your browser is not supported
anymore. Please update to a more recent one."...
So, a bit of a mixed feeling there. Just like fastmail if you can get
someone to help or if you use a screen reader with firefox for initial
setup you should be ok afterwards, but edbrowse isn't going to be
independant anymore :/
next prev parent reply other threads:[~2018-07-21 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 1:28 Karl Dahlke
2018-07-21 1:55 ` Dominique Martinet [this message]
2018-07-21 3:24 ` Karl Dahlke
2018-07-21 3:38 ` Dominique Martinet
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).