Re: [Sks-devel] Key updates not propagating

[Hendrik Visage]

Yes,

 With the poison key issues that started last year, I have neglected the  cryptokeys.(co|org|net).za instances ;(

I fear I need to reload DBs on them, which unfortunately takes human time and effort, and then the single threaded nature of the SKS software

then fails on the next problem key, pull down the service (running on not the fastest VPS instances), and we have again a “weakly connected” case… it’s not the connectedness that is the issue(s), but the SKS software that fails and needs lots of TLC to get going again.

No offense taken, though duly noted I need to schedule time and effort on them again ;(

On 19 Jan. 2019, at 00:55 , Andrew Gallagher <address@hidden> wrote:

On 18 Jan 2019, at 17:47, Alain Wolf <address@hidden> wrote:

While sks1.cryptokeys.org.za is listing pgpkeys.urown.net as peer. It
is not cross-peered back by pgpkeys.urown.net.

Of course. Please don’t take anything I say as an accusation against either yourself or any other particular keyserver operator. These things happen (I was a less than exemplary pool member for several years!). The problem is not that there are keyservers that don’t gossip efficiently with peers, but that weakly connected keyservers can remain in the pool regardless.

A

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

---
Hendrik Visage

HeViS.Co Systems Pty Ltd
T/A Envisage Systems / Envisage Cloud Solutions
+27-84-612-5345 or +27-21-945-1192
address@hidden

signature.asc
Description: Message signed with OpenPGP