Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Hi Tom, I spend the night on the keydump - keys.flanga.io is now also running with hockeypuck (I did not test anything to be honest though ;)). I'll see if it runs stable (not sure if it is pool compatible) - version is 1.1.6. A short write-up for installing this thing is already done - I can

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Just saying... ...the person who created that key has finally started a long overdue process. They are likely reading this as well, so: Thank you. This could otherwise have ended much worse. To the other readers, but only to those of them who do not agree with the following sentences: Please

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Hi Haw, On Sun, Jul 15, 2018 at 9:17 AM Haw Loeung wrote: > > On Fri, Jul 13, 2018 at 07:53:01PM +0100, Andrew Gallagher wrote: > > I am still willing to help with possible upgrades and/or > > replacements for the SKS network. At this point I have come to > > believe that a minimal network

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

> Does anyone in the pool run hockeypuck? How compatible is its recon with others running sks-keyserver? Yes, here is one: http://keyserver.snt.utwente.nl (see https://sks-keyservers.net/status/ and http://keyserver.snt.utwente.nl:11371/pks/lookup?op=stats ) However, it was kicked out of the

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

On Fri, Jul 13, 2018 at 07:53:01PM +0100, Andrew Gallagher wrote: > I am still willing to help with possible upgrades and/or > replacements for the SKS network. At this point I have come to > believe that a minimal network containing only key material, SBINDs > and revocations (no id packets, no

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Does anyone in the pool run hockeypuck? How compatible is its recon with others running sks-keyserver? Daniel On Sat, Jul 14, 2018 at 5:52 AM, Human at FlowCrypt wrote: > One more apology - there does seem to be recent activity when you look at > the repo owner: https://github.com/hockeypuck >

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

One more apology - there does seem to be recent activity when you look at the repo owner: https://github.com/hockeypuck Though not loads of activity, still more code contributions than the SKS repo: https://bitbucket.org/skskeyserver/sks-keyserver/commits/all It may be worth considering. On

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Sorry, I hadn't noticed that you linked specifically the conflux (reconciliation code). That is indeed a good start if someone wanted to take the time to understand it. On Sat, Jul 14, 2018, 20:16 Human at FlowCrypt wrote: > Hockeypuck has not had any commits in years, if I saw correctly. > >

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Hockeypuck has not had any commits in years, if I saw correctly. It cannot process some of the keys (maybe for a good reason, but it will clog the recon mechanism nevertheless, I suppose). I think it was a great effort, but apparently not maintained. If the recon process could be updated with

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Though I am not sure, https://github.com/hockeypuck/conflux may be worth a look. If somebody has a short How-To for installing hockeypuck (and importing a keydump..), I am happy to test if it is more stable than sks :) Best regards, Moritz Am 14.07.18 um 02:50 schrieb Tom at FlowCrypt: > I

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

I would have loved to write an alternative SKS implementation that addresses the issues we were seeing recently. However, this: - Set Reconciliation with Nearly Optimal Communication Complexity - Practical Set Reconciliation

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

> On 13 Jul 2018, at 22:43, Moritz Wirth wrote: > > FWIW, has anybody even started working on a fix for any of the bugs? There has been a fair bit of discussion, but no consensus has been reached, apart from a general agreement that major changes to the recon model will be required, and that

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

FWIW, has anybody even started working on a fix for any of the bugs? Am 13.07.18 um 21:52 schrieb Robert J. Hansen: >> Sad but not surprised. Thanks for all your time and effort. It has been much >> appreciated. > Yes. > >> I am reluctant to declare defeat, but this calls for a tactical

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

> Sad but not surprised. Thanks for all your time and effort. It has been much > appreciated. Yes. > I am reluctant to declare defeat, but this calls for a tactical retreat and > regroup. Yes. There's a certain dark lesson to be learned here. The keyserver network was designed in the

Re: [Sks-devel] withdrawal of service: sks.spodhuis.org

Phil, Sad but not surprised. Thanks for all your time and effort. It has been much appreciated. For myself, whippet.andrewg.com has been broken for several weeks now and I’m not sure I have the heart to go to the effort of restoring it only for it to be clobbered again. I am reluctant to

[Sks-devel] withdrawal of service: sks.spodhuis.org

Folks, with immediate effect, I am withdrawing sks.spodhuis.org from service and it will not be returning in its current form. I am about to disable the DNS in spodhuis.org, while leaving the SKS service itself running, so that clients using pools will not be adversely impacted. I'll give it a