Hello, Vincent Cozzo wrote: > So, the first `agent_genkey` call works just fine (`err` code is > zero), but the subsequent agent_genkey returns `16777220`... [...] > So there is very possibly a problem with how I installed the new > binary. In full disclosure, I tried to "compile" the GnuPG binaries > without "installing" them, which might be the root cause of my errors.
I think that this is the case. In this case, as the function name suggests (agent_genkey), it is actually the gpg-agent which uses libgcrypt for key generation. If your gpg-agent is using the old version of libgcrypt, it fails. For testing, you can invoke a shell under gpg-agent by doing like: $ export GNUPGHOME=$(mktemp -d) $ LD_LIBARRY_PATH=<the-path-to-new-libgcrypt> gpg-agent --daemon /bin/bash [...] $ gpg ... $ exit Then, followng gpg invocations will connect to the agent which runs with the LD_LIBARRY_PATH specified. -- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-users
