Page MenuHome GnuPG
Create Task
Maniphest T989

sockets in home directory
Closed, ResolvedPublic
Actions

Description

gnupg default settings use the sockets in $HOME/.gnupg. Shared filesystems like
afs do not allow use of that, as well as named pipes. kde for example uses
/tmp/ksocket-username, gnome uses /tmp as well. Is it possible for the default
settings to use something similar? It is however possible to configure gnupg to
use sockets on local filesystem, but it is quite a lot of work per user and not
really feasible for large systems.

Event Timeline

andrej added a project: Bug Report.Jan 17 2009, 9:57 AM
andrej added a subscriber: andrej.
• werner added a subscriber: • werner.Jan 19 2009, 8:51 AM

What sockets do you mean? The default is to use socket below /tmp.

andrej added a comment.Jan 19 2009, 9:05 AM

If I start the gpg-agent from scratch with gnupg-2.0.10, I get the following
(gentoo):

af@f9pc136 ~ $ rm -rf .gnupg/
af@f9pc136 ~ $ gpg-agent
gpg-agent[31150]: directory `/afs/f9.ijs.si/home/af/.gnupg' created
gpg-agent[31150]: directory `/afs/f9.ijs.si/home/af/.gnupg/private-keys-v1.d'
created
gpg-agent[31150]: can't connect to
`/afs/f9.ijs.si/home/af/.gnupg/S.gpg-agent':No such file or directory
gpg-agent: no gpg-agent running in this session

• werner added a comment.Jan 28 2009, 1:59 PM

The error message merely indicates that no agent is running. It mentions a
socket below HOME because there is no GPG_AGENT_INFO envvar set with information
on the socket used. gpg falls back to that standard socket if GPG_AGENT_INFO is
not available.

neal closed this task as Resolved.Nov 3 2015, 11:55 PM
neal claimed this task.

This support request appears to have been resolved. Closing.