Hi,

It appears that several of the current active hosts in the hkps pool are not signed using the sks CA which is causing issues when trying to publish keys to it.

46.19.90.99 (StartCom)
80.241.60.3 (StartCom)
94.142.241.93 (GlobNix)
66.16.6.88 (CACert)
131.155.141.70 (CACert)
198.82.169.69 (self-signed)
2001:610:1108:5011::70 (CACert)
2a02:898:31:0:48:4558:73:6b73 (GlobNix)
2001:470:7:6ad::2 (CACert)
2001:470:e232:132:209:6bff:feb7:e69 (CACert)
2001:468:c80:210f:0:162:701c:c917 (self-signed)
2001:67c:2050:1000::3:4 (StartCom)

As you can see almost all of the pool are using certificates that are not signed by the SKS CA certificate.


Thanks,

Daniel.
(pgpkeys.co.uk / pgpkeys.eu)

_______________________________________________
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/sks-devel

Reply via email to