Re: [Dcrup] Open issue -- sha1 must not generate [and|or] accept
"John Levine" <johnl@taugh.com> Thu, 27 July 2017 23:01 UTC
Return-Path: <johnl@taugh.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 1D134131E84 for <dcrup@ietfa.amsl.com>; Thu, 27 Jul 2017 16:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 yupXmYRXkBzm for <dcrup@ietfa.amsl.com>; Thu, 27 Jul 2017 16:01:24 -0700 (PDT)
Received: from miucha.iecc.com (w6.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D8F312F274 for <dcrup@ietf.org>; Thu, 27 Jul 2017 16:01:24 -0700 (PDT)
Received: (qmail 24233 invoked from network); 27 Jul 2017 23:01:23 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 27 Jul 2017 23:01:23 -0000
Date: Thu, 27 Jul 2017 23:00:52 -0000
Message-ID: <20170727230052.51646.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dcrup@ietf.org
Cc: rsalz@akamai.com
In-Reply-To: <c4dca8d57f894b9daf4168f2ec9287ae@usma1ex-dag1mb3.msg.corp.akamai.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/qZA9G53Wn4sWREJvDR2h7pIVnbI>
Subject: Re: [Dcrup] Open issue -- sha1 must not generate [and|or] accept
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: Thu, 27 Jul 2017 23:01:26 -0000
In article <c4dca8d57f894b9daf4168f2ec9287ae@usma1ex-dag1mb3.msg.corp.akamai.com> you write: >https://datatracker.ietf.org/doc/draft-ietf-dcrup-dkim-ecc/?include_text=1 is about using ECC. And >since ECC is brand-new to DKIM, there is no legacy/installed base to deal with so we can just not use >SHA1. > >Is this okay? If not, what what is wrong. Nothing's wrong. The current draft just says eddsa-sha256, to be renamed ed25519-sha256. I suppose I should split that from the hashed RSA draft although it's going to be kind of a pain to cross-reference the new key field in the signature header. R's, John
- [Dcrup] Open issue -- sha1 must not generate [and… Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Jim Fenton
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Jim Fenton
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … A. Schulze
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Barry Leiba
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … John Levine
- Re: [Dcrup] Open issue -- sha1 must not generate … John Levine
- Re: [Dcrup] Open issue -- sha1 must not generate … Barry Leiba
- Re: [Dcrup] Open issue -- sha1 must not generate … Scott Kitterman
- Re: [Dcrup] Open issue -- sha1 must not generate … Jon Callas
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Jon Callas
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Hector Santos
- Re: [Dcrup] Open issue -- sha1 must not generate … Salz, Rich
- Re: [Dcrup] Open issue -- sha1 must not generate … Martin Thomson