From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] Two Factor
Date: Fri, 20 Jul 2018 23:24:06 -0400 [thread overview]
Message-ID: <20180620232406.eklhad@comcast.net> (raw)
In-Reply-To: <20180721015513.GA18666@nautica>
[-- Attachment #1: Type: text/plain, Size: 268 bytes --]
Ok, so somehow you've made a separate imap password, how the hell is that any more secure than the password you use for your account?
Either way an email client is sending over a password. It's just a password.
This looks like bogus bull shit to me.
Karl Dahlke
next prev parent reply other threads:[~2018-07-21 3:24 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
2018-07-21 3:24 ` Karl Dahlke [this message]
2018-07-21 3:38 ` Dominique Martinet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180620232406.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@edbrowse.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.
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).