RE: ACTION-426: strong and weak TLS algorithms (incorporateISSUE-128text)

This is really quite late response but in looking at

Network Working Group                                          T.
Request for Comments: 4346
Obsoletes: 2246                                              E.
Category: Standards Track                                     RTFM,

              The Transport Layer Security (TLS) Protocol
                              Version 1.1

Appendix 5 notes ciphersuite definitions that are not considered secure


-----Original Message-----
From: Thomas Roessler [] 
Sent: Wednesday, June 11, 2008 2:08 PM
To: Doyle, Bill
Subject: Re: ACTION-426: strong and weak TLS algorithms

For context:

On 2008-06-11 13:46:06 -0400, Bill Doyle wrote:

> I like it -


> SSLv3 is deprecated - supported ciphers are no longer strong enough,
> industry moves forward.

I'm happy to add this one to the list of things that you really must
not consider strong.  Which brings me to another point:  It's
probably worth using RFC 2119 verbiage when we enumerate what's
considered weak or strong.  I've made that change in the latest
version, and would actually be tempted to change this further to say

	SSLv3 SHOULD NOT be considered strong.

I also wonder if it's worth saying a word about MD5-based certs.

> Is the IETF grouping ciphers in a way that enables weak ciphers to be
> noted? Export grade is easy, not sure about others.

Not that I'd know.

Thomas Roessler, W3C  <>

Received on Monday, 14 July 2008 18:52:42 UTC