sks-devel
[Top][All Lists]
Advanced

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

Re: [Sks-devel] info on opks.keyserver.ch [was: Mailsync]


From: Jorgen Cederlof
Subject: Re: [Sks-devel] info on opks.keyserver.ch [was: Mailsync]
Date: Tue, 6 Mar 2012 22:30:33 -0800
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, Mar 05, 2012 at 14:37:20 -0500, Eric H. Christensen wrote:
> On Mon, Mar 05, 2012 at 10:08:43AM +0100, kwadronaut wrote:
>> Hi,
>> 
>> First: sorry for breaking threads, somehow the mailarchives aren't
>> playing nicely along with me for finding out the message-id.
>> 
>> John Clizbe asked [1] if anyone has any info on the OPKS Swiss OpenPGP
>> Keyserver. I've been told that Kiss Gabor is also interested in this
>> info. I contacted yesterday the person who has been maintaining it for a
>> long time, Patrick Feisthammel. He has now taken it offline and wot
>> generation has been stopped.
>> 
>> Patrick, if you read this: Thanks for having taken care of that for such
>> a long time, and also thanks for switching the lights off.
>> 
>> Have a nice day,
>> 
>> kwadronaut
>> 
>> [1] http://lists.gnu.org/archive/html/sks-devel/2011-10/msg00056.html
>> [2] http://opks.keyserver.ch:11371/pks/
> 
> That's too bad. Is there any thought to putting that functionality
> into SKS? I've been quite interested in the WOT functions that
> server has/had.

Getting the functionality into SKS should not be that hard. The
current pks2wot.py simply executes pksclient to fetch a key and uses
gpg to parse it. If SKS has something similar to pksclient, that
should work fine. In theory you can do this over internet, but to get
decent performance you will need to run it on (or close to) the key
server.

The bigger problem is maintaining it: Making sure it runs something
like once a day, make sure it has an archive with enough space that is
accessible for downloading, fix bugs if they come up, and things like
that.

There is also http://www.lysator.liu.se/~jc/wotsap/search.html . This
fetches and mirrors the .wot files and acts as a web frontend to
perform queries against the latest .wot. This is maintained by me, but
I don't really have much time to take care of it so it would be good
if someone else took over that part too. Most of the complexity is
from syncing the .wot files from the key server, so if they are both
maintained and run together, things should be much simpler.

  Jörgen



reply via email to

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