[MacPorts] #50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[MacPorts] #50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO

MacPorts
#50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO
---------------------------+--------------------------------
 Reporter:  neil_mayhew@…  |      Owner:  macports-tickets@…
     Type:  defect         |     Status:  new
 Priority:  Normal         |  Milestone:
Component:  ports          |    Version:  2.3.4
 Keywords:  gnupg2         |       Port:
---------------------------+--------------------------------
 I have a running `gpg-agent`:

 {{{
 $ ps x | grep gpg
 44980   ??  Ss     0:00.09 gpg-agent --daemon --write-env-file
 }}}

 The environment is set correctly:

 {{{
 $ env | grep GPG
 GPG_AGENT_INFO=/tmp/gpg-qIkaon/S.gpg-agent:44980:1
 }}}

 The socket exists:

 {{{
 $ ls -l ${GPG_AGENT_INFO%%:*}
 srwxr-xr-x  1 mayhewn  wheel  0 Jan  5 16:11 /tmp/gpg-qIkaon/S.gpg-agent
 }}}

 The environment file also exists:

 {{{
 $ cat ~/.gpg-agent-info
 GPG_AGENT_INFO=/tmp/gpg-qIkaon/S.gpg-agent:44980:1
 }}}

 However, when I run `gpg2` it can't find the agent:

 {{{
 $ touch foo
 $ gpg2 --sign foo

 You need a passphrase to unlock the secret key for
 user: "Neil Mayhew <...>"
 1024-bit DSA key, ID XXXXXXXX, created 2005-11-21

 gpg: can't connect to the agent - trying fall back
 }}}

 At this point, it manages to find the agent that was started by `launchd`,
 and a pinentry dialog pops up on the screen. This is unfortunate, since
 I'm using `ssh` and not sitting in front of the computer.

 I've tried using `dtruss -f`, and as far as I can tell `gpg2` and its
 children never stat or open the socket, and in fact never refer to it at
 all. They do, however, try to stat `~/.gnupg/S.gpg-agent` which normally
 doesn't exist, but even if I symlink the actual socket to this location,
 `gpg2` still can't find the agent.

--
Ticket URL: <https://trac.macports.org/ticket/50238>
MacPorts <https://www.macports.org/>
Ports system for OS X
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO

MacPorts
#50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO
----------------------------+---------------------
  Reporter:  neil_mayhew@…  |      Owner:  ionic@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.3.4
Resolution:                 |   Keywords:
      Port:  gnupg2         |
----------------------------+---------------------
Changes (by mf2k@…):

 * keywords:  gnupg2 =>
 * owner:  macports-tickets@… => ionic@…
 * port:   => gnupg2


Comment:

 In the future, please fill in the Port field and Cc the port maintainers
 ({{{port info --maintainers gnupg2}}}), if any.

--
Ticket URL: <https://trac.macports.org/ticket/50238#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X
_______________________________________________
macports-tickets mailing list
[hidden email]
https://lists.macosforge.org/mailman/listinfo/macports-tickets
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO

MacPorts
In reply to this post by MacPorts
#50238: gpg2 can't connect to the agent specified in GPG_AGENT_INFO
----------------------------+--------------------
  Reporter:  neil_mayhew@…  |      Owner:  Ionic
      Type:  defect         |     Status:  closed
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.3.4
Resolution:  worksforme     |   Keywords:
      Port:  gnupg2         |
----------------------------+--------------------
Changes (by roederja):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 In recent versions the agent starts automatically and doesn't need to be
 started by launchd anymore. So I assume your issue is resolved. Please re-
 open if not.

--
Ticket URL: <https://trac.macports.org/ticket/50238#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS