Please, if you consider the canary...
Don't centralize it.
SKS is supposed to be decentralized.
If the power to ban someone from the public pool or from peers, or
somewhere else, falls on a single person, then you are centralizing an
important part of SKS.
SKS is already broken due to the attacks..
Thanks!
Yeah, I know that is not a solution.
Looking at the code, it seems "reasonable" to add keys to the blacklist...
so I guess I will check everyday for problematic keys, and if I find any I
will be able to ban them from my SKS server (and I will notify the list
with the keys, as I guess I won
I am receiving lots of request for key: 0x69D2EAD9
http://pgp.librelabucm.org/pks/lookup?search=0x69D2EAD9&fingerprint=on&op=index
And, as it turns out, when I have an error and I clic on the browser on
"View page source", I can see part of the key text is:
Do not use SKS keyserver sites (no val
I'm not an active member of this community.
I represent a group of people. We recently set up a SKS Keyserver as a way
to contribute to the community.
We have had a lot of problems, but we don't have the knowledge and the
experience to contribute to the code or to submit pull requests.
I like the
