[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Sks-devel] Cleaning up pools
From: |
kwadronaut |
Subject: |
[Sks-devel] Cleaning up pools |
Date: |
Thu, 10 Mar 2016 20:53:04 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
Hi,
wanted to use eu.pool.sks-keyservers.net, was sent to
2001:610:1108:5011::70, which seems to be 'mud.stack.nl', closest I
found on the status [1] page was 'stack.nl' which isn't in the pool.
Wanted to use ipv6.pool.sks-keyservers.net:
* ran into wrong cert for keys.void.gr (https)
* 2a01:4f8:192:806c::2 gave me some webpage asking money to send
encrypted messages or something
* 2a01:7e00::f03c:91ff:fe69:8da9 gave me the blog of someone who loves
good company from cats on keyboards
* 2a03:4000:6:202e::1 blog from someone who likes metal
* I *think* I hit a hickup at sks.fidocon.de, but seems fine now.
* 2a01:4f8:192:f5::3 HTTP/1.1 200 OK is all I got.
I'm guessing some dual stack hosts get checked only on IPv4 or they're
outdated or something? Who's usually taking care of this?
Kind regards,
kwadronaut
[1] https://sks-keyservers.net/status/ was
[2] http://ipv6.pool.sks-keyservers.net
signature.asc
Description: OpenPGP digital signature
- [Sks-devel] Cleaning up pools,
kwadronaut <=