From: Karl Dahlke <email@example.com>
Subject: [edbrowse-dev] two factor, per device
Date: Sat, 21 Jul 2018 05:44:46 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
I'm sorry but I still don't understand it. Maybe I am a little dense.
You get an imap password, somehow, and you claim it is per device? How is that possible?
I've seen the pop3 and imap protocols at the lowest levels.
Hell I implemented them, before curl.
There is no field for "here's the device I'm on".
There's a log in and a password, that's it!
In theory the server could glom onto your ip address, but that is not an indicator of your device; it is where you are, which public wifi etc.
There are no cookies, nothing else that would indicate device.
So again, it seems to me it's just another password, that you use for imap, and a) I don't see that it adds much security, maybe a little,
and b) I definitely don't understand how it can be per device or per application.
If password foobar gets you in to imap from mutt on your phone, it will get you in on edbrowse on your desktop.
next reply other threads:[~2018-07-21 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 9:44 Karl Dahlke [this message]
2018-07-21 11:20 ` Dominique Martinet
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).