Malformed Revokation Certificate?

Kristian Fiskerstrand kristian.fiskerstrand at
Thu Aug 9 23:07:58 CEST 2012

On 08/09/2012 10:46 AM, Werner Koch wrote:
> On Wed,  8 Aug 2012 22:53, dshaw at said:
>> If you want the keyservers to accept them, you need to talk to the
>> keyserver folks.  As this is an extension, they aren't required to
>> support it.
> Actually it is  good thing that they don’t accept them.  This avoids
> accidental uploads of the revocation certificate.
> We may want to display a warning if a user tries to upload a bare
> revocation certificate.


I've added a patch to my local patch queue[0] that add the warning "Add
failed: This is a stand-alone revocation certificate. Revocation
certificates should be imported to a public key before being published
to a keyserver ". The patch is applied to [1] for testing.

If it works as expected I'll set up a pull request into SKS Trunk.


Kristian Fiskerstrand
Twitter: @krifisk
Nosce te ipsum!
Know thyself!
This email was digitally signed using the OpenPGP
standard. If you want to read more about this
The book: Sending Emails - The Safe Way: An
introduction to OpenPGP security is now
available in both Amazon Kindle and Paperback
format at
Public PGP key 0xE3EDFAE3 at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20120809/381079f2/attachment.pgp>

More information about the Gnupg-users mailing list