On Mon, Apr 20, 2015 at 09:50:45PM +0200, ma...@wk3.org wrote:
> Hi,
>
> I am looking for peers for a new SKS keyserver installation.
>
> I am running SKS version 1.1.5, on keys.enteig.net.
I'd be happy to peer:
gpg.n1zyy.com 11370 # Matt Wagner 0x2BE02E05
> I am runni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2/22/15 10:19 AM, Jeremy T. Bouse wrote:
> I'm curious if this is a OS or distribution specific change as I
> took the liberty of checking on my SKS hosts and found on all 3 the
> sks/DB directory was only around 12GB and at most I found 3 10MB
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi all,
I just noticed on one of my servers that the KDB directory has grown
to 26GB in size, including almost 1,200 10MB log.00 files. My
other server has "only" 600 of the log files.
I'm curious if there's a recommended practice for house
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I have hit that error!
In all honesty, at the time, I couldn't figure it out other than that
it had something to do with my sksconf file, so I just deleted the
file and set the relevant options on the command line. (Dumb, I know.)
I had poked around
11 December. It should be
available over both IPv4 and IPv6[1].
I show 3,793,492 keys loaded at this time. I kindly request some peers
to keep my database up to date. You might find this line appropriate
for placing in your membership file:
gpg.n1zyy.com 11370 # Matt Wagner 0x2BE02E05
This is
