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: Sat, 5 Jul 2014 20:42:49 -0700	[thread overview]
Message-ID: <CAPi0psvjOboJjta39+Hb9W7nOaD=trx2gXrdAQTBDW0nrbsk8w@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_kQJjqj38cdDH9ZXBO5xMe8RBs3gryjP=UOH=jTJDc4=w@mail.gmail.com>

On Sat, Jul 5, 2014 at 7:57 PM, Rich Freeman <rich0@gentoo.org> wrote:
> In any case, I suspect that gpg-agent is actually serving passwords to
> openssh, so the file you want is ~/.gnupg/gpg-agent.conf - it probably
> contains the line "pinentry-program /usr/bin/pinentry".  If you trust
> all your X clients you can set the option no-grab in the file which
> will probably allow copy/paste/etc to work with the entry window.

Rich,

Thank you, I will give that a shot.  FYI I discovered:

declare -x GPG_AGENT_INFO="/tmp/gpg-2uVMfE/S.gpg-agent:26095:1"

When I unset this env variable, ssh stopped trying to use pinentry to
acquire my passphrase.  However, I still do not understand how that
variable got set or how/why ssh behaves differently when it is set.

Chris


  reply	other threads:[~2014-07-06  3:42 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 [this message]
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
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='CAPi0psvjOboJjta39+Hb9W7nOaD=trx2gXrdAQTBDW0nrbsk8w@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