IETF Logo Mail Archive

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

Martin Thomson <martin.thomson@gmail.com> Sat, 10 June 2017 16:38 UTC

Return-Path: <martin.thomson@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 ECF6A126E3A for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 6bTFzzZwh5Ic for <dcrup@ietfa.amsl.com>; Sat, 10 Jun 2017 09:38:02 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 B1D3A1200E5 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:38:01 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id p189so38834523lfe.2 for <dcrup@ietf.org>; Sat, 10 Jun 2017 09:38:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fThr0Wwq3cZQqDg2DZmf6Dv5br6q6dmoHJlRShEu/qk=; b=fr2lBYUwZEEXfXFZjgLk1x7YTz+Jz7IaMg3tda+6FMyOE373F6AB9obre4KuWjbtlc qXO5sSszElqGRvLeqwX15GSSfF807x0x0cyybV+TDxM4DVZIR0V77flM8F28WESP95cF HS7+m0YD/f8MELgY7/1Xiw9DjX6VBavS2X+3fBrdwWI8DzRMWm/FqzRQzOB9QSUf1vmT AZ4LJHtOuJVgP2IYjJG3myAonF+7j4ifCoEHl5djr1K19OruwJHVC46DjGxYWey+HTi9 KItyuECOzob5LnOSDZb7v7qgzzyBZWruiLgFDMmY8yBkINEfvkTs/17a4CNOjtjV6B6V 7wAQ==
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=fThr0Wwq3cZQqDg2DZmf6Dv5br6q6dmoHJlRShEu/qk=; b=iT2miW8rv/zJSCe/46EOiRaVVAU0GveZOxrh2e1l3OCPCVQBNX+/OQqws1UtyywdtC xOsR+MKAwegG7djS7RNu5Oo5YdkSgHDDLogOtwjvHHL+av5lOZOepnruRNRrF7zDidL+ m2qXRUFYCosmSfhbmlWtrvmYDO5NreAVCvQZMAjsYKGtdv/PVVIxr2pnAqCfO0Z3HSxA ndNzetqPHtF1AQ8cv9cn+A7pmwuwQbKwyaEAa5oxQCwVii0RsjWufZfx3kdjC8otH4JZ MqQ7d2sYX1LOJeV18/gYAp6hT03WH/cYCyPe5vE9rpfGdiE9Y2caABzkf7mbdCiXQ1ZJ D73g==
X-Gm-Message-State: AODbwcB6ugTswjMEdu6QXOD7LklhZ0kw3Yri6TZevjPonmzf3xapWyhX Cj077ciztjDwqcywOGPUuvgX2LzYjBMx
X-Received: by 10.25.201.18 with SMTP id z18mr11278604lff.172.1497112679998; Sat, 10 Jun 2017 09:37:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.8.66 with HTTP; Sat, 10 Jun 2017 09:37:59 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.21.1706101211200.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> <CABcZeBM_P4C8xYDmMEbhAbs1tVPVWk6+UgT7vAcktSNtjVyXCg@mail.gmail.com> <alpine.OSX.2.21.1706101211200.16559@ary.qy>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sat, 10 Jun 2017 17:37:59 +0100
Message-ID: <CABkgnnUQHcOtt3haKpr0mXbpYKoxyKtWc_TvmUwxfS0FTotvMw@mail.gmail.com>
To: John R Levine <johnl@taugh.com>
Cc: Eric Rescorla <ekr@rtfm.com>, dcrup@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/bIDFvtbAhjx5Z0vRcRbOLAFeRXw>
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:38:04 -0000

On 10 June 2017 at 17:11, John R Levine <johnl@taugh.com> wrote:
>>> 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?
>
>
> The key.

Well, keys are fixed size, but you could include an argument if you
need to have a consistent API.

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