[saag] sha1 - have we more work to do?

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 09 October 2015 13:25 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F07761B3DDE for <saag@ietfa.amsl.com>; Fri, 9 Oct 2015 06:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 5ANc7DoUyWCN for <saag@ietfa.amsl.com>; Fri, 9 Oct 2015 06:25:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE0991B3DB6 for <saag@ietf.org>; Fri, 9 Oct 2015 06:25:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 20928BE59 for <saag@ietf.org>; Fri, 9 Oct 2015 14:25:43 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zV4MS28PHxwr for <saag@ietf.org>; Fri, 9 Oct 2015 14:25:41 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.26.211]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5D0EEBDD0 for <saag@ietf.org>; Fri, 9 Oct 2015 14:25:41 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1444397141; bh=2mmjzH5u05xZYaXWP9F2U7wdPCTlgRXFHmi2L0VCAIA=; h=To:From:Subject:Date:From; b=o4bD+Bl9yhQuGu77rYs2bN02JJreRJCoU0S3jS6icrDN3Or27sIkyO1i6ZVxUYjNQ EwWcSeacH1Zod9UAWz6D/hrYmn/EFW7noBWNC0NmS4u40+ctnI4UGJJL8D3SSuy0hf w6MJP4SitrgSJzZ1U1NobWgwi7NlxnJC4SuxWXDo=
To: "saag@ietf.org" <saag@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5617C054.1070207@cs.tcd.ie>
Date: Fri, 09 Oct 2015 14:25:40 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/1iiiMLJmrtEMSmghoYO6lC_xje4>
Subject: [saag] sha1 - have we more work to do?
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2015 13:25:48 -0000

Hiya,

While it may be still under submission, and not yet peer reviewed,
I was just looking at [1,2] and wondered if we've still work to do
to deprecate sha1 anywhere that we've not yet done. I know a lot
of this was done already but just wanted to check that we're good.

Anyone know places where sha1 is still a should or must or where it's
still in widespread use despite no longer being a should or must?
(No need to mention root stores in browser for that last though, as
that's a known issue and is I think already being tackled by browser
makers.)

I guess we can make a list and then figure out what to do if the
list is non-empty.

Cheers,
S.

[1] https://sites.google.com/site/itstheshappening/
[2] https://sites.google.com/site/itstheshappening/shappening_article.pdf