Error message when refreshing keys

Jerry gnupg.user at
Sun Jun 19 23:27:46 CEST 2011

On Sun, 19 Jun 2011 22:50:22 +0200
Jerome Baum articulated:

> >> Could you post the output of "gpg --export D02B0179 | gpg
> >> --list-packets" ?
> >>
> > I hope this is what you wanted. The output seems rather long.
> >
> > :public key packet:
> (snip)
> Yes, that's the right output. As I get the same issues, apparently gpg
> (v1 here) doesn't like non-armored keys via HTTP. RFC 4880 doesn't
> discuss the issue, but in any case Jeremy would be well-advised to
> upload an armored version of his key. That'll resolve the problem.
> Just as a reference, can you try pulling my key (from
>, importing it, and then refreshing
> it? Does it throw any errors?

gpg: requesting key C58C753A from http server
gpg: key C58C753A: "Jerome Baum <jerome at>" not changed
gpg: key 215236DA: "Jerome Baum" not changed
gpg: Total number processed: 2
gpg:              unchanged: 2

Jerry ✌
GNUPG.user at
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.

More information about the Gnupg-users mailing list