-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If one configures a proxy (such as nginx) with a config like:
# nginx syntax
# presume:
# keys.example.net 2001:DB8::1
# keys.example.net A198.51.100.1
server {
listen [::]:11371 ipv6only=off;
access_log off;
On 08/16/2013 10:03 AM, James Cloos wrote:
It looks like this might be a debian error.
sks-1.1.4 from debian experimental fails reliably when using sid, as of
the latest upgrade to libdb5.1 (5.1.29-7) in sid.
thanks for reporting this as http://bugs.debian.org/719876 -- it sounds
to me like
On Aug 19, 2013, at 6:30 PM, Daniel Kahn Gillmor wrote:
On 08/16/2013 10:03 AM, James Cloos wrote:
It looks like this might be a debian error.
sks-1.1.4 from debian experimental fails reliably when using sid, as of
the latest upgrade to libdb5.1 (5.1.29-7) in sid.
thanks for reporting
On 2013-08-19 at 17:59 -0400, James Cloos wrote:
If one configures a proxy (such as nginx) with a config like:
Don't, because that's not what the Peering wiki page says to do and
advertises the wrong port.
Use:
https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering#!nginx
Instead,
