On 7/10/2017 1:21 PM, Achim Gratz wrote: > jeff writes: >> jeff_xeon:/cygdrive/u:503: gpg2 --output fred.good --decrypt fred.gpg >> gpg: encrypted with 4096-bit RSA key, ID A3791E7DD935A424, created >> 2013-03-21 >> "Jeff Deifik <j...@jeffunit.com>" >> gpg: public key decryption failed: No such device or address >> gpg: decryption failed: No secret key >> >> I have uninstalled the standalone version of gnupg2 before I did this. >> It seems most likely that the version of gpg2 being invoked is a cygwin >> version. > > It fails to find your private key, so it is quite obviously not in a > place where gpg2 expects to find it.
I have my keys stored in $HOME/.gnupg which is where gnupg v1 expects them. Using gnupg2: gpg2 --export -a "Jeff Deifik" -----BEGIN PGP PUBLIC KEY BLOCK----- mQGiBEt8tlURBACkuHVVgDFnNK9JeY9JbaoBwyaiCebmUPbp66YIMjRi4LKHOsYG zVR0XUlYfB9M7S6td8HEOhakjpjXFdSzBqWzFEhBKhnl4r2lPU7WxH/+f8Tmyuuo ... gpg2 --export-secret-key -a "Jeff Deifik" gpg: key XXX: error receiving key from agent: No such device or address - skipped gpg: key FXXX: error receiving key from agent: No such device or address - skipped gpg: key XXX: error receiving key from agent: No such device or address - skipped gpg: key XXX: error receiving key from agent: No such device or address - skipped gpg: WARNING: nothing exported (I replaced the hex with XXX) I suspect there is a problem with the pinentry and/or agent. The pinentry thing seems to be a new thing with gnupg2. jeff -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
