IETF Logo Mail Archive

[TLS] Deprecate SHA1 for signatures in TLS 1.3 (was Re: TLS 1.3 draft-07 sneak peek)

Dave Garrett <davemgarrett@gmail.com> Tue, 07 July 2015 15:35 UTC

Return-Path: <davemgarrett@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23BE71A8901 for <tls@ietfa.amsl.com>; Tue, 7 Jul 2015 08:35:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 ldpsCpxsiNlj for <tls@ietfa.amsl.com>; Tue, 7 Jul 2015 08:35:06 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3F551A8912 for <tls@ietf.org>; Tue, 7 Jul 2015 08:35:05 -0700 (PDT)
Received: by qkhu186 with SMTP id u186so142569880qkh.0 for <tls@ietf.org>; Tue, 07 Jul 2015 08:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=ORmGpJZhRUqQHH6iK6d4u6KDMQs5B2eBcv7PWkQkiQc=; b=e92sTwOPEtp1njXwpGpPfqRmydtcf/0C89VnodBNUGoTuo+ZtrucK5/N/ZZDl4mY+d 6BcSemqVUFcPfwWGpS/U55KAOvPams6rb0/ICT00s0wBcaJOej7bNJ7+zoyyHu6aMdI9 1DuR8a9MA1Agwzc5XyAWxN8nIXZOfquy/VeUiTz213c9KMU28vI8o7ukYBRhrM9r4PGl RaM98ez670Fx2mhy7zeh3s2g+S955UDXPMVri6fC7ArYBexZT4aqrpAWW6vXyiANlgfl 8CTha1EMyR5QcxRxUReU6mAWe6cZFzJlrRGyAX6LMV05aYfT3vbeFkehrE4fEIPX9t6y vAWQ==
X-Received: by 10.140.98.238 with SMTP id o101mr7806194qge.12.1436283305212; Tue, 07 Jul 2015 08:35:05 -0700 (PDT)
Received: from dave-laptop.localnet (pool-96-245-254-195.phlapa.fios.verizon.net. [96.245.254.195]) by mx.google.com with ESMTPSA id 10sm11386748qgl.9.2015.07.07.08.35.01 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 07 Jul 2015 08:35:04 -0700 (PDT)
From: Dave Garrett <davemgarrett@gmail.com>
To: tls@ietf.org
Date: Tue, 07 Jul 2015 11:35:00 -0400
User-Agent: KMail/1.13.5 (Linux/2.6.32-74-generic-pae; KDE/4.4.5; i686; ; )
References: <CABcZeBOWK_WnHAefsZUBr4UyEkyiZqi1mhoZH8ZeGFftdOqTTw@mail.gmail.com> <7D0FA086-F797-4B11-B5DE-6D202DEF8001@gmail.com> <20522301ad4047bf8a9e3794fd785da9@ustx2ex-dag1mb2.msg.corp.akamai.com>
In-Reply-To: <20522301ad4047bf8a9e3794fd785da9@ustx2ex-dag1mb2.msg.corp.akamai.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201507071135.00448.davemgarrett@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/ZspLmk4oiN6x44PTx8VdQJBiiM4>
Cc: Karthikeyan Bhargavan <karthik.bhargavan@gmail.com>
Subject: [TLS] Deprecate SHA1 for signatures in TLS 1.3 (was Re: TLS 1.3 draft-07 sneak peek)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 07 Jul 2015 15:35:08 -0000

On Tuesday, July 07, 2015 10:57:24 am Salz, Rich wrote:
> > Putting aside the timeline for retiring SHA-1 from certificates, which will
> > happen sooner than later, I think we should ban MD5 and SHA1 from client
> > and server signatures in TLS 1.3.
> 
> Strongly in favor.  I see no reason why a new protocol should ever use SHA1.

Good. There seems to be strong support all around for this. I've updated the PR to drop SHA1 too.

PR:
https://github.com/tlswg/tls13-spec/pull/188/files
Issue:
https://github.com/tlswg/tls13-spec/issues/186

I also have a mandatory extensions patch here:
https://github.com/davegarrett/tls13-spec/compare/pruning...davegarrett:mandatoryextensions

I'll probably just submit a PR for that too in a bit.


Dave

v2.23.0 | Report a Bug | By Email