Hi Haw, On Sun, Jul 15, 2018 at 9:17 AM Haw Loeung <haw.loe...@canonical.com> 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 containing only key material, SBINDs > > and revocations (no id packets, no third party sigs) is the absolute > > maximum functionality we can hope to sustain in the long term. And > > for this to be bulletproof, all such material must be > > cryptographically verified (otherwise people could just create > > “random” key material containing arbitrary data). > > If it helps others, we have a patched SKS packaged to exclude the bad > key (one of them at least)[1]. A couple of others in my team did all > the work so I can't comment on the details. >
Could you provide the patch on bitbucket[1], I'm not sure if Kristian will accpet it or not. But I'd like to see it in patch form and include it in my own build. [1] https://bitbucket.org/skskeyserver/sks-keyserver/ -- Regards, Shengjing Zhu _______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
