[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sks-devel] Withdrawal of Service -

From: Moritz Wirth
Subject: Re: [Sks-devel] Withdrawal of Service -
Date: Fri, 16 Nov 2018 01:38:28 +0100

Also some personal words - this is not meant to judge or criticize
anyone but rather to express my own feelings and opinions about SKS
within the last months.

- The fact that most (all?) vulnerabilities inside SKS are known for a
very long time and have not been fixed is deeply concerning - for
example I really don't see any reason how a reasonable size limit of a
single key would have censored anybody - but it would have prevented
many keyservers from constantly becoming unresponsive as well as high
traffic and resource consumption (we spent 2.4 TB on peering over the
last 2 months). Just ignoring it because it still works somehow is
frustrating at best and desasterours at worst.
- GDPR is not really a new thing and it was already in place 2 years
before it actually became relevant. Instead of waiting until someone
uploads data relevant enough to get it removeed by a court, a simple
remove list would not have been a big deal.
- got kicked out of the pool around 3-4 months ago - the
initial response to this was about some missing Header files - my
request to check again was simply not answered. As I found out, it was
excluded due to "unrecognized server version" - it is true that we were
running our own implementation for a while - however this was not the
case for Kicking it out is one thing (and comitting that
change 2 months later so I was finally able to see why), not responding
instead of resolving the issue is another - but no offense (we all
forget things :) ).
- Though SKS keyservers are not meant to be trusted, people still trust
in the reliability of it as a service. Therefore, it should be operated
and handled in that way - a roundrobin that is checked and updated every
hour when all 5 keyservers can be killed within seconds is not something
that I would consider reliable.

Best Regards,

Am 16.11.18 um 00:59 schrieb Mike:
> Moritz you did the right thing!
> A lot of people consider the GDPR crappy only because it inconveniences them.
> This law is actually extremely useful and greatly overdue.
> On Fri, 16 Nov 2018 00:50:31 +0100
> Moritz Wirth <address@hidden> wrote:
>> I asked to be allowed to share some more details, however the request
>> was to remove/prevent indexing of 2 keys stored on our keyservers -
>> including copies of ID's to verify the request as required by the
>> european data protection law. Since it is not possible to prevent the
>> indexing of data, I think the only possible way to handle this request
>> is to shut them down. I don't see a reason to fight this - it is the
>> right of someone to get his/her data removed so we are required to do
>> this regardless of how crappy that law might be. If someone decides to
>> ignore it, it's up on them.
>> Am 16.11.18 um 00:31 schrieb Mike:
>>> Fabian, im sure you can tell that nothings going to change :(
>>> But maybe these shutdowns in protest will provoke change, before its too 
>>> late?
>>> On Thu, 15 Nov 2018 23:23:43 +0000
>>> "Fabian A. Santiago" <address@hidden> wrote:
>>>> Wow! I’d love to see that as well.
>>>> I just saw Kristian’s post with his email exchange. It’s a shame the 
>>>> situation is going down like this. I do hope a proper solution can be 
>>>> found so I and hopefully others can return to contributing to the network, 
>>>> should the mode of operation dictate and stay this way.
>>>> --
>>>> Thanks,
>>>> Fabian S.
>>>> OpenPGP:
>>>> 0x643082042DC83E6D94B86C405E3DAA18A1C22D8F
>>>> On Thu, Nov 15, 2018 at 5:58 PM, Georg Faerber <address@hidden> wrote:
>>>>> Hi,
>>>>> On 18-11-15 23:56:07, Moritz Wirth wrote:
>>>>>> will cease operation - we received a request to remove
>>>>>> some keys and since we are unable to do this, we will shutdown all
>>>>>> keyservers and erase all relevant databases immediately.
>>>>> Would it be possible to share this request, omitting sensitive details?
>>>>> Cheers,
>>>>> Georg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]