Re: [TLS] Issue 30: Reject RSA public exponent 1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TLS] Issue 30: Reject RSA public exponent 1
On 6/3/07, Eric Rescorla <ekr at networkresonance.com> wrote:
http://www3.tools.ietf.org/wg/tls/trac/ticket/30
Nelson Bolyard writes:
Some time ago, mozilla was modified to detect and reject RSA
keys with public exponents equal to 1. Presumably, the
readers of this list need no explanation of the implications
of such keys.
Now, mozilla users are encountering web sites whose certs have
such keys. At least one public CA has apparently issued one
or more such certs.
I'm reporting this here to alert the readers of this list who
may wish to ensure that their implementations detect such
keys, and to suggest that perhaps the TLS RFC should
explicitly forbid the use of any public keys (RSA or
otherwise) that facilitate such weak encryption and/or
authentication by requiring implentations to detect and reject
them.
My general feeling is that there are a broad category of "good crypto
practices" issues that don't apply specifically to TLS. I'd love to
see an RFC on them, but would rather not see them in TLS proper
since they need to be duplicated in every crypto-using RFC.
Proposed resolution: do nothing.
I'm wondering what the threat model is here? So, the guy who makes the
key gets you to transmit your data in the plain. But, regardless of
exponent value, if he wants to reveal your data all he need do is
decrypt it and reveal it.
Now, I'm sure you can construct some James Bond scenario where its a
good idea to reveal your victim's credit card number to a local
sniffer instead of the central server, but hey, we've got Tor and
anonymous remailers, anyone can hide their identity, so why bother?
-Ekr
_______________________________________________
TLS mailing list
TLS at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls
_______________________________________________
TLS mailing list
TLS at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.