Hello.
On 05/25/2014 12:00 AM, Kristian Fiskerstrand wrote:
On 05/24/2014 08:32 AM, Gabor Kiss wrote:
On Wed, 9 Apr 2014, kristian.fiskerstr...@sumptuouscapital.com
wrote:
You are quite correct, and I will revoke and issue new
certificates as I get CSRs signed with the same openpgp keys
On 05/27/2014 09:27 AM, Dmitry Yu Okunev (pks.mephi.ru) wrote:
BTW, is it right that our server is not in the HKPS pool
hkps.pool.sks-keyservers.net.
Server: keyserver.ut.mephi.ru (85.143.112.59)
$ host hkps.pool.sks-keyservers.net
hkps.pool.sks-keyservers.net has address 162.243.102.241
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/27/2014 05:00 PM, Daniel Kahn Gillmor wrote:
On 05/27/2014 09:27 AM, Dmitry Yu Okunev (pks.mephi.ru) wrote:
BTW, is it right that our server is not in the HKPS pool
hkps.pool.sks-keyservers.net.
..
the host command just looks
Am 27.05.2014 17:41, schrieb Kristian Fiskerstrand:
On 05/27/2014 05:00 PM, Daniel Kahn Gillmor wrote:
On 05/27/2014 09:27 AM, Dmitry Yu Okunev (pks.mephi.ru) wrote:
BTW, is it right that our server is not in the HKPS pool
[pools and zone-entries]
To check the inclusion of your server in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Kristian
You are quite correct, and I will revoke and issue new
certificates as I get CSRs signed with the same openpgp keys
that I originally got requests from.
Please consider to remove vulnerable servers from HKPS pool.
This is not a
Dear Rolf,
On Tue, May 27, 2014 at 10:18:31PM +0200, Rolf Wuerdemann wrote:
Am 27.05.2014 17:41, schrieb Kristian Fiskerstrand:
On 05/27/2014 05:00 PM, Daniel Kahn Gillmor wrote:
To check the inclusion of your server in the hkps pool, look at the
HKPS column of:
