edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] two factor, per device
Date: Sat, 21 Jul 2018 08:17:03 -0400	[thread overview]
Message-ID: <20180621081703.eklhad@comcast.net> (raw)
In-Reply-To: <20180721112043.GA13812@nautica>

[-- Attachment #1: Type: text/plain, Size: 341 bytes --]

> if you were a good boy and used a different password for each device,

Well if I have to jump through a lot of hoops, maybe ask for sighted help, to generate that password, then no, I'm not gonna be a good boy and go through that process for each device;
I'm gonna do it once and then use that same password everywhere.

Karl Dahlke

      reply	other threads:[~2018-07-21 12:17 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
2018-07-21 12:17   ` Karl Dahlke [this message]

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=20180621081703.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).