>> 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 >> http://jeromebaum.com/jerome.asc), importing it, and then refreshing >> it? Does it throw any errors? > > gpg: requesting key C58C753A from http server jeromebaum.com > gpg: key C58C753A: "Jerome Baum <[email protected]>" not changed > gpg: key 215236DA: "Jerome Baum" not changed > gpg: Total number processed: 2 > gpg: unchanged: 2
Okay, so Jeremy should definitely upload an armored version of the key. That is the cause of the problem. Whether it is intentional or not, and whether this applies to other implementations, I cannot say. But I know for sure that if it should work for gpg, he has to upload an armored version. -- Jerome Baum tel +49-1578-8434336 email [email protected] web www.jeromebaum.com -- PGP: A0E4 B2D4 94E6 20EE 85BA E45B 63E4 2BD8 C58C 753A PGP: 2C23 EBFF DF1A 840D 2351 F5F5 F25B A03F 2152 36DA _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
