Re: [Dcrup] Hey, crypto experts, what signing algorithm should we add
Eric Rescorla <ekr@rtfm.com> Sat, 10 June 2017 16:09 UTC
Return-Path: <ekr@rtfm.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 87B0C124BFA for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 0nDfRChAPSNr for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:09:00 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 D032E1200E5 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:08:59 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id e142so19352594ywa.1 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YJDoJ73y5wxD198hIZ+bJb9ysgLDdTg8NS0gsPQ/nRE=; b=KflDMRi6X9tBb9t9ilM/J2Kf81vo8YEAyBLIPo0vkhWh9qtIVGVxwmQQSNVgPRl3XV J7KBz3fPD0drcFJLDoUYridUztSXm2C7/v7qDaMefd+UG1oUFH37DSMxZo9qFLzt5O9/ Wa2h3qmJb7t8I/ZotlnFQeWWYBOK1zcgOmRo4psczCAnRBGibSPeJUy8gJ9rMk5RyGLD OEFmMVNSgIvaI/xe1suI35+5VMKiJgHSMFsJp9mhn9Kcrif8bpQoeZoFedlCmPPaKyga WzgPWQpxQETvw+tdb0CWSNzZuXWGPwvJfo4ZOd2Iu60aQCWfd/9AVrY3y+N3ulXAdOQy OlAQ==
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=YJDoJ73y5wxD198hIZ+bJb9ysgLDdTg8NS0gsPQ/nRE=; b=I9aGUrUb2FL24HUYWD+ZmsnQyD9BqmGRguFV9HXUuQBOgrxNjxkgrVlqrVtKuVpSpP 2TG/DIMPFUh851WcwZldC7V7+5X4FO1Nzr5HdqM73564PDyWAfdN5rpX/t3OfZKN4RFk Kd3jLzhEBgzuqwEDcR2zexBuEQRR+i2jp+Mw+4Ys677/dMeYqLP6aQ7J7yWmK8gS9+Y0 5tj04YB97g97o49hE/V7YXqQrCriCQQtGApgeWGV0yLnP2YEdVpNWv4y7aiz5+cL7EyJ fj83TLEMWMlpxi2FlKasJmpJc8CH6ee8BuR8jWEsRRpSLvzadT8x1iHzmesgbr55/o+3 Bltg==
X-Gm-Message-State: AODbwcD1Gp7RwUta710/SW6/j32ngQwqEs5dym3Nb+2JAAT8xmJa7uNW KUJm3aFMsFbRjG43Sc071lWcWHHi3PkEDNg=
X-Received: by 10.129.97.195 with SMTP id v186mr15832825ywb.270.1497110938957; Sat, 10 Jun 2017 09:08:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.215.144 with HTTP; Sat, 10 Jun 2017 09:08:18 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.21.1706101205270.16559@ary.qy>
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>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 10 Jun 2017 17:08:18 +0100
Message-ID: <CABcZeBM_P4C8xYDmMEbhAbs1tVPVWk6+UgT7vAcktSNtjVyXCg@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: dcrup@ietf.org
Content-Type: multipart/alternative; boundary="001a11490122b4d9bf05519d4d06"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/hwEfM8b45uQOTGFeIXoipRsLjBw>
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:09:01 -0000
On Sat, Jun 10, 2017 at 5:07 PM, John R Levine <johnl@taugh.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. >> > > Great. How about the sign/verify interface compared to RSA ? RSA has a > length parameter but I gather that's in the blob of base64 key info. > I'm not sure what you mean by a length parameter. Length of what? -Ekr > R's, > John >
- [Dcrup] Hey, crypto experts, what signing algorit… John Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Martin Thomson
- Re: [Dcrup] Hey, crypto experts, what signing alg… Eric Rescorla
- Re: [Dcrup] Hey, crypto experts, what signing alg… John R Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Eric Rescorla
- Re: [Dcrup] Hey, crypto experts, what signing alg… John R Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Martin Thomson
- Re: [Dcrup] Hey, crypto experts, what signing alg… Phillip Hallam-Baker
- Re: [Dcrup] Hey, crypto experts, what signing alg… Eric Rescorla
- Re: [Dcrup] Hey, crypto experts, what signing alg… John R Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Salz, Rich
- Re: [Dcrup] Hey, crypto experts, what signing alg… Mark D. Baushke
- Re: [Dcrup] Hey, crypto experts, what signing alg… John R Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Salz, Rich
- Re: [Dcrup] Hey, crypto experts, what signing alg… Scott Kitterman
- Re: [Dcrup] Hey, crypto experts, what signing alg… John R Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Eric Rescorla
- Re: [Dcrup] Hey, crypto experts, what signing alg… Salz, Rich
- Re: [Dcrup] Hey, crypto experts, what signing alg… Phillip Hallam-Baker
- Re: [Dcrup] Hey, crypto experts, what signing alg… John R Levine
- Re: [Dcrup] Hey, crypto experts, what signing alg… Phillip Hallam-Baker