IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Sun, 11 June 2017 02:21 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 A9FDC1294B8 for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 19:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] 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=3220nsfg; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=wbbkV2Io
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 jKb3vVCjEeKK for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 19:21:36 -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 0451B1294B2 for <dcrup@ietf.org>; Sat, 10 Jun 2017 19:21:35 -0700 (PDT)
Received: (qmail 40046 invoked from network); 11 Jun 2017 02:21:34 -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=9c6b.593ca92e.k1705; bh=N/qFQ1B92qHqy13bBAjbyzV/V/KN4us3YbX3DO7BaXs=; b=3220nsfg1w5+SMZhaEIbwWaiRsBOpw7X36B/mkNgtHMUz7gWaTboHTmZQhUavNq4mHTpQYhYWRXII8YQC7Rr0zmcbvTRTgh/LEJOOfHVgNB6vig9q9ky+dHRNRTXAt8xP+GWP/hYUiHrfE2/QkYvAgx3xvHC+zH1361xMuwL4nkh6Dh/wrLU6etWa0/886ERP6eaQO9qz6ozLNRShEeWFrUgQ3xae2/rW9N1BMbcGSVdD0sEpHC4E9W4OygJddlT
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=9c6b.593ca92e.k1705; bh=N/qFQ1B92qHqy13bBAjbyzV/V/KN4us3YbX3DO7BaXs=; b=wbbkV2IoTylauFrakcxYy9gx+vlyrGIcdDIgqD/eD4HrdDw6B6CNVMYCArs79lfS8X3RiGsislX12xyiNmCSV0CQNODOn6zJxL1sUc7xl096Pe6VjJFYNbtcGy4QHqnqR7zoHZMIPi55sL/VYgFAOX6OWSKqXm5kZPN0arnVVIhWnjcOQZquGBUNxLm8BPREUCiC1dSd7obfrncYqqOF5CC+mbHzjcbQVZ9PcuTqy7vXltp/4dngIdc+BJ5hTVpd
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; 11 Jun 2017 02:21:34 -0000
Date: Sat, 10 Jun 2017 22:21:43 -0400
Message-ID: <alpine.OSX.2.21.1706102220360.17881@ary.local>
From: John R Levine <johnl@taugh.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "dcrup@ietf.org" <dcrup@ietf.org>
In-Reply-To: <d1496579f43f41dc9cda7cbe2f043a9e@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>
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/I4lLxtSB_5SiENRjwf3Ez-Eccvs>
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 02:21:38 -0000

On Sat, 10 Jun 2017, Salz, Rich wrote:
>> Since we have a lot of lazy programmers who will need to do this, how
>> different is ED25519 sign/verify from RSA?
>
> Rough estimate:  every time you do an RSA thing (load key, sign, etc) add an if test and six-10 additional lines.

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?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

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