On 08/09/2012 10:46 AM, Werner Koch wrote: > On Wed, 8 Aug 2012 22:53, ds...@jabberwocky.com 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.
Hi, 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. [0] https://bitbucket.org/kristianf/sks-keyserver-patches/src/f1f6b537921c/Error_on_standalone_revokation_certificate [1] http://keys2.kfwebs.net:11371 -- ---------------------------- Kristian Fiskerstrand http://www.sumptuouscapital.com 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 http://www.amazon.com/dp/B006RSG1S4/ ---------------------------- Public PGP key 0xE3EDFAE3 at http://www.sumptuouscapital.com/pgp/
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
