-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/09/2014 02:36 AM, Martin Papik wrote:
Dear Kristian
Thank you for your response.
Second, with 1.1.3, are ECC signatures lost? Meaning if someone
queries my server running 1.1.3 for a key containing an ECC
signature, will only the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Kristian
Thank you for your response.
Second, with 1.1.3, are ECC signatures lost? Meaning if someone
queries my server running 1.1.3 for a key containing an ECC
signature, will only the one signature be missing or will there
be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
[Please do not top-post, it makes it difficult to follow the thread]
On 04/07/2014 05:12 AM, Martin Papik wrote:
Dear Phil
First of all thank you for your exhaustive response, it's much
appreciated.
I'm running it on real HW, so the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2014-04-06 at 13:49 +0300, Martin Papik wrote:
And my impression is that 1.1.3 is okay, a number of the servers
visible on https://sks-keyservers.net/status/ are 1.1.3, and so far
the only difference I came across is that 1.1.3 doesn't export
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
Thank you very much Jerzy, however I'm facing some problems. I wonder if
you have any insight. I'm new to sks, but it seems to me that there
might be an apache proxy intercepting the connections and interfering
somehow. I don't see my server in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
Quoting from https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering
'Versions prior to 1.1.2 have a severe interoperability bug (POST
requests for exchanging keys are HTTP/0.9, does not work with modern
setups having reverse HTTP
Thank you, I've upgraded to 1.1.3, although why Ubuntu didn't install
that one without an explicit parameter boggles me a bit. Oh well. Is
that sufficient, or will I have to install the very latest from source?
The web server is enabled, there's just no main page in the directory yet.
I see
Hi everyone,
I've just configured sks 1.1.1 (default on Ubuntu) on
sks-server.randala.com. The machine has IPv6 but SKS has not yet been
assigned an address. I wonder, is there an advantage (e.g. in terms of
peering)? The server is located in Germany/EU. For now I'm deploying the
server for
11 matches
Mail list logo
