Re: [Dcrup] Time For People To Really Stop Using SHA-1 Signatures?

Scott Kitterman <sklist@kitterman.com> Tue, 14 January 2020 14:58 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 845361200FD for <dcrup@ietfa.amsl.com>; Tue, 14 Jan 2020 06:58:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=hhD1xuUC; dkim=pass (2048-bit key) header.d=kitterman.com header.b=B8neRdin
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 J-D9Jckgswba for <dcrup@ietfa.amsl.com>; Tue, 14 Jan 2020 06:58:29 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E4941200FB for <dcrup@ietf.org>; Tue, 14 Jan 2020 06:58:29 -0800 (PST)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 97F6AF801CD for <dcrup@ietf.org>; Tue, 14 Jan 2020 09:58:28 -0500 (EST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1579013908; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=ys3cGtiHQnYMegTVwj1J371Xy7yXLtbrdW8xB9+x+yc=; b=hhD1xuUC39dW7g78MrtXC7OYDfpEPGw9tgnM6RsyQ947va9bTFpcSW2W AHmIX8GjF8bT7EoCdw/Pz/r13JfgDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1579013908; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=ys3cGtiHQnYMegTVwj1J371Xy7yXLtbrdW8xB9+x+yc=; b=B8neRdinoDNGkwzp+lARyQBtAr1mAytQ8xI1T1tjtkdNtbbMhSDHbLl/ 3EDJynlRVlkzCsIjaLAefzcHypQ0EAjhxbgqWcZ8Or+oj1spLZ93dqCHN/ NmU4aisI+VVlXlY0fzDofVNnGR78rsJxOY/O/XZHa09HnElu8CnFc98GIl TWKdRYKn8GXhKyQgYK3+PFJh/YLkQdhUlKdFEyeHbicpII5oUYRVhkr7iK UdKCXD5C4j7647+Fq0sx9yndgKMKLPJn9h8Cz0it8gnRme6biYBPb+pExo rH64zz57WL5CXR0nM3D5LM3sOlsh+8Nacm//1ywHsIdZC4Bz8yQmgw==
Received: from l5580.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id 612A5F800F2 for <dcrup@ietf.org>; Tue, 14 Jan 2020 09:58:28 -0500 (EST)
From: Scott Kitterman <sklist@kitterman.com>
To: dcrup@ietf.org
Date: Tue, 14 Jan 2020 09:58:27 -0500
Message-ID: <9344656.UHueZpf3bW@l5580>
In-Reply-To: <2930903.4jkiU04MHV@l5580>
References: <1836468.B6t98xBJ9D@l5580> <5E1DD3B8.5030507@isdg.net> <2930903.4jkiU04MHV@l5580>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/EkVssd6FSisZ4EdIrzFPYuIJyFo>
Subject: Re: [Dcrup] Time For People To Really Stop Using SHA-1 Signatures?
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Jan 2020 14:58:35 -0000

On Tuesday, January 14, 2020 9:50:58 AM EST Scott Kitterman wrote:
> On Tuesday, January 14, 2020 9:44:08 AM EST Hector Santos wrote:
> > Whether SHA1 usage is 10%, 5% or 1%, we need to remember, it is still
> > part of the protocol and DKIM Verifiers MUST be including SHA1 for
> > verification purposes.
> 
> No.  It's not.  Please review RFC 8301, which updates RFC 6376:
> > 3.1.  Signing and Verification Algorithms
> > 
> >    DKIM supports multiple digital signature algorithms.  Two algorithms
> >    are defined by this specification at this time: rsa-sha1 and
> >    rsa-sha256.  Signers MUST sign using rsa-sha256.  Verifiers MUST be
> >    able to verify using rsa-sha256.  rsa-sha1 MUST NOT be used for
> >    signing or verifying.
> >    
> >    DKIM signatures identified as having been signed with historic
> >    algorithms (currently, rsa-sha1) have permanently failed evaluation
> >    as discussed in Section 3.9 of [RFC6376].
> 
> I know you know this, so please stop pretending it's not true.

At some point you are going to have to actually implement sha-256:

DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1;

You're close to a decade and a half late.

Scott K