Hi Kristian (2012.07.26_20:27:50_+0200)
Try adding: Header set Server Apache to the config.
IIRC it needs to be lower-case apache.
http://code.google.com/p/sks-keyservers-pool/source/browse/trunk/sks-keyservers.net/status-srv/sks.inc.php#337
SR
--
Stefano Rivera
http://tumbleweed.org.za/
On 2012-07-27 08:50, Stefano Rivera wrote:
Hi Kristian (2012.07.26_20:27:50_+0200)
Try adding: Header set Server Apache to the config.
IIRC it needs to be lower-case apache.
http://code.google.com/p/sks-keyservers-pool/source/browse/trunk/sks-keyservers.net/status-srv/sks.inc.php#337
Not
On 2012-07-27 05:10, Daniel Kahn Gillmor wrote:
hey folks--
Hi
...
If anyone has a thoughts about how i could have handled this
differently, i'd be happy to hear it.
Just rebuilding the PTree folder using pbuild would probably suffice, as
long as there wasn't any corruption in (K)DB.
On 2012-07-27 06:05, Phil Pennock wrote:
On 2012-07-26 at 09:40 -0400, Phil Benchoff wrote:
...
Hrm, for full compliance with HTTP, we really need:
proxy_pass_header Server;
Thanks for the tip
Now, doing this breaks the current pool checks, because the Server:
header goes back to
Hi all!
Christoph Egger christ...@christoph-egger.org writes:
Due to random hangs I've stopped sks on keyserver.siccegge.de for now
which seems to improve things a bit (I'd bet on network stack). Will be
back after debugging stuff a bit / replacing hardware.
It's currently back online.
Dear Kristian,
I'm just came back from the holliday.
Surprisingly I found the keys.niif.hu is not in the pool.
More precisely no servers running SKS 1.1.1 is included.
I quickly scanned the recent mails of sks-devel but I found
no announcement about new requirements.
Page
On 07/27/2012 01:08 PM, Kiss Gabor (Bitman) wrote:
I'm just came back from the holliday.
welcome back!
Surprisingly I found the keys.niif.hu is not in the pool.
More precisely no servers running SKS 1.1.1 is included.
I quickly scanned the recent mails of sks-devel but I found
no
While I've used git/hg a bit, before today I hadn't dealt with creating
server-forked repos and issue pull requests.
That part of the process is clean and simple. But none of the docs I'm
finding describe what happens *next*, how do you clean up?
I know that for git-like models, and I assume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/25/2012 08:08 PM, David Benfell wrote:
On 07/25/2012 02:19 PM, David Benfell wrote:
Hi all,
I will reply to this posting with an additional note just before
I begin the test.
The experiment is, so far, a failure. Even my initial network
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/25/2012 08:08 PM, David Benfell wrote:
On 07/25/2012 02:19 PM, David Benfell wrote:
Hi all,
I will reply to this posting with an additional note just before
I begin the test.
The experiment is, so far, a failure. Even my initial network
10 matches
Mail list logo
