sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] How to delete single keys from the SKS keyserver


From: Yaron Minsky
Subject: Re: [Sks-devel] How to delete single keys from the SKS keyserver
Date: Wed, 4 Jun 2008 20:59:40 -0400

Ari is right that it's not trivial, but I do think there are some technically reasonable solutions if you can find some way of having everyone agree on which keys should be removed.  For instance, if you had a trusted set of "deleters", they could sign certificates that indicated which keys should be deleted, and these certificates could be gossiped around with everything else, and used to delete keys from the network.

Unfortunately, the decentralized nature of the SKS network makes this a bit hard to manage, since it's not clear who the trusted deleters should be.  (Also, there's the small matter of who should implement the functionality in the keyserver.  I'm happy to do maintenance work on SKS, but I don't have time for implementing significant new functionality). 

y

On Wed, Jun 4, 2008 at 12:28 PM, Ari Trachtenberg <address@hidden> wrote:
We had talked about approaches to this ... it turns out to be an
non-trivial problem to
integrate this with the efficient synchronizer without breaking the
synchronizer's efficiency.

Best,
  _Ari


Yaron Minsky wrote on 06/04/2008 07:25 AM:
> On Wed, Jun 4, 2008 at 2:56 AM, Patrick Rother <address@hidden> wrote:
>
>
>> Hello.
>>
>>
>>>> You can use the "sks drop" command with a key hash as a parameter.
>>>>
>> You'll need to have a running SKS server.
>>
>> Althouhg having read "sks help", "sks --help" and the man page at
>> least two times each, I really overlooked the sks drop command.
>>
>> Thank you!
>>
>>
>>> But if the key is already on other servers you will get it back with the
>>> next sync.
>>>
>> Yes, I'm aware of that, but I have to comply with a users request to
>> delete the key.
>>
>> BTW, is there a way to block specific keys from being synced into my
>> server?
>>
>>
>
> There's nothing in theory to prevent it, but I never got around to
> implementing blocks like this.
>
> y
>
>
>
>> Thank you.
>>
>>
>>
>> _______________________________________________
>> Sks-devel mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/sks-devel
>>
>>
>>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/sks-devel
>



reply via email to

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