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:40:43 -0700 [thread overview]
Message-ID: <CAPi0pstXXEORk=tv9Zqri3kEiC6W9py0cMZuTYPJfpd-Ab9qDw@mail.gmail.com> (raw)
In-Reply-To: <53B9B279.2070509@gmail.com>
On Sun, Jul 6, 2014 at 1:32 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> Why not do the obvious thing instead?
>
> Run keychain and have it unlock your keys *once* when the workstation
> boots up. ssh then always uses that key as it is unlocked.
Alan,
Thank you. FYI, I do not have a problem typing my password 100 times
per day. The only problem I have with "pinentry" is that it doesn't
let me paste. Does keychain allow me to paste? If so, I'll consider
it. However, now that I have killed pinentry from my system I am
happily pasting my passphrase into the ssh console.
On another note, from my OP, I am still curious how the ssh software
knows to use /usr/bin/pinentry to fetch my passphrase. In a follow-up
post, I discovered that this mechanism only works if an environment
variable called GPG_AGENT_INFO is set. I doubt the ssh source code
contains the string "/usr/bin/pinentry" or "GPG_AGENT_INFO".
Chris
next prev parent reply other threads:[~2014-07-07 0:40 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
2014-07-06 20:32 ` Alan McKinnon
2014-07-07 0:40 ` Chris Stankevitz [this message]
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='CAPi0pstXXEORk=tv9Zqri3kEiC6W9py0cMZuTYPJfpd-Ab9qDw@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