Re: [Dcrup] EDDSA implementation question
Martin Thomson <martin.thomson@gmail.com> Tue, 20 June 2017 01:47 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 2BB061318BE for <dcrup@ietfa.amsl.com>; Mon, 19 Jun 2017 18:47:11 -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 xJzQqFEa3QjX for <dcrup@ietfa.amsl.com>; Mon, 19 Jun 2017 18:47:08 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 702BC131537 for <dcrup@ietf.org>; Mon, 19 Jun 2017 18:47:08 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id o83so65274833lff.3 for <dcrup@ietf.org>; Mon, 19 Jun 2017 18:47:08 -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=Swn1eZqWGgFHufyerNwDnoM/Oo0d/oI8cqn70kI6aWw=; b=I14p9okJc/eNW2ldMQKC0ObXd38Og0Vay8WTXtq4dWqfAiX5JCkfgBH51eMFnvfv6c 5bzITj7ie9+lK2+zIjwifqlaKIVuxHWtaDXqGG2Ib1/HdyHKEyPFgaicTLut+agoN0fW 12OZrxH60vl3pM2w6B6a2LCZ2d2bBNw1y7t1XeV6wvLjDz+MGyTaEnmmRGWiHY8XtBMj zbvecCvmh9Z6fZaH0C7uHH4MBlKSZyPTW95RfRk6F2Qo3hTkbhkNZtkWa7Ua66nxyy/x kdGBKzVpAI8klPRs925wLDxFcgV/eVjUNhOF+5BWtGWcjjpgKYx3dpEug3SJCjinHHsr ldww==
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=Swn1eZqWGgFHufyerNwDnoM/Oo0d/oI8cqn70kI6aWw=; b=kqFGqJJTis+mKBHOasdMmolhcCDve/qFXnHeJXtGUBHIZFpSRPhRANAJ37DLBwHgHP MdLAEmytF2KEp4DPDdwgMT9zrI5Z+iUCTCCrFBXgjgYWv80UsHo5LyRijB3sVYmqGqZT U1he5yh/IqzsbCN9R2MQbBHSsZ+iEvmI0w1PwgRpQrtq2VSysR7MGTNI6o1eLy9dO9u/ yNU+0p+IthPox9+7iP2Ma2h0x3NOXrHkOiKLDIMHGZQW+5H+4eqMECMegQvUrrCw/aRK uUWD6YTfpAIiJTb/BPSv15LKxAHWTztBKjNYvX1XFpqd5Xb4u4uh5THHyQRQ2mLLlsvm XpBw==
X-Gm-Message-State: AKS2vOxgV8DjqdpvjiSVVZuB3G5T97EHeCHwkMciuQWyVNn8UigPeU2d HekX5J8KLVffoMEZi2Bm8UYr7wMsl/Z0y/8=
X-Received: by 10.25.201.18 with SMTP id z18mr8678988lff.172.1497923226738; Mon, 19 Jun 2017 18:47:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.78.17 with HTTP; Mon, 19 Jun 2017 18:47:06 -0700 (PDT)
In-Reply-To: <CAMm+LwhApVD-xbfvHf7GJvC2EK+5EOePU7ww5sCV0ckE+LCC7w@mail.gmail.com>
References: <20170619205416.10860.qmail@ary.lan> <CAMm+LwhApVD-xbfvHf7GJvC2EK+5EOePU7ww5sCV0ckE+LCC7w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 20 Jun 2017 11:47:06 +1000
Message-ID: <CABkgnnW6TzykXWNuKiuE-g00JsTaWNMh9gajQK8MrA3X7X8mWw@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: John Levine <johnl@taugh.com>, dcrup@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/MgbNawpjw2jeiGOM6V6687MmGxk>
Subject: Re: [Dcrup] EDDSA implementation question
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: Tue, 20 Jun 2017 01:47:11 -0000
It's not clear that the code in the RFC is free of side channels, so it's probably not fit for use other than for verifying correctness of outputs. Note: This code is not intended for production. Although it should produce correct results for every input, it is slow and makes no attempt to avoid side-channel attacks. On 20 June 2017 at 11:42, Phillip Hallam-Baker <phill@hallambaker.com> wrote: > The reference code in the RFC is python. > > On Mon, Jun 19, 2017 at 4:54 PM, John Levine <johnl@taugh.com> wrote: >> >> If I wanted to work on, say, updating the python or perl DKIM >> libraries to do eddsa, which crypto code should I use? As far as I >> can tell it isn't in openssl yet. >> >> R's, >> John >> >> >> _______________________________________________ >> Dcrup mailing list >> Dcrup@ietf.org >> https://www.ietf.org/mailman/listinfo/dcrup > > > > _______________________________________________ > Dcrup mailing list > Dcrup@ietf.org > https://www.ietf.org/mailman/listinfo/dcrup >
- [Dcrup] EDDSA implementation question John Levine
- Re: [Dcrup] EDDSA implementation question Scott Kitterman
- Re: [Dcrup] EDDSA implementation question Peter Goldstein
- Re: [Dcrup] EDDSA implementation question Phillip Hallam-Baker
- Re: [Dcrup] EDDSA implementation question Martin Thomson
- Re: [Dcrup] EDDSA implementation question Salz, Rich
- Re: [Dcrup] EDDSA implementation question Scott Kitterman