[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24076: gnupg [-agent]: when signing [commits], it claims that there
|
From: |
Leo Famulari |
|
Subject: |
bug#24076: gnupg [-agent]: when signing [commits], it claims that there is no pinentry - but there is |
|
Date: |
Fri, 27 Mar 2020 16:02:26 -0400 |
On Thu, Mar 26, 2020 at 01:09:40PM +0100, Ludovic Courtès wrote:
> I (finally!) implemented this second option in commit
> c7af9d0b5ebaa1fdb08ff5d8a56004998bcd8103.
It still doesn't work for me :/
> I confirmed that it has the indented effect like this:
[...]
> where the strace log shows:
>
> 10 execve("/home/ludo/.gnupg/.guix-profile/bin/pinentry", ["pinentry"],
> 0x7f7aa80035e0 /* 14 vars */) = -1 ENOENT (No such file or directory)
This path includes the ~/.gnupg directory, so users need to do `export
GNUPGHOME=$HOME` for the lookup to work.
Is it okay to make GnuPG do that automatically when building the path in
get_default_pinentry_name()?