Weird error during key refresh
Doug Barton
dougb at dougbarton.email
Wed Mar 25 20:42:35 CET 2015
On 3/25/15 11:12 AM, Kristian Fiskerstrand wrote:
> 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
>> END ) ->0 gpg: DBG: armor-keys-failed (KEY
>> 0xE3520E149D053533C33A67DB5CC686F11A1ABC84 BEGIN
> ...
>
>
>> I'm using the latest on Mac from homebrew:
>
>> gpg --version gpg (GnuPG) 2.0.27
>
> See http://lists.gnupg.org/pipermail/gnupg-devel/2015-February/029546.html
Thanks Kristian.
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 software you use. Thanks!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20150325/6f43979c/attachment-0001.sig>
More information about the Gnupg-users
mailing list