Re: [Sks-devel] GDPR (equine corpse)

[Stefan Claas]

brent s. wrote:

> On 8/17/19 11:46 AM, Stefan Claas wrote:

> > The other points you have mentioned, like the signer cannot upload a key,
> > well that's true but I wonder how you guys like then to solve the problem
> > with uploading flooded key material to the key servers. I think you can
> > not have all options, but I am all ears.
> > 
> > Regards
> > Stefan
> > 
> 
> Hence the original discussion, yes. The only way to do it that I can
> think if is one (or both) of:
> 
> - blacklisting keys, which makes the server peering *incredibly* more
> complex (and, it can be made the case for, impossible) - if you were
> following this mailing list for a while, you'd have seen us discuss this
> very issue many, many times. For something like 8 months now. Check the
> archives.

Will do.

> - heuristic analysis, which is always going to be faulty to some degree
> and just ends up as a cat-and-mouse game.

Interesting! If understood correctly the advantage then would be no changes
in the SKS code and simply using a front-end key parser, with a defined rule
set, right?

Regards
Stefan 

-- 
box: 4a64758de9e8ceded2c481ee526440687fe2f3a828e3a813f87753ad30847b56
GPG: C93E252DFB3B4DB7EAEB846AD8D464B35E12AB77 (avail. on Hagrid, WKD)