On Mon, 4 Jul 2016 21:43, w...@wolfsden.cz said:
> I did some thinking about this and I must admit that I don't see why the
> check is needing at all. In what situation relaxing the check would case
Such a directory may already exist with sufficient permission for any
user to create a socket. A
On , Werner Koch wrote:
> On Fri, 1 Jul 2016 01:58, w...@wolfsden.cz said:
>
> > the building/signing is done in fakeroot environment. Therefore the
> > socket path default to ~/.gnupg/S.gnu-agent. Because (at least it seems
> > to me) in fakeroot I am root (0) and therefore don't own /run/user/1
On Fri, 1 Jul 2016 01:58, w...@wolfsden.cz said:
> the building/signing is done in fakeroot environment. Therefore the
> socket path default to ~/.gnupg/S.gnu-agent. Because (at least it seems
> to me) in fakeroot I am root (0) and therefore don't own /run/user/1000
That is a very special case I
On Fri, Jul 01, 2016 at 01:58:20AM +0200, Wolf wrote:
> I'm in need of changing the path to the agent socket, but I cannot find
> a way to do so.
For GPG 1.x, you can change this by setting the GPG_AGENT_INFO
environment variable or by using the --gpg-agent-info flag. Both of
these are documented
Greetings,
I'm in need of changing the path to the agent socket, but I cannot find
a way to do so. My problem:
gpg-agent normally runs in /run/user/1000/gnupg/S.gnu-agent , which is
completely fine. However, when building packages (archlinux, makepkg),
the building/signing is done in fakeroot envi
