Hi,
if you'd be using the latest Ubuntu, you would probably also have
access to the newest SKS version in the repositories. ;-)
Ubuntu 14.04 LTS will come out soon; upgrading to that should give you
1.1.4.
If your server is running on amd64, you can use this .deb for now, if
you want to:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am using the latest stable LTS, unfortunately, ubuntu LTS matures
slowly and I've been bitten with premature dist-upgrades. I'll choose
waiting over being a test-case. At least on anything that's exposed to
the internet.
# wget
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is why libc is required, I've tried to use sks-1.1.4 from trusty
already, same set of dependencies. And as before, if I'm going to
update libc, I might as well do a full dist upgrade.
# dpkg -i libdb5.3_5.3.28-3ubuntu2_amd64.deb
(Reading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I have removed these Peerings from my SKS Server due to long term
failed status and/or failed cross peerings:
- - keyserver.cais.rnp.br
- - keyserver.codinginfinity.com
- - sks.undergrid.net
I am always welcoming new peerings (Gossip
I don't know what failed status you're referring to with my cluster
running on sks.undergrid.net as you've certainly never made any attempt
at contact, but I've gone ahead and removed you from my membership file
as well.
On 06.04.2014 05:19, Christian wrote:
-BEGIN PGP SIGNED
Having just spent about an hour sifting through my recon.log and
trying to track down the number of unauthorized gossip attempts I was
seeing I've stopped. I've already contacted a few that I was able to
identify and instead just figured I'd blanket the list as it seems to be
a wider issue.
On 04/06/2014 02:06 PM, Gabor Kiss wrote:
Having just spent about an hour sifting through my recon.log and
trying to track down the number of unauthorized gossip attempts I was
seeing I've stopped. I've already contacted a few that I was able to
identify and instead just figured I'd
Having just spent about an hour sifting through my recon.log and
trying to track down the number of unauthorized gossip attempts I was
seeing I've stopped. I've already contacted a few that I was able to
identify and instead just figured I'd blanket the list as it seems to be
a wider
On 04/06/2014 06:19 PM, David Benfell wrote:
On Sun, Apr 06, 2014 at 11:37:50AM -0400, Jeremy T. Bouse wrote:
Having just spent about an hour sifting through my recon.log and
trying to track down the number of unauthorized gossip attempts I was
seeing I've stopped. I've already contacted a
