Re: [Sks-devel] 0xd5920e937cc1e39b shows signatures with 0xca57ad7c continuing?

[David Benfell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/27/2012 05:17 PM, John Marshall wrote:
> 
> What warrant do we have for applying any filtering at the servers
> at all? If the "problem" is one robo-signer, wouldn't it make sense
> to talk to its minders?
> 
I finally followed the URL posted at the beginning of this thread:
http://keyserver.kjsl.org:11371/pks/lookup?search=0xd5920e937cc1e39b&op=vindex

It looks like this key gets re-signed every two weeks or so.

I notice in a couple places in this thread, people are wondering why.
Count me in with that group. Perhaps I'm just lacking imagination, but
John Marshall's advice here seems appropriate.

But then I also have to ask, how big a problem is this really? Is this
a common practice? How much space is this kind of thing taking out of
all the certificates (many ancient, many--including some of
mine--never properly revoked) we're currently lugging around?

- -- 
David Benfell
address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPwtVJAAoJELT202JKF+xpWCAQAIWtJHcTZpiYtRUw2UgC7ypH
Q/6fGOl06uhIJHzy7j8kHU7TFqEY/Jrnxa/pRsqtDGh+lu0/Y7TYg0EKCF+wUOR5
LlfGzyV6EHnff4XQd3dw48fORl9QZmPhoV3LwusoEfI8DUddk10+X/ZkgY7293hR
k6+XPjHshowJSqYZoVJGm+lwHI8um31UgdmKsI+tpMSCDtZcO3u+90YrTNdECZZ5
f6cJuOXZ+VKaKneYMMohFwd2ySTus1cqg4LUnTTnJfLzwLF7s1QnrtscNzTAM+V9
Oez1mpOuM3kH9DHW+cA6bSjGYEKzaDQXQd65cPcJKgT/+wulS+ZeKrHgdF99/dWF
gHiFPU10mM6fEGsLR4FQ5z2uBLS4IyCpT3byzz5h9f/B1LgRvdcPF1e0jc639ZLB
uRUcPbk/fgHSg3bOe1cMweZzvJE+k1YT+sAaM98csG7oNtGHfHvn6zgWwUL8u2fI
rTfAtqbb3MhFZjEXwdEqHcEGemNxfNamNsjwRdJmpwSgAgVh8q+VpkrMWPLgu6du
+J995qBFkGhwefcqAG+Nh+QRdjfs1ST+z0e09kyDfO+gOYWCFBEmD/6HfU2nK+MV
pm998AsQSICqpBHkJRcjIBJsTBgyvyTBPpYmyfIfarmgynIsaU3ghGRL2YN5ZsJN
vaXC4586NoIFMwjjUGtI
=isNN
-----END PGP SIGNATURE-----