Re: [TLS] TLS 1.2

"Steven M. Bellovin" <smb@cs.columbia.edu> Mon, 29 August 2005 12:22 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E9if3-00072i-KL; Mon, 29 Aug 2005 08:22:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E9if2-00072M-1m for tls@megatron.ietf.org; Mon, 29 Aug 2005 08:22:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04843 for <tls@ietf.org>; Mon, 29 Aug 2005 08:22:45 -0400 (EDT)
Received: from machshav.com ([147.28.0.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E9igK-00067T-4y for tls@ietf.org; Mon, 29 Aug 2005 08:24:09 -0400
Received: by machshav.com (Postfix, from userid 512) id 24B51FB262; Mon, 29 Aug 2005 08:22:39 -0400 (EDT)
Received: from berkshire.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id 494A5FB246; Mon, 29 Aug 2005 08:22:38 -0400 (EDT)
Received: from cs.columbia.edu (localhost [127.0.0.1]) by berkshire.machshav.com (Postfix) with ESMTP id 3B7CB3BFFF4; Mon, 29 Aug 2005 08:22:37 -0400 (EDT)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: pgut001@cs.auckland.ac.nz
Subject: Re: [TLS] TLS 1.2
In-Reply-To: Your message of "Mon, 29 Aug 2005 21:47:10 +1200." <E1E9gEQ-0002RK-00@medusa01.cs.auckland.ac.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 29 Aug 2005 08:22:37 -0400
Message-Id: <20050829122237.3B7CB3BFFF4@berkshire.machshav.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: tls@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>
Sender: tls-bounces@lists.ietf.org
Errors-To: tls-bounces@lists.ietf.org

In message <E1E9gEQ-0002RK-00@medusa01.cs.auckland.ac.nz>, Peter Gutmann writes
:
>Eric Rescorla <ekr@rtfm.com> writes:
>
>>I'd like to start a discussion on whether we should be thinking about a TLS
>>1.2 that was more oriented towards newer hash functions. Obviously, we're not
>>at a point where there's a crisis yet but it doesn't hurt to be prepared.
>
>I've actually had a proposal for fixing TLS' broken signatures sketched out
>probably since it was still SSL, so perhaps we can use this to fix several
>problems at once.  Firstly, in terms of attacks on hash functions, the only
>thing that really needs to be addressed is the use of hash functions as, well,
>hash functions.  Most of the use in TLS is as PRFs and in HMAC, none of which
>are even remotely endangered by any known attack.  Signatures, however, need
>to be fixed for three main reasons:

Note that we're also talking about negotiating which certificates are 
used.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb



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