IETF Logo Mail Archive

Re: [Dcrup] Hey, crypto experts, what signing algorithm should we add

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 11 June 2017 18:44 UTC

Return-Path: <hallam@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 F070A1279EB for <dcrup@ietfa.amsl.com>; Sun, 11 Jun 2017 11:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level:
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 5ps7FpsgtWfS for <dcrup@ietfa.amsl.com>; Sun, 11 Jun 2017 11:44:38 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 E9920127419 for <dcrup@ietf.org>; Sun, 11 Jun 2017 11:44:37 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id s64so3214971oif.1 for <dcrup@ietf.org>; Sun, 11 Jun 2017 11:44:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=kPytU6TCs498+DJidWOzVrYwDAIzPH0ia8UIOaYqjz4=; b=Gzz3K8b20J9v9nw6+xCqOKx4inPOl6U2zyjvkcCgj3ivkp1TWjeTC5qjIncoRKUbqi eaqZ5jl1lEzGhtZhUs9nJXttA9LUkWYT7HlYmZriP0arWCCQM4dBqjwU50RMxUiyJlWs naaU3k0vGRtvgcY7c+o9Oyx/O013VaUDlJLnT4uiUsRWyTN5G0weyiyuv82/9PhX8pJE W7WoLzJ96UGwydZ59Z1rH2OsIXxacpdBKYAJD2rNqPu6oQ04HCutHl6ELZN1AytOlJVN hcW2ToPoDATZJY3dfhV4j/cEqDLHPoLog6fu8A/UFCdIIBLL16/7LI1vxeA+vvjQpVsO AFgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=kPytU6TCs498+DJidWOzVrYwDAIzPH0ia8UIOaYqjz4=; b=ETHfDk8g3kPU/EHHLYqd/Ziq5uvb8yF5EEfAfK1GyRsugEt2gV6Yf6qI5EcNQQHhnK uNLwqD4dRrz3vm7HEE6bIcHUjBLzocHoEdcmRYS8vJUqhFnYvGyohNG98BBPvatlKDFZ a8B+V9Q+Vvife3wehZLPn3DDT3FVcKnGix0i8knckyVd9x0zb6HZyZ3WGYtM3XwqS++O G6MPyXIBDd4xNVUKF+ormHs8yVVmlXm+KGwE2+ZLXXRPkYK9flh3XoJSlPZSBJ8C0I8a t2TbxD77DGil89bE6RU3C4LFB8zvCBizLSy1jbnRkbEFCRk3qpRxmT/4vNrA6i98npCE rzCA==
X-Gm-Message-State: AODbwcAgaSVRddG/vAGkQY2VqXE8FVhuYbe5Yg4x177ZgRr/WQ2/D8qP pQXVrHv+i7vbhayf0TICUr4NaK5rnQ==
X-Received: by 10.202.64.131 with SMTP id n125mr20555371oia.154.1497206677392; Sun, 11 Jun 2017 11:44:37 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.23.5 with HTTP; Sun, 11 Jun 2017 11:44:36 -0700 (PDT)
In-Reply-To: <152cd69567124a1aa2fec7fbe63c936c@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <20170610125545.14232.qmail@ary.lan> <CABkgnnUAJ6ix3pMB_Y792QOCqRSp2qA9oTSyUCbXP_=P5HRwGA@mail.gmail.com> <CABcZeBMAmjVaJCJwB-qZSpTX0aS-oi1mTduHCdLCM33dWj9P-Q@mail.gmail.com> <alpine.OSX.2.21.1706101205270.16559@ary.qy> <CABcZeBM_P4C8xYDmMEbhAbs1tVPVWk6+UgT7vAcktSNtjVyXCg@mail.gmail.com> <alpine.OSX.2.21.1706101211200.16559@ary.qy> <CABcZeBN9r9XdsJVayMcUE03WJv74MOsefVdwb-CdchVbaKdT1Q@mail.gmail.com> <alpine.OSX.2.21.1706101344460.16992@ary.qy> <e867f8b5b99c4b498b80c6f851fca175@usma1ex-dag1mb1.msg.corp.akamai.com> <alpine.OSX.2.21.1706101527500.17660@ary.qy> <d1496579f43f41dc9cda7cbe2f043a9e@usma1ex-dag1mb1.msg.corp.akamai.com> <alpine.OSX.2.21.1706102220360.17881@ary.local> <152cd69567124a1aa2fec7fbe63c936c@usma1ex-dag1mb1.msg.corp.akamai.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 11 Jun 2017 14:44:36 -0400
X-Google-Sender-Auth: elOCJ3aVjMWf98GImdFqscfJ8eE
Message-ID: <CAMm+LwjwYtTj=GUM_KPewZCEnaWYyu=K8z4er9fG5E3tSJWv1Q@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: John R Levine <johnl@taugh.com>, "dcrup@ietf.org" <dcrup@ietf.org>
Content-Type: multipart/alternative; boundary="001a113de01429548e0551b39850"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/CGVP5LPh1uw9pNY93i1DHaWNDzw>
Subject: Re: [Dcrup] Hey, crypto experts, what signing algorithm should we add
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: Sun, 11 Jun 2017 18:44:40 -0000

Which flavor of Ed25519?

Are we talking about RFC 8032 or something else. Because there really needs
to be a very very good reason not to use the standard as written.

The amount of code that needs to be writ is irrelevant to me. People will
have to write code whatever. It took me a day to write RFC8032. It will
take a lot longer to write a spec for anything else, do test vectors, etc.



On Sun, Jun 11, 2017 at 1:43 PM, Salz, Rich <rsalz@akamai.com> wrote:

> > If we want to add ED25519 as a new algorithm, can we just say that you
> use it
> > where you would have used RSA, with standard base64 formats, and the
> > discussions about key size don't apply?  Or do we need to say more?
>
> That should do it.
>
> _______________________________________________
> Dcrup mailing list
> Dcrup@ietf.org
> https://www.ietf.org/mailman/listinfo/dcrup
>

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