Re: [Dcrup] Hey, crypto experts, what signing algorithm should we add
"John R Levine" <johnl@taugh.com> Sat, 10 June 2017 16:07 UTC
Return-Path: <johnl@taugh.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 0849D127076 for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=iecc.com header.b=lz6xhIvU; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=jv+M0iet
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 vXjM1FG4AP5L for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:07:40 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07B061200E5 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:07:39 -0700 (PDT)
Received: (qmail 81570 invoked from network); 10 Jun 2017 16:07:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=13ea0.593c194a.k1705; bh=7ao1h2odoVh+QM7PWIWjBlVfGaIWiDd8PIL3E9ZDEig=; b=lz6xhIvUH5156sdiaIIg00PT94P/8JtjqIfw1RqURdOqm3ubowXSokUr6QmKcCaGxOeXwzWNmRqF7L5K43bKCaLMP+q/+99ZUiZYl7L1b3myUEob1qpOE8+TNauIMVLQYpL4NTVbC7plrL+eve3gyyzJYAD0udJTKucNzOH/S8JzXPBZl2/QJZ1ZH7ZV7hVksPK5ze+TGfS/DHneX7CJgabsNkr2A4+XPcNQ0+iGXZ4sd5URSesg4HuTveEBTzca
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=13ea0.593c194a.k1705; bh=7ao1h2odoVh+QM7PWIWjBlVfGaIWiDd8PIL3E9ZDEig=; b=jv+M0ieteMusBk7pCs0skT0eCifvoUZnKThJvl8cxn8Zc0/DchbtUkgGnWyYNOVZTAi8J0XZfbll21BFBZl5Ew4na+eyBoNHrU4Jrha2Lb9x5BB3/1Ey3lkS4Yo/52u5R7pGECGYXVmNhdVY8uf+JQYUZwNcbWikGXqYkD1hO0SPNHUFMNG6I2e0jNY/RAVnL9nC72E3PndYfIt8Q66FBoY6gtL8ACK15twHiGOMKLW1xtba3fCGMe4k5dYm6aSD
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 10 Jun 2017 16:07:38 -0000
Date: Sat, 10 Jun 2017 12:07:37 -0400
Message-ID: <alpine.OSX.2.21.1706101205270.16559@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: dcrup@ietf.org
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>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/NX3WBZlDjVnygisM_axTpDw8TOs>
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:07:42 -0000
> 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. 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