> > 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.
>
> So we should just wait for new certificates. Right? :)
All of us have to generate new secret key key and signing request first.
Hello
On 04/09/2014 10:51 PM, 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 that I originally got
> requests from.
So we should just wait for new certificates. Right? :)
-
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.
HOWEVER please excuse some tardiness on my part for the next week as I'll be
off on holiday and won't have access to my offline keys
Sent fro
Folks,
Do not forget that all hkps.pool.sks-keyservers.net certificates
should be revoked and replaced after fixing openssl Heartbleed Bug
on vulnerable key servers. (Including mine.)
Gabor
___
Sks-devel mailing list
Sks-devel@nongnu.org
https://lists.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/09/2014 02:36 AM, Martin Papik wrote:
> Dear Kristian
>
> Thank you for your response.
>
>>> Second, with 1.1.3, are ECC signatures lost? Meaning if someone
>>> queries my server running 1.1.3 for a key containing an ECC
>>> signature, will
