Hi Doug,
it's an error very similar to the one I've got using --refresh-keys with a
specified -keyserver [name].
Did you try to specify the keyserver's name and enable both --use-temp-files and
--keep-temp-files? The output of the temp files retain the communication data of
the refreshing action
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/25/2015 08:28 AM, Doug Barton wrote:
gpg --refresh-keys dougbarton.us
...
gpg: DBG: armor-keys-failed (KEY
0x9DD1E44C8660ADA6580F83B6C886A42BD5B2F0FB BEGIN ) -0 gpg: DBG:
armor-keys-failed (KEY 0x9DD1E44C8660ADA6580F83B6C886A42BD5B2F0FB
On 25.03.15 21:42, Doug Barton wrote:
Doug
--
I am conducting an experiment in the efficacy of PGP/MIME signatures.
This message should be signed. If it is not, or the signature does not
validate, please let me know how you received this message (direct, or
to a list) and the mail
