IETF Logo Mail Archive

Re: [Dcrup] I do not like the dcrup ECC document

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 10 July 2017 06:50 UTC

Return-Path: <superuser@gmail.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 ADA5E12708C for <dcrup@ietfa.amsl.com>; Sun, 9 Jul 2017 23:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 uB5JoOCoGY6R for <dcrup@ietfa.amsl.com>; Sun, 9 Jul 2017 23:50:43 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18C8C126CBF for <dcrup@ietf.org>; Sun, 9 Jul 2017 23:50:43 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id r126so42230052vkg.0 for <dcrup@ietf.org>; Sun, 09 Jul 2017 23:50:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PTjoCZRVn0g16v+/Tsw+k1vtrSlWMs841MiIYG07CoA=; b=aobF8jpHxh/l6KFhxK/YjIO6eQeFFsKV+gN1VnKiOKSyDD+vGHCIC+Nz2ULIdCUFPw nqDSTaWZ0GfTEJD4T9+6OuJeQTebtZvVwT8+rxRy7rnytui2t9C7dtlEKP7oPvfw0ECM Fwgax1fXRDEpFSLcgj0/lMc+L1z9tyjWAc1ZtiSz7aHDyQn1Wayp5Ev2UxaCnYSBFc1k 5Z3DgqSNCF3r7dHQNdEEG367LsEx9qFc4rxAUoj8SnGI8hOxOeiLzK7lOk4GTzNV1C4t rvkF4YMVrjKntVcr+YfwL3vzf+C4Pk1ZOKfoje/kvyuhB1sa2f+Bk9mMzPQ22giq2Ccg 7xDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PTjoCZRVn0g16v+/Tsw+k1vtrSlWMs841MiIYG07CoA=; b=sqBCWydq7TZLS3qTOcGdPyhXOEletBQ4My2LFIijwpG73mp00r10qltSMm9BOsfVKC t4oNHe6Tx9XlzOItmIxX117sCtTjGyONzfxYcNNKiez5mvOZ5sasfoTk0pKn281HiZ7o dHCbfRWy/QRN90AmXx0jqWWZjMJUgovTXHeIV/6m39hkk0LgdaQD96R5aL3ooSl3WdAA z/t8hPSXdSdumn0h9efN6ue1VAYWYQUGvVVkxXy+F0CJ+z+RWchsACT48Net6U5GQ53o jZxQ8zgbetqfiZDkcfI5IWZ5IXpESQT+dpJsqjQy70qWkBTY2ZKjx5gS3M7JEIAFX+sT qsVA==
X-Gm-Message-State: AIVw112D/Uq62Sq7URTqfrmmoL4m04d2JOnIxPwsebA+Q1fLnHWfbbdi sUxES8KLbzSioIIMOcdTFlJOdaoY8/gT
X-Received: by 10.31.154.150 with SMTP id c144mr3958350vke.125.1499669442083; Sun, 09 Jul 2017 23:50:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.126.196 with HTTP; Sun, 9 Jul 2017 23:50:41 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.21.1707091702130.6209@ary.qy>
References: <20170709203414.90415.qmail@ary.lan> <3A2ECF01-E8A0-4E11-9E3F-6A67C5198ACC@vigilsec.com> <alpine.OSX.2.21.1707091702130.6209@ary.qy>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Sun, 09 Jul 2017 23:50:41 -0700
Message-ID: <CAL0qLwZnmWVzVTNyK7F7paotoG8NmM=0yOOZiqtTP4t-5aQrsg@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: Russ Housley <housley@vigilsec.com>, dcrup@ietf.org
Content-Type: multipart/alternative; boundary="001a1140f7106042190553f100d7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/DS7nOwH24KAOt6AGOCMLDG9ZGDM>
Subject: Re: [Dcrup] I do not like the dcrup ECC document
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: Mon, 10 Jul 2017 06:50:45 -0000

On Sun, Jul 9, 2017 at 2:14 PM, John R Levine <johnl@taugh.com> wrote:

> RFC 6376 describes in great detail in section 3.7 how to create the
> material to be signed.  What it ends up with is a sha-256 hash, but that's
> not the signing algorithm's problem.  I say PureEdDSA to emphasize that it
> doesn't get hashed again.
>
> As it stands now, the RSA and EdDSA signing algorithms sign the same
> thing.  I suppose I could extensively rewrite the signing instructions so
> that stuff to be signed by RSA is hashed while stuff to be signed by EdDSA
> is not because it'll use HashEdDSA, but that seems a lot of work and a lot
> of code changes for no benefit.
>

+1, unless there is such benefit and someone could describe it (or point us
to a reference that does so).

-MSK, participatin'

v2.28.0 | Report a Bug | By Email | System Status