Re: [Dcrup] rsa-sha1 proposals

Scott Kitterman <sklist@kitterman.com> Tue, 20 June 2017 16:40 UTC

Return-Path: <sklist@kitterman.com>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 689F7131BC1 for <dcrup@ietfa.amsl.com>; Tue, 20 Jun 2017 09:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 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_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kitterman.com
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 7w3uJiQAjesA for <dcrup@ietfa.amsl.com>; Tue, 20 Jun 2017 09:40:41 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D2B6131BD4 for <dcrup@ietf.org>; Tue, 20 Jun 2017 09:40:27 -0700 (PDT)
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 0CC57C40021 for <dcrup@ietf.org>; Tue, 20 Jun 2017 11:40:25 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1497976825; bh=TQSCV5fO+iHxVNv5r+bFCT6l0w7hMyH2j237iS+4IzU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UJeDQ2ipQOk0BJz96z0PnZKchmoRCC2rZVnU4TmRcLCKXGInUZJaaP3EQJiRlBdKm ZnTBl0aZyf1qmngCeSy6/mG4DJjvLptca+9/OiR6UAumhkCHy80/XQ2daQJiTaB6ZV H8dDdopC/jYtAxHHwMMbo+lCPnppiF0jF9nraWYg=
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Tue, 20 Jun 2017 12:36:35 -0400
Message-ID: <1555197.Rcy4aD9AYe@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-119-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CAOZAAfPvDDuTW6cC6ZQqN7zxDEvVn8=Lp_8jCveigE5zT8gDmA@mail.gmail.com>
References: <1642300.47WuTbIWPP@kitterma-e6430> <CAOZAAfPvDDuTW6cC6ZQqN7zxDEvVn8=Lp_8jCveigE5zT8gDmA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/clGV1EI8M5Y8OFLvEXrfikulIrU>
Subject: Re: [Dcrup] rsa-sha1 proposals
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2017 16:40:43 -0000

On Tuesday, June 20, 2017 09:18:56 AM Seth Blank wrote:
> On Tue, Jun 20, 2017 at 8:39 AM, Scott Kitterman <sklist@kitterman.com>
> 
> wrote:
> > Remove rsa-sha1:
> > This option eliminates (to the extent it is adopted) the potential of
> > security
> > risks with rsa-sha1.  If a relevant issue with rsa-sha1 is made public,
> > there
> > will be no further standards work that needs to be done.  This option also
> > keeps the number of algorithms at two, eliminating the additional
> > complexity
> > associated with having more algorithms to sort through in implementation.
> > While this might be considered somewhat abrupt, rsa-sha1 signing has been
> > effectively SHOULD NOT for a decade.  Maybe this will create some momentum
> > for
> > operators to move off of it.
> > 
> > It is abrupt to remove something without a formal deprecation period.
> 
> I strongly vote to remove SHA1 as proposed here; I do not believe any other
> approach will incentivize senders or receivers to make the change.
> 
> I do not believe this qualifies as an "abrupt" deprecation, as you said, it
> has been SHOULD NOT for over a decade.

Modulo the IETF doesn't vote, I agree, but then you knew that already.  
Hopefully the responses give enough information for the chairs to develop an 
opinion about where the consensus is on this issue.

Thanks,

Scott K