To reproduce using version 2.0.26 (on Windows):
- Set your keyserver to something invalid (ie. put the following line in your
gpg.conf, without any other keyserver entries:
keyserver hkp://invalid.gnupg.net
- Try to retrieve the key 82058954 (from john doe) from the server: gpg --recv-keys 82058954
This should report that no key has been found. What it *should* report is that
there was a communication problem with the servier.
- Revert to a vali keyserver destination in your gpg.conf
keyserver hkp://keys.gnupg.net
- Perform the recv operation again, it should successfully load the key gpg --recv-keys 82058954
- Reset your server to an invali value and perform the following operation: gpg --send-keys 82058954
The application will with the message that it is sending the key to
invalid.gnupg.net, wnen in fact it is not