Re: [pkix] PKCS #8? Re: Updated EdDSA/Ed25519 PKIX document

Anders Rundgren <anders.rundgren.net@gmail.com> Thu, 12 November 2015 08:42 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E901AD26B for <pkix@ietfa.amsl.com>; Thu, 12 Nov 2015 00:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 RKDGjF4vbDnb for <pkix@ietfa.amsl.com>; Thu, 12 Nov 2015 00:42:37 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 DC2A81AD1EE for <pkix@ietf.org>; Thu, 12 Nov 2015 00:42:36 -0800 (PST)
Received: by wmec201 with SMTP id c201so21286983wme.0 for <pkix@ietf.org>; Thu, 12 Nov 2015 00:42:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=L3qsYYH97I9BU5fSLCaHymGX1JNtxRW1Lk2+pZkRlwQ=; b=BCBa3utLQ2uObrP1KwU1TDVqGp+cUgeby2VtsTOLU5DOQaJlLw9V1jRz8afJfzbMRK RG5TbWFsQsYcBut0apmUce7n7QmtLRqFoIH6hkPTg+mMaudnVEJ4M5Xf7D3EZOxcIEHq WmwQcipGX+csoS4jnvAfBYyZ/VoB8iVjRGLGpV2W/sk8QRa1hrQ14n5d5EyfdbyREmOU DRJCF2CutpSfi+3/TZq1gHG7hFAXzpv26rWPYFjDPEhjZ1XvaF64Bn7Rt2LZIpdDlvsr 1Hjs0kyZesnyS4iQwuJtXSXxYINbClH/OPmuJtNHiuo5JBHO/2BlNO0DScBKVgo0szEi UWAw==
X-Received: by 10.28.217.6 with SMTP id q6mr17050284wmg.5.1447317755465; Thu, 12 Nov 2015 00:42:35 -0800 (PST)
Received: from [192.168.1.79] (148.198.130.77.rev.sfr.net. [77.130.198.148]) by smtp.googlemail.com with ESMTPSA id he3sm13186308wjc.48.2015.11.12.00.42.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Nov 2015 00:42:34 -0800 (PST)
To: Simon Josefsson <simon@josefsson.org>
References: <878u7xtu06.fsf@latte.josefsson.org> <5643175F.9070405@gmail.com> <1447244606.16388.10.camel@josefsson.org> <56435732.8020405@gmail.com> <87io57bqsy.fsf@latte.josefsson.org> <56444D7D.7090502@gmail.com> <87egfvbokg.fsf@latte.josefsson.org>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <564450F9.4070008@gmail.com>
Date: Thu, 12 Nov 2015 09:42:33 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <87egfvbokg.fsf@latte.josefsson.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/F7aFulkWyTadJZy-mwk_BUXejho>
Cc: pkix@ietf.org
Subject: Re: [pkix] PKCS #8? Re: Updated EdDSA/Ed25519 PKIX document
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix/>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Nov 2015 08:42:38 -0000

On 2015-11-12 09:37, Simon Josefsson wrote:
> Anders Rundgren <anders.rundgren.net@gmail.com> writes:
>
>> Pardon me for being somewhat unclear, I meant the distinction of EC versus ED.
> ...
>> Essentially the question is weather you extend EC or create a new type.
>
> Ah, now I understand.
>
> Well, the situation is that GnuTLS implements a new key type (see [1]
> but it should have more text) and there is ALSO the possibility of using
> the RFC 5915 ECPrivateKey together with the NamedCurve defined in [2]
> but it is a bit underspecified (see below).  I'm not negative about
> doing a PKCS#15 format in addition to this.
>
> The problem with re-using RFC 5915 is that has a number of references in
> it that doesn't make a lot of sense for EdDSA (e.g., it uses I2OSP from
> RSA for encoding!).  So it is not really clear how you would actually
> re-use the existing EC type for EdDSA since it is so tailored around how
> ECDSA works.  I assume this was the reason Nikos didn't re-use it but
> created a new simpler private key format for EdDSA.

This was (IMO) the right approach.

>
> To have more alignment, we could describe an ECPrivateKey structure for
> EdDSA keys that would be ASN.1-compatible but have different semantics
> that would work for EdDSA.  I'm not convinced that is worth the effort,
> as it will create implementation complexity and confusion.

Indeed.

Anders
>
> /Simon
>
> [1] https://tools.ietf.org/html/draft-josefsson-pkix-eddsa-04#section-8.3
> [2] https://tools.ietf.org/html/draft-josefsson-pkix-newcurves-01
>