IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Sat, 10 June 2017 17:48 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 897D51270A3 for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 10:48:31 -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=gxqa2b40; dkim=neutral reason="invalid (public key: not available)" header.d=taugh.com header.b=Bdgfn2O6
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 NeEnU5Zdr6Iw for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 10:48:30 -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 DC1C7126DC2 for <dcrup@ietf.org>; Sat, 10 Jun 2017 10:48:29 -0700 (PDT)
Received: (qmail 90475 invoked from network); 10 Jun 2017 17:48:28 -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=16169.593c30ec.k1705; bh=qf6kwkZOACvbHR6+ppB3/4K4HcfnfhN8l4vRVgdFAhk=; b=gxqa2b40l+d0/TJe0nLYGPSv7VZloqOK5TJi0FT36eXEy8sBxbBNFc3HN+/6+D5ObV2WnzA+k3d3NCDLLS2U/fzey0yrnpA7vVb5iCNodK9W4MoFnNsRFbZYEoTtjNJsjdX0GUfs64cMXASzIPqzfDEDybEPHgTerGfnn/nVV1xfzEPuSUrhMP7Lj+T1EwnJN9AosI8daizdBF1+KHCfodQbPH1rKi26mBXr4z+wIpv4w0+8zuQqIBTBVdHAA+ya
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=16169.593c30ec.k1705; bh=qf6kwkZOACvbHR6+ppB3/4K4HcfnfhN8l4vRVgdFAhk=; b=Bdgfn2O6jByxPvekb6WZ6SApelCrr2vsA24XAeE1h92gOgtkCX/VBtgzRltKpE4/uEAdmuxrfc6+tSkhNpaxTLpvNMNZvlh6eq2DOUizB5bufJU8jc4nO7NAxAfD4u/EZSEGd4Py/HXLwSv4Ot4H+LIyEiX+Yn9hbS9Ds4gQ7pk8BmfqqX1l5x3nXhG/N+1ejZ4cpqiFBIQxl/SdsOujYgCanGtalwE53GWPOuwqEDYm/XSQso8a7kBjfFE6bFpZ
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 17:48:28 -0000
Date: Sat, 10 Jun 2017 13:48:28 -0400
Message-ID: <alpine.OSX.2.21.1706101344460.16992@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: dcrup@ietf.org
In-Reply-To: <CABcZeBN9r9XdsJVayMcUE03WJv74MOsefVdwb-CdchVbaKdT1Q@mail.gmail.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>
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/CgL-XMN_P1fMSF7PLAh4EESry3o>
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 17:48:31 -0000

> Hmmm... That's not really part of the standard RSA signing interface that
> I'm familiar with. See for instance [0].. Can you send me a pointer to what
> you have in mind.

I do this to generate the key:

$ openssl genrsa -rand /dev/random -out key.example.com 1024

$ openssl rsa -in key.example.com -pubout | munge > key record

where munge removes the BEGIN/END PUBLIC KEY puts the key on one line

Somehow that blob includes the key length, since I can change the length 
and the signing and validation code is the same.

For the interface, it would be nice if the EC key were similarly 
self-describing.  Or it may be moot since the key sizes are fixed.

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