Re: [Sks-devel] Apache setup for refusing to serve bad keys

2019-02-18 Thread John Zaitseff
Hi, all again, Slight bug fix: replace: RewriteCond "%{QUERY_STRING}" "search=([^&]+)&?" with: RewriteCond "%{QUERY_STRING}" "search=([^&]+)(&|$)" John Zaitseff -- John Zaitseff ,--_|\The ZAP Group Telephone: +61 2 9643 7737 / \

Re: [Sks-devel] Apache setup for refusing to serve bad keys

2019-02-18 Thread John Zaitseff
Hi, all, I previously wrote: > [...] Here is my version for the Apache server. It allows you to > include the list of keys in a separate file that can be updated at > any time without restarting/reloading the server. I've since revised the Apache configuration file to contain: RewriteEngine

[Sks-devel] Apache setup for refusing to serve bad keys

2019-02-18 Thread John Zaitseff
Hi, everyone, There's been some discussion on this list about refusing to serve bad OpenPGP keys -- at least as a workaround for the time being. Andreas Puls has even supplied a configuration snippet for nginx. Here is my version for the Apache server. It allows you to include the list of keys

Re: [Sks-devel] Annoying malicious keys - any easy solution?

2019-02-18 Thread Andreas Puls
Hi Todd, Am 17.02.2019 um 17:02 schrieb Todd Fleisher: > Do you (or others) see are any side effects to this approach? I’m > particularly wondering if it would cause your server to fall behind if it > repeatedly closes connections from its peers. > Sorry, currently i don't know - it was a

Re: [Sks-devel] SKS scaling configuration

2019-02-18 Thread Michiel van Baak
On Sun, Feb 17, 2019 at 09:18:11AM -0800, Todd Fleisher wrote: > The setup uses a caching NGINX server to reduce load on the backend nodes > running SKS. > His recommendation is to run at least 3 SKS instances in the backend (I’m > running 4). > Only one of the backend SKS nodes is configured to