IETF Logo Mail Archive

Re: [pkix] RFC8410 / RFC8037 incompatibility

Jim Schaad <ietf@augustcellars.com> Fri, 28 August 2020 16:03 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69C4C3A0D2C for <pkix@ietfa.amsl.com>; Fri, 28 Aug 2020 09:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 QD92U3yH5vCd for <pkix@ietfa.amsl.com>; Fri, 28 Aug 2020 09:03:19 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 426BB3A0D95 for <pkix@ietf.org>; Fri, 28 Aug 2020 09:03:19 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 28 Aug 2020 09:03:12 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Anders Rundgren' <anders.rundgren.net@gmail.com>, pkix@ietf.org
References: <6b0c0d16-d421-f516-9b21-d94492d72075@gmail.com> <b9a3b61f-b987-58e4-53f8-853b8d2ab265@gmail.com>
In-Reply-To: <b9a3b61f-b987-58e4-53f8-853b8d2ab265@gmail.com>
Date: Fri, 28 Aug 2020 09:03:11 -0700
Message-ID: <011101d67d54$bc52dbc0$34f89340$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQDekE2dNMpTGW2yQ3hzq1U+X+H3JwJ4ECQrqynH4xA=
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/kZfZBRyV5rzq7Nu2n0pt84WwTqU>
Subject: Re: [pkix] RFC8410 / RFC8037 incompatibility
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 28 Aug 2020 16:03:29 -0000

If you read the text, the certificate in 10.2 says it is self-issued not
self-signed.  The key used to sign the certificate is not the private key of
the public key in the certificate.  I don't remember off the top of my head
which of the EdDSA certs from that draft I used to do the signature.

jim

-----Original Message-----
From: pkix <pkix-bounces@ietf.org> On Behalf Of Anders Rundgren
Sent: Friday, August 28, 2020 8:00 AM
To: pkix@ietf.org
Subject: [pkix] RFC8410 / RFC8037 incompatibility

Hi Crypto Experts,

Please pardon my ignorance regarding curve25519, but I ran into problems [*]
trying to recreate the sample certificate:
https://tools.ietf.org/html/rfc8410#section-10.2

Reading
https://tools.ietf.org/html/rfc8037#section-3.2
indicates that signing using an ECDH key MUST NOT be doable as well.

Personally I don't see any use of a self-signed encryption certificate so
maybe this is just a bad example...kind of edge case.

Regards,
Anders

*] java.security.InvalidKeyException: cannot identify EdDSA private key

_______________________________________________
pkix mailing list
pkix@ietf.org
https://www.ietf.org/mailman/listinfo/pkix

v2.23.0 | Report a Bug | By Email