From: Dominique Martinet <firstname.lastname@example.org>
To: Karl Dahlke <email@example.com>
Subject: Re: [edbrowse-dev] two factor, per device
Date: Sat, 21 Jul 2018 13:20:43 +0200 [thread overview]
Message-ID: <20180721112043.GA13812@nautica> (raw)
Karl Dahlke wrote on Sat, Jul 21, 2018:
> You get an imap password, somehow, and you claim it is per device? How
> is that possible?
No, well, yes - the way they want it to work is you generate as many
password as "apps" you want to use gmail with, so it's your "job" to
generate one per device.
More to the point, when you generate such a password it's given once and
then there's no way to view it again, so unless you go find it in your
.ebrc or somewhere you wrote it down it's probably easier for most
people to make another one up when they need a second one.
I doubt they'll forbid you to log in if you use the same one for
multiple programs/devices though.
> If password foobar gets you in to imap from mutt on your phone, it
> will get you in on edbrowse on your desktop.
Right, it's just a matter of user perspective. But my arguments from the
previous mail stand: if you were a good boy and used a different
password for each device, and one of them gets stolen, it's easy to
revoke that one.
If on the other hand you want to use the same generated password for
everything then it's the same as before, like you say.
next prev parent reply other threads:[~2018-07-21 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 9:44 Karl Dahlke
2018-07-21 11:20 ` Dominique Martinet [this message]
2018-07-21 12:17 ` Karl Dahlke
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).