IETF Logo Mail Archive

[lamps] Re: What priv key format are we hacking in 2 weeks?

Russ Housley <housley@vigilsec.com> Thu, 06 March 2025 17:12 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@mail2.ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 72C4E859C35 for <spasm@mail2.ietf.org>; Thu, 6 Mar 2025 09:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mRmZ6Hm6Mg8n for <spasm@mail2.ietf.org>; Thu, 6 Mar 2025 09:12:47 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4416E859C09 for <spasm@ietf.org>; Thu, 6 Mar 2025 09:12:47 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 16833151FBD; Thu, 6 Mar 2025 12:12:47 -0500 (EST)
Received: from smtpclient.apple (63-145-195-251.dia.static.qwest.net [63.145.195.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 9831F15202C; Thu, 6 Mar 2025 12:12:44 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <39BAA7E6-BF4F-4DC2-A948-CC4919423441@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0C20F59F-B602-46A3-AF18-3287C1E8CA70"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Thu, 06 Mar 2025 09:12:28 -0800
In-Reply-To: <505d6ee0-1d0c-4072-92ec-5b06195f1d91@redhat.com>
To: Hubert Kario <hkario@redhat.com>
References: <CH0PR11MB5739C7D0A262F054C515C8339FC82@CH0PR11MB5739.namprd11.prod.outlook.com> <7C3C0A20-FE79-4EBB-98A4-E4CADEED07D5@vigilsec.com> <E261F86C-FBE3-4729-A3C7-F9A2099A74C9@sn3rd.com> <Z8cngX0jvQf_QEWB@chardros.imrryr.org> <505d6ee0-1d0c-4072-92ec-5b06195f1d91@redhat.com>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=from:message-id:content-type:mime-version:subject:date:in-reply-to:cc:to:references; s=pair-202402141609; bh=JTu6QR5jB9n+F8QA0RSZowwsCyX7voG7DAdByfbZwIA=; b=jBs+uk+336XPovhPvx43LPJueWHAvD/tFNzSM2pRJUBrAymQBGelmC+hWi3Ayv17swqDtjw6+KKICtUK7hw5P92NE87gpD/XdMLAxZ8nev4cuj8Wg5Q1vy2Mo5PK9QgOxExleiebOLglPxh+soaF8A3uaG9QJjYgBMh8bFXpzdKPhdP53c7iHiFmxrsF5DEqmfaqHo20IQ4dTle6snYaWEldYiSmMpgGzKpLUrzXqEQCywYdwfI1Cd9XKA2EWTvDNESK+FHfH9c0tB2a4ynEP2+HQqUKPnHzjsbaEv2/ZQvGU6D6BfH15wTkGs/U8ATDH6TlrE7QGp680uf1WieWDg==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Message-ID-Hash: 3I7SHPPDK2ZG4NOPCBCA4VQ7246RQU3A
X-Message-ID-Hash: 3I7SHPPDK2ZG4NOPCBCA4VQ7246RQU3A
X-MailFrom: housley@vigilsec.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Viktor Dukhovni <ietf-dane@dukhovni.org>, spasm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: What priv key format are we hacking in 2 weeks?
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/9QSvEf7nVcQetAkXBEFksBPvHEA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>

Alicja:
> 
> So, can confirm the priv-only and seed-priv, but I have an issue with seed-only.
> The tag used for it is 0x80 (which indicates IMPLICIT encoding), I would have
> expected a 0xa0 tag (which would be EXPLICIT encoding)...

The ASN.1 Module in Appendix A of draft-ietf-lamps-kyber-certificates says:

   DEFINITIONS IMPLICIT TAGS ::= BEGIN

So, IMPLICIT tags are correct.

Russ

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