|
From: | Scott Grayban |
Subject: | Re: [Sks-devel] IPv6 peering; keydumps annoyingly large |
Date: | Wed, 01 Jun 2011 02:18:24 -0700 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.23) Gecko/20090812 Lightning/0.9.4-Inverse Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 |
So just wait
and see until the last minute to clean it up when DB does become a
issue ? I don't like that idea... that means in some future the entire pool could be down if we take the "wait and see" approach. Why wait ? Why can't we run a script that will at least delete keys that have expired and revoked ? And then prevent such keys from being re-imported back into the db ? That would be the sensible thing to do now when we don't have any emergencies. Regards,
Scott Grayban /"\ \ / ASCII RIBBON X FIGHT BREAST CANCER / \ Johan van Selst said the following on 06/01/2011 12:42 AM: That said, there is indeed a lot of old stuff kept in the keydump. I wonder how useful it is to keep distributing all the old keys that have been revoked years ago. But as long as the keyservers manage to respond as fast as they do now, it's probably not worth the effort to clean this up. |
[Prev in Thread] | Current Thread | [Next in Thread] |