[Gpg4win-users-en] 2.0.2rc1 - Can't start agent when I use --homedir

[Matthew Orlando]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
 
I had to do two things to solve this:

1: use absolute paths for the homedir. E.g.:
    gpg --homedir "C:\users\me\test\gpg" --gen-key

2: kill any existing GnuPG agents with task manager, and then start one
manually using the same homedir:
    gpg-agent --homedir="C:\users\me\test\gpg" --daemon

After you're done, kill the agent you started.

Cheers,

Cogwheel

> I'm not sure if I'm missing a configuration issue, but...
>
> I wanted to make a dummy keyring for testing.  I created a test
> directory "test/gpg".  From the 'test' directory, I ran "gpg --homedir
> gpg --gen-key."  When it's time to set the passphrase, I get the
> following error:
>
> Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
> You need a Passphrase to protect your secret key.
>
> gpg: can't connect to the agent: Invalid value passed to IPC
> gpg: problem with the agent: No agent running
> gpg: can't connect to the agent: Invalid value passed to IPC
> gpg: problem with the agent: No agent running
> gpg: Key generation canceled.
>
> To rule a few things out, I ran "gpg --gen-key" without a homedir.  I
> was able to create a key.  Pinentry started up as expected.  I also
> tried copying the entire contents of my real gpg directory "Application
> Data/gnupg" into the test directory "gpg".  I still get the same error.
>
> Do I need to do something to configure this?  Or is it a bug?  Or a
feature?
>
> -Grant
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQEcBAEBCAAGBQJX8EU2AAoJEPro35Ne53Y9OJ4H/jxdbGk+Atb7HjIvriBrvozz
QKjxASQQeM4Uflf711i0ofR6vmhuUwVuLO8VuR31AF7OjdZWCv95zA+GBzbgGIyf
PeEBNyQllY9J5Oc0OFJSlTDmncyjhPdALGe9MivE2BQuN0RGHhIeW2SVe/Y9O7SL
oztLGbn4JF6fXKP1en79wfzYIPjKV/CtSBmjTNg9Kh74pXxV6JQ7nKAieyUqzMQC
MvNQv6NVXVgpPxxx3Dj2+bOs3/nXuHoJgTDrjbKFkdNqZDtr5EIuowftrtZPnAvL
tPS2PbgoYPu7W+UzXL8jWzW2cDDFV2F3JkUFXomWBLxNgmQ7G7rHkwxYSDn2Az4=
=m71W
-----END PGP SIGNATURE-----