Re: [Dcrup] Working Group Last Call for draft-ietf-dcrup-dkim-crypto
"John Levine" <johnl@taugh.com> Tue, 19 December 2017 01:43 UTC
Return-Path: <johnl@iecc.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 790FA12D95C for <dcrup@ietfa.amsl.com>; Mon, 18 Dec 2017 17:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.76
X-Spam-Level:
X-Spam-Status: No, score=-1.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=wknMbPaD; dkim=pass (1536-bit key) header.d=taugh.com header.b=LasfPGWu
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 uMspyB1D1TiH for <dcrup@ietfa.amsl.com>; Mon, 18 Dec 2017 17:43:25 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5D0E12D88A for <dcrup@ietf.org>; Mon, 18 Dec 2017 17:43:24 -0800 (PST)
Received: (qmail 24756 invoked from network); 19 Dec 2017 01:43:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=60b2.5a386ebb.k1712; bh=jqAJIlEoZlUO1M/l5qWlGWDSgvTxTmRw1lfkeXGoc4A=; b=wknMbPaDa7PFYhAxNpN5Dx/sUh8dizJKhdMaz9JsTZPkrCtUW875VlYm9Bb9Q/aDJiWacuvYPmqixDi0kYe9xrMfkw4qD/id9q5nlSdNv5q+K1JVA+/DykYsyvMpE+u+DFziPcBED9WharoZ4WfGSmveYnr/BUz/g4CR4mIjE/Nk6XzbipttzxSvNC+q+YdFJQoVgskb+g8ljGcl2eUJv1Mcy1+ZDGeYTw68v4o+VvgPYWUH1BqvsbQYkxWLxURO
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=60b2.5a386ebb.k1712; bh=jqAJIlEoZlUO1M/l5qWlGWDSgvTxTmRw1lfkeXGoc4A=; b=LasfPGWuuWQ7N1qg87zY2tQdcEKUWiVoxDffOA8jHNhjbkodDg8fABLI+QXnimmYL8YNADq9FQEQczfS1w4c4k2AFFxhilcGuhg4t6AOC+N39v4dCNR/nSCXUBfIg64TR3P3wy64BLQEXIrxy4RILiIjafea1zl/8SMvkZ/FQxXeWw4NQnTdsWfB1I6408YB0m4eKDgsYgn0ysllyg2wxFbYXTpwPIy1lnzhcEHG1Z+zbLSYqXlSm4GzI54XYFUp
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 19 Dec 2017 01:43:23 -0000
Received: by ary.qy (Postfix, from userid 501) id 32C181823BFF; Mon, 18 Dec 2017 20:43:22 -0500 (EST)
Date: Mon, 18 Dec 2017 20:43:22 -0500
Message-Id: <20171219014323.32C181823BFF@ary.qy>
From: John Levine <johnl@taugh.com>
To: dcrup@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwYm-Qq=+vZhbiJWB0p5W_pFWcqS5ch1czTwQ+o6YccQrg@mail.gmail.com>
Organization: Taughannock Networks
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/9FDw65_KiikHV87wbQdLbafksqg>
Subject: Re: [Dcrup] Working Group Last Call for draft-ietf-dcrup-dkim-crypto
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, 19 Dec 2017 01:43:26 -0000
>Simultaneously: John, your comments in reply to this? >> 1. The existing RFC 6376 signature algorithms specify what to use for >> hash- >> alg. That's missing from the Ed25519-SHA256 definition in section 3. As >> implied by the name (and discussed on the list), the hash-alg should be >> SHA256. Recommend replacing the leading sentence phrase in section 3 with: >> >> The Ed25519-SHA256 Signing Algorithm computes a message hash as described >> in >> Section 3.7 of [RFC6376] using SHA-256 [FIPS-180-3-2008] as the hash-alg, That's fine. >> 2. For clarity, per some of the IETF LC feedback on draft-ietf-dcrup-dkim- >> usage, recommend adding after the main body of section 3 and before the >> note: >> >> This is an additional DKIM signature algorithm added to Section 3.3 of >> [RFC6376] as envisioned in Section 3.3.4 of [RFC6376]. Also fine. >> 3. Private key storage format >> >> Unlike RSA, Ed25519 does not appear to have a standardized textual >> format. I >> think it might make sense to specify that for DKIM Ed25519 purposes the >> private key is stored as the base64 encoded output of the RFC 8032 Section >> 5.1.5 private key generation processes. This would provide a (slightly) >> human readable private key representation that could be used by different >> implementations so that operators can safely switch implementations without >> regenerating keys and that are more understandable for trouble shooting >> purposes. OK by me but I'm no crypto expert. Perhaps we could ask the openssl folks what key format they'll be using. >> 4. Examples >> >> It would be nice to have at least one signing example for implementers to >> use to verify correctness. I currently have either a signing bug or a >> verification bug in my work and I'm not sure which. If I had a known >> correct example to bounce my signing results against, that would help a lot. A reasonable albeit somewhat painful request. What ed25519 library are you using? R's, John -- Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
- [Dcrup] Working Group Last Call for draft-ietf-dc… Murray S. Kucherawy
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… John Levine
- Re: [Dcrup] Working Group Last Call for draft-iet… Murray S. Kucherawy
- Re: [Dcrup] Working Group Last Call for draft-iet… Seth Blank
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… Seth Blank
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… Murray S. Kucherawy
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… Murray S. Kucherawy
- Re: [Dcrup] Working Group Last Call for draft-iet… John Levine
- Re: [Dcrup] Working Group Last Call for draft-iet… Jeremy Harris
- Re: [Dcrup] Working Group Last Call for draft-iet… John Levine
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… Barry Leiba
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman
- Re: [Dcrup] Working Group Last Call for draft-iet… John Levine
- Re: [Dcrup] Working Group Last Call for draft-iet… Scott Kitterman