public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Stankevitz <chrisstankevitz@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] How does ssh know to use "pinentry"?
Date: Sun, 6 Jul 2014 17:33:17 -0700	[thread overview]
Message-ID: <CAPi0pst=HYOc7_e-dPW-SDEkbs7SGP+mc9dO8=EHhkO21_DhEA@mail.gmail.com> (raw)
In-Reply-To: <201407062009.36913.michaelkintzios@gmail.com>

On Sun, Jul 6, 2014 at 12:09 PM, Mick <michaelkintzios@gmail.com> wrote:
> I think that the idea of keeping your passphrase in the clipboard is frowned
> upon for security reasons.  Not only because of any potential memory leaks,
> but because you may inadvertently paste it in GUI fields/areas you were not
> meant to

Mick,

Thank you.  I too have been concerned about this.  I've also been
concerned about "memory leaks".  FYI one cute feature of keepass is
that it clears the clipboard 20 seconds after you copy your password
to it.  Today (2014) I am choosing to use the clipboard/keepass to
manage complex/unique passwords.  Perhaps in the future (2015)
everybody will support something like the Yubikey HW OTP... in which
case it won't matter if everyone sees my password!

Chris


  reply	other threads:[~2014-07-07  0:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-06  1:41 [gentoo-user] How does ssh know to use "pinentry"? Chris Stankevitz
2014-07-06  2:57 ` Rich Freeman
2014-07-06  3:42   ` Chris Stankevitz
2014-07-06 10:25     ` Rich Freeman
2014-07-06 15:29       ` Chris Stankevitz
2014-07-06 19:09         ` Mick
2014-07-07  0:33           ` Chris Stankevitz [this message]
2014-07-06 20:32 ` Alan McKinnon
2014-07-07  0:40   ` Chris Stankevitz
2014-07-07  0:45     ` Rich Freeman
2014-07-07  1:18       ` Chris Stankevitz
2014-07-07  1:30         ` Rich Freeman
2014-07-07  8:05     ` Alan McKinnon

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='CAPi0pst=HYOc7_e-dPW-SDEkbs7SGP+mc9dO8=EHhkO21_DhEA@mail.gmail.com' \
    --to=chrisstankevitz@gmail.com \
    --cc=gentoo-user@lists.gentoo.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