IETF Logo Mail Archive

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

Phillip Hallam-Baker <phill@hallambaker.com> Sat, 10 June 2017 16:49 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 DF0C0127076 for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 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, SPF_PASS=-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 dQuMC2yr5Fie for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:49:37 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 584B71200E5 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:49:37 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id o65so40437082oif.1 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:49: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=hoSAjWJ2PPIIk9AHg/1tYvcC19tfMnjYSwljqv4m0OI=; b=OSI3nXh35zkhoxCMkECOv/oWwfZbgo3BuioTBC8oLYgdWeI4tXEgPrvwWkieQLdeuQ RQeGKnaZCHdufsAI5a7QubCENKFduF0Fx1v/qNgKg466jLfS0Dcr1jmJZ+RBz7jUzH97 R6S3rUc5TgI5I0BKoTmVk6uD+2Ska2l/8g9hifAyVtzE3VfKwhW7tGgQB6wEzDF+zuFw frnF8MPFScXj3wBf1hho8gsO0OUHe55wDVQ5edzIZPCHVvYtjBTq+9j7HWC6ATWG1NIZ aD2QPuXE/b9A/jXq51MlxDXyt8Jg/k3FD8MphAF+k4Q0BAAlZmUd8088Wk26CVCoAvp/ Rjpg==
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=hoSAjWJ2PPIIk9AHg/1tYvcC19tfMnjYSwljqv4m0OI=; b=oub8xEyMqXcon6pUQ+tmV7tWXrAakBLQq0oJ0fp4jHM17GjWEASbFgWJbVdHKOEzG3 7WfYKZo7hU2GIGCyAVhYNU0wpWcBem4RI4shYdFaPoriPY+n0zRrrfd1QV08lWX8vMeh EEra207akAVLlTNXKL4J0PJ+Q9NaBTdIT0H0gOpDrZMD34OT7/LGOqZeLvEDAGu0kbLI 50AzBXZQfnvUfEYz4NAWy+O/JWJo11wBJ4ci7xA5JYIVLHhQm1ZouohSLNUwdEfX1Vob BSrjMr9669GRL8Ye6J4dys0Wcw/UZnvJ8bPOM2ADyxscSseI8k7zl5ZnjtbnVP0TZpa5 fLEA==
X-Gm-Message-State: AODbwcAGpo7xA0X90IAUDjUq7z7bZdGm1rY8HckmYTxVcPTXGMpefJoT T5NZVkhk3MCcP6upkHC4m2Wai6H9vQ==
X-Received: by 10.202.220.67 with SMTP id t64mr21691293oig.134.1497113376783; Sat, 10 Jun 2017 09:49:36 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.23.5 with HTTP; Sat, 10 Jun 2017 09:49:36 -0700 (PDT)
In-Reply-To: <CABcZeBMAmjVaJCJwB-qZSpTX0aS-oi1mTduHCdLCM33dWj9P-Q@mail.gmail.com>
References: <20170610125545.14232.qmail@ary.lan> <CABkgnnUAJ6ix3pMB_Y792QOCqRSp2qA9oTSyUCbXP_=P5HRwGA@mail.gmail.com> <CABcZeBMAmjVaJCJwB-qZSpTX0aS-oi1mTduHCdLCM33dWj9P-Q@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sat, 10 Jun 2017 12:49:36 -0400
X-Google-Sender-Auth: bdbovqT3G8OQ8N3NqFgLaNWXbuQ
Message-ID: <CAMm+LwiUvtPrLJBto3tyMFVvAooEiub4vHbpP9kgmzKo=agjfw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, dcrup@ietf.org, John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="001a113d21a20302a405519ddfef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/6GU3KIP6N7UuBqT8UPsD0NUJ8Lw>
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: Sat, 10 Jun 2017 16:49:39 -0000

I think IETF is pretty much set on the 25519 approach.

Use RFC 8032, it is what it is for.

On Sat, Jun 10, 2017 at 10:52 AM, Eric Rescorla <ekr@rtfm.com> wrote:

> I think clearly either Ed25519 or ECDSA P-256. Either seems fine, with
> ECDSA having an advantage on the availability and Ed25519 an advantage on
> the modernness.
>
> -Ekr
>
>
> On Sat, Jun 10, 2017 at 3:51 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> On 10 June 2017 at 13:55, John Levine <johnl@taugh.com> wrote:
>> > Any suggestions?
>>
>> I thought that you had already settled on Ed25519.  Availability is
>> the only concern of note based on your criteria.  We don't have it in
>> NSS (yet) and it's a bit green in some other libraries, but it's still
>> pretty widely available.
>>
>> I see no huge motivation for Ed448 or ECDSA at this stage.
>>
>> _______________________________________________
>> Dcrup mailing list
>> Dcrup@ietf.org
>> https://www.ietf.org/mailman/listinfo/dcrup
>>
>
>
> _______________________________________________
> Dcrup mailing list
> Dcrup@ietf.org
> https://www.ietf.org/mailman/listinfo/dcrup
>
>

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