On 2009-03-24 at 11:57 -0400, Daniel Kahn Gillmor wrote:
> Are these scripts published? (this is out of curiosity more than
> anything else)
Well, since it's just curiosity, I'll pipe in with something roughly
equivalent to the IP generation side:
http://sks.spodhuis.org/sks-peers/ip-valid
No
On 2009-03-24 at 11:12 -0400, Daniel Kahn Gillmor wrote:
> On 03/23/2009 07:05 PM, John Clizbe wrote:
> > Folks may be holding back from upgrading because they don't want to
> > upgrade their Berkeley DB version to 4.6.
>
> That does sound unpleasant. Who on the list has done this process? Has
>
On Mon, Mar 23, 2009 at 04:02:22PM -0400, David Shaw wrote:
> The odd thing here is that version has been broken for at least 2
> years, as I reported the problem in 2006. Did nobody else notice, or
> are there still a bunch of 1.0.9 SKSes out there?
I went from 1.0.9 -> 1.1.0, skipping 1.0.10.
On 03/24/2009 11:39 AM, Kristian Fiskerstrand wrote:
> But I'm always open for suggestions. As for now I already have blacklist
> on aliases/ips, but there is an RFE to block certain versions?
I'd like to propose blacklisting SKS version 1.0.10 from the main pool,
because of that version's misbeha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Kahn Gillmor wrote, On 03/23/2009 09:17 PM:
> On 03/23/2009 04:02 PM, David Shaw wrote:
>> On Sun, Mar 22, 2009 at 07:41:50PM -0400, Daniel Kahn Gillmor wrote:
>>> has any thought been
>>> given to requiring members of the keyserver pools to n
On 03/23/2009 07:05 PM, John Clizbe wrote:
> David Shaw wrote:
>> None that I know of. Eventually, such a thing will be necessary, but
>> it would have to be done via whoever controls the particular keyserver
>> round-robin.
>
> Or convince the keyserver operators running 1.0.10 to upgrade to 1.1
> It'll be nice to have a new release with recon doing regular reloads of
> membership. Then I can stop bugging folks to `touch membership`.
> keys.niif.hu
Done.
Regards
Gabor
___
Sks-devel mailing list
Sks-devel@nongnu.org
http://lists.nongnu.org/m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If your server is peered with keyserver.gingerbear.net:
Time-Warner did it again, around 01:20AM (US/Central) on Monday.
Everything should now be squared away. I checked several DNS servers and
they are showing the new address for keyserver.gingerbea
