Re: [Dcrup] EDDSA implementation question
Scott Kitterman <sklist@kitterman.com> Mon, 19 June 2017 23:27 UTC
Return-Path: <sklist@kitterman.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 8E3A9129566 for <dcrup@ietfa.amsl.com>; Mon, 19 Jun 2017 16:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kitterman.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 ZbLHPLeruk3t for <dcrup@ietfa.amsl.com>; Mon, 19 Jun 2017 16:26:59 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEA8B1289B5 for <dcrup@ietf.org>; Mon, 19 Jun 2017 16:26:59 -0700 (PDT)
Received: from [10.152.151.131] (mobile-166-171-59-241.mycingular.net [166.171.59.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 17745C40320; Mon, 19 Jun 2017 18:26:58 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1497914818; bh=uQWQ8Qzt4lJQzjXeTUgT7blmwGHvl1IbIm3vNnUoGMY=; h=Date:In-Reply-To:References:Subject:To:From:From; b=DN5k3u36RxeKzM8pEVfl4AHvovUX+j1OdKdF4L/FSugbR6h908tok5EHB2q6WOl9M dIZf6XGRkdrwYkSVqX81q36fFbbjvjJh63FcOTBApNQzC61nWsIQJ2YA/wjC3TiLcW j4APQeoUqwqfKzkiqDyN9sD1nL4QvnGfsFEBT+eY=
Date: Mon, 19 Jun 2017 23:26:56 +0000
In-Reply-To: <20170619205416.10860.qmail@ary.lan>
References: <20170619205416.10860.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: dcrup@ietf.org
From: Scott Kitterman <sklist@kitterman.com>
Message-ID: <7807DE08-7107-4598-BC4F-0B8D73CFE75C@kitterman.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/IdI1xJlsxLbqijXkuTTsCxRGYpY>
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: Mon, 19 Jun 2017 23:27:01 -0000
On June 19, 2017 4:54:16 PM EDT, 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. It looks like python-nacl has what's needed (quick look only, didn't investigate thoroughly). Scott K
- [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