Bug 1415538 - gpg-agent no longer works with shared NFS home directory
Summary: gpg-agent no longer works with shared NFS home directory
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnupg2
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-23 01:22 UTC by Andrew J. Schorr
Modified: 2017-01-23 09:56 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 09:56:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrew J. Schorr 2017-01-23 01:22:50 UTC
Description of problem:
In RHEL 7.3, gpg-agent creates a unix socket in $HOME/.gnupg/S.gpg-agent.
This results in collisions when $HOME is on an NFS-mounted home directory shared between multiple machines. This bug was reported upstream here:
https://bugs.g10code.com/gnupg/issue1752
and was fixed in subsequent releases of gnupg2.

Version-Release number of selected component (if applicable):
gnupg2-2.0.22-4.el7.x86_64


How reproducible:
Run "gpg-agent --daemon" and observe that the socket is in a shared NFS location. Older versions of gnupg put this socket under /tmp.

Steps to Reproduce:
1. gpg-agent --daemon
2.
3.

Actual results:
GPG_AGENT_INFO=$HOME/.gnupg/S.gpg-agent

Expected results:
Some way to avoid collisions.

Additional info:

Comment 1 Andrew J. Schorr 2017-01-23 01:32:55 UTC
Oops, I now see that the --no-use-standard-socket option solves this problem. Sorry for the bother. Unfortunately, I can't seem to close this bug myself...


Note You need to log in before you can comment on or make changes to this bug.