-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's the nginx config I use for my server. This setup tries
to be the most secure with HTTPS and HSTS with cert pinning.
Also, the cipher list is 100% forward secrecy and uses a strong
4096 dhparam.
Unfortunately, the only downside is that if you vi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/01/2015 04:25 PM, Arnold wrote:
> On 19-07-15 17:58 +0200, Kristian Fiskerstrand wrote:
>
> Looking at https://sks-keyservers.net/status/ I see
>
>> These statistics were last updated: 2015-07-19 19:35 (UTC)
>
> Kristian, did you update som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.08.2015 at 16:25, Arnold wrote:
> On 19-07-15 17:58 +0200, Kristian Fiskerstrand wrote:
>
> Looking at https://sks-keyservers.net/status/ I see
>
>> These statistics were last updated: 2015-07-19 19:35 (UTC)
>
> Kristian, did you update s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 31.07.2015 at 01:05, Mike Forbes wrote:
> So now begins the task of trying to make HKPS and SSL and SKS all work
> together.
>
> Currently we're serving up our main pgp pages with our own SSL cert
> (https://pgp.net.nz)
>
> If we were to serv
On 19-07-15 17:58 +0200, Kristian Fiskerstrand wrote:
Looking at https://sks-keyservers.net/status/ I see
> These statistics were last updated: 2015-07-19 19:35 (UTC)
Kristian, did you update something on the monitoring that did not turn out as
expected? ;-)
Kind regards,
Arnold
___
On Fri, 31 Jul 2015 11:05:15 +1200
Mike Forbes wrote:
> If we were to serve this using the HKPS cert I imagine it would throw
> a certificate warning for most people who haven't imported the
> hkps.pool.sks-keyservers.net CA.
If you want to use hkps.pool.sks-keyservers.net with GnuPG you have to
