[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method

To: Georgi Guninski <[email protected]>
Subject: Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
From: [email protected] (Peter Gutmann)
Date: Thu, 3 Sep 2015 13:33:48 +0000
Cc: "[email protected]" <[email protected]>
In-reply-to: <[email protected]$>
References: <[email protected]$> <9A043F3CF02CD34C8E74AC1594475C73F4AF0463@uxcn10-5.UoA.auckland.ac.nz>, <[email protected]$>

Georgi Guninski <[email protected]> writes:

>Anyway, I would appreciate if someone checks if current implementations
>accept composite $q$.

Well, I think the problem will be finding any implementation of this at all,
or at least any that's still around now.

>What do you mean by DH certificate?

The static DH parameters need to be turned into a certificate by a CA.  I
don't know of any public CA that can issue these.

Peter.

Follow-Ups:
- Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
  - From: [email protected] (Georgi Guninski)

References:
- Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
  - From: [email protected] (Georgi Guninski)
- Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
  - From: [email protected] (Peter Gutmann)
- Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
  - From: [email protected] (Georgi Guninski)

Prev by Date: Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
Next by Date: Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
Previous by thread: Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
Next by thread: Possible crypto backdoor in RFC-2631 Diffie-Hellman Key Agreement Method
Index(es):
- Date
- Thread