When GNUPGHOME env variable is set gpg does not work.

[ariellourenco]

Hi there,

I am using the GPG shipped with Git for Windows to sign my commits. However, I would like to move the .gnupg from my $HOME directory but if I set the GNUPGHOME env variable to a different location the signing command stops work and returns the following error message:

$ git commit -m "Test commit signing"
error: gpg failed to sign the data:
gpg: error running '/usr/bin/gpg-agent': exit status 2
gpg: failed to start gpg-agent '/usr/bin/gpg-agent': General error
gpg: can't connect to the gpg-agent: General error
gpg: keydb_search failed: No agent running
gpg: skipped "3ADF5C8C64710AY3": No agent running
[GNUPG:] INV_SGNR 0 3ADF5C8C64710AY3
[GNUPG:] FAILURE sign 33554509
gpg: signing failed: No agent running

fatal: failed to write commit object

I am setting the GNUPGHOME on .bash_profile as follow:

case "$APPDATA" in *\\*) APPDATA="$(cygpath -m "$APPDATA")";; esac
test -d "$XDG_CONFIG_HOME" || test ! -d "$APPDATA" || {
  XDG_CONFIG_HOME="$APPDATA"
  export XDG_CONFIG_HOME
}

# Sets GnuPG configuration files directory.
# https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration.html
export GNUPGHOME="$XDG_CONFIG_HOME/gnupg"

Any idea about what is going on?

[becm]

@ariellourenco the gpg binary seems to not support mixed path notation and requires the pure unix version.

… APPDATA=$(cygpath -u "$APPDATA")";; …

[ariellourenco]

Hi @becm,

Thank you for your reply. I think there is something else that prevents gpg from getting access to this folder. I have updated my configuration to use a pure Unix path notation however the error still the same:

$ gpgconf -L
sysconfdir:/etc/gnupg
bindir:/usr/bin
libexecdir:/usr/lib/gnupg
libdir:/usr/lib/gnupg
datadir:/usr/share/gnupg
localedir:/usr/share/locale
socketdir:/c/Users/ariellourenco/AppData/Roaming/gnupg
dirmngr-socket:/c/Users/ariellourenco/AppData/Roaming/gnupg/S.dirmngr
keyboxd-socket:/c/Users/ariellourenco/AppData/Roaming/gnupg/S.keyboxd
agent-ssh-socket:/c/Users/ariellourenco/AppData/Roaming/gnupg/S.gpg-agent.ssh
agent-extra-socket:/c/Users/ariellourenco/AppData/Roaming/gnupg/S.gpg-agent.extra
agent-browser-socket:/c/Users/ariellourenco/AppData/Roaming/gnupg/S.gpg-agent.browser
agent-socket:/c/Users/ariellourenco/AppData/Roaming/gnupg/S.gpg-agent
homedir:/c/Users/ariellourenco/AppData/Roaming/gnupg

$ git commit -m "sign commit on Windows"
error: gpg failed to sign the data:
gpg: error running '/usr/bin/gpg-agent': exit status 2
gpg: failed to start gpg-agent '/usr/bin/gpg-agent': General error
gpg: can't connect to the gpg-agent: General error
gpg: keydb_search failed: No agent running
gpg: skipped "3ADF5C8C64710AE3": No agent running
[GNUPG:] INV_SGNR 0 3ADF5C8C64710AE3
[GNUPG:] FAILURE sign 33554509
gpg: signing failed: No agent running

fatal: failed to write commit object

[dscho]

Since you set APPDATA to the output of cygpath -m, I bet it starts with a drive letter and a colon, and for that reason so does XDG_CONFIG_HOME and therefore also GNUPGHOME. Further, I bet if you set GNUPGHOME="$(cygpath -au "$XDG_CONFIG_HOME/gnupg")" it will start to work.

[dscho]

Also, don't try to debug the complex process tree via git commit. Try to do something simple like signing a string or something like that, using pure gpg (something like echo 123 | gpg --encrypt --armor -r <your-email-address> | tee encrypted-file.txt, then gpg --decrypt <encrypted-file.txt should launch the GPG agent and should allow you to use --verbose and/or --debug=<level> to investigate in a much more effective way).

[ariellourenco]

Hi @dscho and @becm,

Thank you for your replies and the support on this issue. Both of you guys were right and the path was wrong.

[becm]

@ariellourenco seems I fumbled the executable name in my first reply (fixed or posterity).
Glad you got it to work despite my sloppiness. ☺