IETF Logo Mail Archive

Re: [Dcrup] draft-ietf-dcrup-dkim-crypto-00

"John R Levine" <johnl@taugh.com> Fri, 19 May 2017 18:48 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 ACA4A12947D for <dcrup@ietfa.amsl.com>; Fri, 19 May 2017 11:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.678
X-Spam-Level:
X-Spam-Status: No, score=0.678 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=X5Xd6sow; dkim=pass (1536-bit key) header.d=taugh.com header.b=Q1b1F3Ff
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 nDMUotrwb0RV for <dcrup@ietfa.amsl.com>; Fri, 19 May 2017 11:48:39 -0700 (PDT)
Received: from miucha.iecc.com (www.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 63ED71273B1 for <dcrup@ietf.org>; Fri, 19 May 2017 11:48:39 -0700 (PDT)
Received: (qmail 3479 invoked from network); 19 May 2017 18:48:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d95.591f3e06.k1705; bh=GpL6o6xbRXz1pDolvnXVvV/hDsvJNcWo+Pgp+95ADMQ=; b=X5Xd6sowchkQFtUd/qzeDPNmFBS5o1x+gHvLiDdwE6h6wzafRqnnyb6DVqQEBFS3kxwi3ix5I7XnORmKnz1uqK4ZL2irozk0slKj5T8NKRXdKw8KRaViHHm5KwMJ7n9FUdiifW1hbvGI7FKKZtF8vKymqY1hPDEcgoyjJnuZ9itDKoWXPPD5mHM9rJeBO+n+BaA1oNqV6/eYdKz2FjFLHmcurU5SrsUU7f9b0qoCd7ixrBWTOcqMmY4bhmLCuabb
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d95.591f3e06.k1705; bh=GpL6o6xbRXz1pDolvnXVvV/hDsvJNcWo+Pgp+95ADMQ=; b=Q1b1F3FfKeaRjzPLTe+hvxB44dDResJKMhv063ynw2mwlPBBei2TVgvoCQWyYaEiUSMGiNjpZW2QwAq6URXfBYzWbVUhOQ/QOEXtiQcTcerXivR+p/zqsq+zMQ95WKMM3hP47kt6heCQA0LSuz7gfGSioLq6mTIbthq8n/CF5JjW5FlIdEyepv/6uHMIa0lRYvXTRUu6Mq0d227np7uMGTuBHJPgvIz/EdeNHptHmUxxWrKdjBvuvDGFNG6I80S0
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 19 May 2017 18:48:38 -0000
Date: Fri, 19 May 2017 14:48:38 -0400
Message-ID: <alpine.OSX.2.21.1705191445560.6525@ary.qy>
From: John R Levine <johnl@taugh.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "dcrup@ietf.org" <dcrup@ietf.org>
In-Reply-To: <88797f820fc540debef7d0fdb5f4cc92@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <b4089f9898264ce8a638605fcb1f93a8@usma1ex-dag1mb1.msg.corp.akamai.com> <20170519155006.5267.qmail@ary.lan> <88797f820fc540debef7d0fdb5f4cc92@usma1ex-dag1mb1.msg.corp.akamai.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/jLOAHKxNZNVu2js7OU_C269jZBo>
Subject: Re: [Dcrup] draft-ietf-dcrup-dkim-crypto-00
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: Fri, 19 May 2017 18:48:41 -0000

> Speaking as an individual, I'd like to emphasize what Mark said.  ECDH is a key exchange protocol, not a signing protocol.  For elliptic curve signatures, the document should use https://datatracker.ietf.org/doc/draft-ietf-curdle-cms-eddsa-signatures/ which is now in IESG last call.  Note that the hash mechanism is implicit in the signature algorithm.

That's fine, like I said I don't purport to be a crypto expert.  Even 
better, send text.

> The key fingerprint needs more clarification.  For 25519 keys, there is 
> a "natural and obvious" byte representation, but for RSA keys what is 
> being fingerprinted?  The DER OCTET STRING?

IIM had key fingerprints.  Perhaps Jim can tell us what it did.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email