Re: [TLS] security levels for TLS

Eric Rescorla <ekr@networkresonance.com> Sat, 13 October 2007 07:40 UTC

Return-path: <tls-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Igbbo-00075n-9N; Sat, 13 Oct 2007 03:40:28 -0400
Received: from tls by megatron.ietf.org with local (Exim 4.43) id 1Igbbm-00075h-PV for tls-confirm+ok@megatron.ietf.org; Sat, 13 Oct 2007 03:40:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Igbbm-00075Z-G5 for tls@lists.ietf.org; Sat, 13 Oct 2007 03:40:26 -0400
Received: from [74.95.2.169] (helo=delta.rtfm.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Igbbl-0001C1-9u for tls@lists.ietf.org; Sat, 13 Oct 2007 03:40:26 -0400
Received: from delta.rtfm.com (localhost.rtfm.com [127.0.0.1]) by delta.rtfm.com (Postfix) with ESMTP id 5CDA833C28; Sat, 13 Oct 2007 00:36:14 -0700 (PDT)
Date: Sat, 13 Oct 2007 00:36:13 -0700
From: Eric Rescorla <ekr@networkresonance.com>
To: Mike <mike-list@pobox.com>
Subject: Re: [TLS] security levels for TLS
In-Reply-To: <4710146E.4080909@pobox.com>
References: <c331d99a0710080621g7c0ec91et35c46553c23f4402@mail.gmail.com> <p0624082fc331b0ed0ecc@[192.168.1.100]> <FA998122A677CF4390C1E291BFCF59890849871E@EXCH.missi.ncsc.mil> <470D0243.3050009@pobox.com> <20071010180324.7ABC533C21@delta.rtfm.com> <470E4399.3010008@pobox.com> <20071011155829.965C733C28@delta.rtfm.com> <470EF76B.5050102@pobox.com> <20071012045718.DE16033C21@delta.rtfm.com> <470FB525.7010308@pobox.com> <20071012180445.1D22D33C21@delta.rtfm.com> <470FC52E.6080707@pobox.com> <p06240828c3357a914a76@[192.168.1.3]> <470FEA1F.7030500@pobox.com> <20071012220036.E3DFC33C21@delta.rtfm.com> <4710146E.4080909@pobox.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20071013073614.5CDA833C28@delta.rtfm.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: tls@lists.ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org

At Fri, 12 Oct 2007 17:42:22 -0700,
Mike wrote:
> >> Negatives:
> >>
> >>    - effort is needed to write a specification and approve it
> >>    - a server may not support the extension, so a client may
> >>      have to implement an inefficient renegotiation scheme in
> >>      addition anyway
> > 
> > - It encourages an inappropriate focus on key size. As I said already,
> >   There's a lot more to security than key size.
> 
> But key size -is- a big part of it, and you should be able to tell
> a server what key sizes you want, rather than leave it up to chance.

To sharpen the point I was trying to make earlier, once you're using
keys in the 1024-bit range, there are actually a number of other
factors which are of equivalent if not larger importance to key
size. These include:

- The quality of PRNG used to generate the key.
- Whether the key is being securely stored (e.g, in an HSM).
- When we're talking DH, whether each ephemeral is fresh, and
  the structure of the DH group.
- Which server is in use.
- Whether the server software is up to date.

The last two in particular are of vastly more importance than key
size. I have never heard of a 1024-bit RSA key being cracked, yet I'm
aware of remote vulnerabilities in every major C-based SSL
server. These vulnerabilities lead to far easier private key
extraction than factoring the modulus.

-Ekr









_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls