Hi,
thanks for the information; I have now updated my nginx configuration. :)
Best regards,
Tobias Frei
Am 28.04.2014 18:25, schrieb Kristian Fiskerstrand:
> I've received reports that uploading some (large) keys to some of the
> keyservers in the pool (my test shows failure on 30 servers afte
On Apr 28, 2014 7:36 PM, "Jeremy T. Bouse"
wrote:
>
> I don't know about the others on the list but my configuration follows
> the recommendations from
> https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering which has
> never stated anything about this issue as long as I've been following
Dear all,
On Mon, Apr 28, 2014 at 06:25:45PM +0200, Kristian Fiskerstrand wrote:
I've received reports that uploading some (large) keys to some of the
keyservers in the pool (my test shows failure on 30 servers after
trying to run against 115: These are listed in [A]) results in a
gpgkeys: HTTP
On 04/28/2014 02:07 PM, Phil Pennock wrote:
> For now, if it's taken 15 years for someone keen on key signings to
> reach a 1MB limit, then I think that 8MB, covering 120 years of
> activity at such a rate, is likely to be enough for most normal mortal
> human beings. It's certainly enough to set
On 2014-04-28 at 13:32 -0400, Jeremy T. Bouse wrote:
> I don't know about the others on the list but my configuration follows
> the recommendations from
> https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering which has
> never stated anything about this issue as long as I've been following
I don't know about the others on the list but my configuration follows
the recommendations from
https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Peering which has
never stated anything about this issue as long as I've been following
it. Do we need to make changes to the documentation that's al
> I have not yet implemented an automated check for this in the pool
> (and a bit unsure how I'd do it without actually sending large amount
> of data to the server during the check, something I generally want to
> avoid), but might run a semi-manual / scripted check and add affected
> servers to t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've received reports that uploading some (large) keys to some of the
keyservers in the pool (my test shows failure on 30 servers after
trying to run against 115: These are listed in [A]) results in a
gpgkeys: HTTP post error 22: The requested URL re
