On 07/15/2014 12:30 AM, Ludwig Hügelschäfer wrote: > On 14.07.14 23:16, Otto de Voogd wrote: >> On 07/12/2014 03:52 PM, Alexander Buchner wrote: > > (...) > >>> After you revoke your key with the revocation certificate you >>> have to upload the revoked key to the server again, I think. > >> I did that a long time ago, here you can see that it was revoked: >> https://gpg.mozilla.org/pks/lookup?search=otto+de+voogd&op=vindex > >> Maybe it didn't propagate to other keyservers, > > It should have. It runs the newest SKS version and one of it's peers > is a member of pool.sks-keyservers.net. See: > https://gpg.mozilla.org/pks/lookup?op=stats > >> I'll try to do that manually to see if it makes a difference. > > No need, a quick check reveals that 0x2BF81C27 is revoked now on > several keyservers of pool.sks-keyservers.net. So it did propagate out > of gpg.mozilla.org to other keyservers.
I just manually uploaded it to pgp.mit.edu and pgp.surfnet.nl, both didn't show it as revoked before I uploaded. However it doesn't make a difference to my problem. On Enigmail I searched on gpg.mozilla.org anyway (where it was revoked) and it always shows the revoked key first. If I search for ruben.garske (who's revoked keys were posted as an example in a previous post), Enigmail also shows his revoked keys when searching on a keyserver. ps. The revoked key was not created by me, but by someone trying to be "helpful". Otto _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
