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 19:52 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 5278412702E for <dcrup@ietfa.amsl.com>; Sun, 11 Jun 2017 12:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 UZhrp57CaJHD for <dcrup@ietfa.amsl.com>; Sun, 11 Jun 2017 12:52:43 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 9D7C01200F3 for <dcrup@ietf.org>; Sun, 11 Jun 2017 12:52:43 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id k4so57946536otd.0 for <dcrup@ietf.org>; Sun, 11 Jun 2017 12:52:43 -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=hrfbHOqwHWrO5OQwl9eVpdCuuzej34z3GajxiIGMP0I=; b=V4PNIZDA38u70K3Q3tprFBsTCXw9S4uieVY8BJ4YV490B3TfPMCbytCwwd1gjnw6tm 6Lqv7cBPwAexSc98kxTTfSMcD7LabiU5GqkRlIexBD7K4IhpNapxHHUdFYk6KbzFK1XY xTddJB8lFPyvPwaiMLKWtP8fjOSckyJeNj85Aqxpvze2IsoqDPUCn8zeHgJL9TN5CEr7 Bw4O3/L9MsGArXBYEEnELzd3+7QdzUMN0LE0LM5/IaPt8rQCI/cyxIEhcgvUh5nNEa9l jEnitGOWksoUCZppc6/RYnD9LPzfEe3NfLJ5ZywCaIAUq9Pq/snh4WDnfrfcbHV5IPdR bsbg==
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=hrfbHOqwHWrO5OQwl9eVpdCuuzej34z3GajxiIGMP0I=; b=r0yYVnI2+6bR7p+kQsnxVA4nFqM2ZBANAw5xLI8Jy30hf1TbkQJo/n+a1Ie4PhQ2mn R2/rfqTdEIZztGrjKq6a21FZ9YYooNpWg2XsttvNwS78Qy16ZhdD3+e7dfDF93Ehq4Qm oQ3PwbDereY5Ts6NYyD9vVD9CdFco6Cca2wDlBM5ZBGKv34HNYhPskVsy0zsx9UDvjnR GYP71Xieqmc++2SGhSnlvbKM1j/M6su8k18I53FuLrwpdthS5KsYmWFtOCKP4vJGgVku qNqwrVfV82JirJ1NAzPQN+PZcRqDiMC9EqnMRfDRuL2J5/AEkUBiLE0QGbTBKzO63yXs 0PFw==
X-Gm-Message-State: AODbwcAl+/7zvAxfwR+LgUlUNVflZ6Xfe/q9WyJNvK5C6mXKVsT0xm1R V78+0G22rqRE57jGnl4TCGYjz2HQYQ==
X-Received: by 10.157.44.102 with SMTP id f93mr29390922otb.199.1497210762890; Sun, 11 Jun 2017 12:52:42 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.23.5 with HTTP; Sun, 11 Jun 2017 12:52:42 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.21.1706111953380.18312@ary.lan>
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> <CAMm+LwjwYtTj=GUM_KPewZCEnaWYyu=K8z4er9fG5E3tSJWv1Q@mail.gmail.com> <alpine.OSX.2.21.1706111953380.18312@ary.lan>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 11 Jun 2017 15:52:42 -0400
X-Google-Sender-Auth: N46-U7YHmTpG3TgPPM-NS15GV1A
Message-ID: <CAMm+Lwia4j+gAeurdz2kbwxNxvJVwqc7WuLJ95J2NPbPza-8VA@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: "dcrup@ietf.org" <dcrup@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0d5864ad13570551b48b72"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/D6kMt5SUD7Znmh1FdRXQYQ1oX0o>
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 19:52:45 -0000

I just want to make sure we are clear on that.


On Sun, Jun 11, 2017 at 2:54 PM, John R Levine <johnl@taugh.com> wrote:

> 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.
>>
>
> I'm not aware of any reason to use anything other than RFC 8032.
>
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail. https://jl.ly
>

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