Re: [TLS] WGLC for "Deprecating TLSv1.0 and TLSv1.1"

Hubert Kario <hkario@redhat.com> Mon, 06 May 2019 11:19 UTC

Return-Path: <hkario@redhat.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7D3120059 for <tls@ietfa.amsl.com>; Mon, 6 May 2019 04:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nnq0Rly6zwDd for <tls@ietfa.amsl.com>; Mon, 6 May 2019 04:19:09 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF8DF120058 for <tls@ietf.org>; Mon, 6 May 2019 04:19:08 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C45D33084031; Mon, 6 May 2019 11:19:07 +0000 (UTC)
Received: from pintsize.usersys.redhat.com (unknown [10.43.21.83]) by smtp.corp.redhat.com (Postfix) with ESMTP id 026B52708C; Mon, 6 May 2019 11:19:06 +0000 (UTC)
From: Hubert Kario <hkario@redhat.com>
To: mrex@sap.com
Cc: tls@ietf.org, Martin Thomson <mt@lowentropy.net>
Date: Mon, 06 May 2019 13:18:55 +0200
Message-ID: <5707914.oG825gbWTC@pintsize.usersys.redhat.com>
In-Reply-To: <20190503145654.B6421404C@ld9781.wdf.sap.corp>
References: <28511b10-8f6a-4394-95a9-5188130f7b58@www.fastmail.com> <5441930.X76MtM1CnQ@pintsize.usersys.redhat.com> <20190503145654.B6421404C@ld9781.wdf.sap.corp>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2707469.Cs2EVW077G"; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.40]); Mon, 06 May 2019 11:19:07 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/owcQFd808XJvmDNzxZOUZmeHXg4>
Subject: Re: [TLS] WGLC for "Deprecating TLSv1.0 and TLSv1.1"
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 11:19:11 -0000

On Friday, 3 May 2019 16:56:54 CEST Martin Rex wrote:
> Hubert Kario <hkario@redhat.com> wrote:
> > We've been over this Martin, the theoretical research shows that for
> > Merkle- Damgård functions, combining them doesn't increase their security
> > significantly.
> 
> You are completely misunderstanding the results.
> 
> The security is greatly increased!

like I said, that were the follow up papers

the original is still Joux:
https://www.iacr.org/archive/crypto2004/31520306/multicollisions.pdf

>   TLSv1.2 (rsa,MD5) *cough* -- which a depressingly high number of clueless
>           implementers actually implemented, see SLOTH

SLOTH? You mean the same one in which Bhargavan and Leurent write:

Concatenation: To  strengthen  protocols  against  collisions  in  any  one  
hash  function,  it  may  be  tempting  to use  a  combination  of  two  
independent  hash  functions. For example, TLS versions up to 1.1 use a 
concatenation of  MD5  and  SHA-1.  While  the  output  length  of  this 
construction  is  288  bits,  it  does  not  offer  the  security of a 288-bit 
hash function. In particular, Joux described a  multi-collision  attack  that  
breaks  the  concatenation of  two  hash  functions  with  roughly  the  same  
effort  as breaking the strongest one of the two [18].
-- 
Regards,
Hubert Kario
Senior Quality Engineer, QE BaseOS Security team
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 115, 612 00  Brno, Czech Republic