IETF Logo Mail Archive

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

Russ Housley <housley@vigilsec.com> Tue, 04 March 2025 14:22 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 646EC725DCB for <spasm@mail2.ietf.org>; Tue, 4 Mar 2025 06:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.537
X-Spam-Level:
X-Spam-Status: No, score=0.537 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_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=no 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 Cu3b9YbmlV8e for <spasm@mail2.ietf.org>; Tue, 4 Mar 2025 06:22:07 -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 7B017725DB7 for <spasm@ietf.org>; Tue, 4 Mar 2025 06:22:07 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 23621194E56; Tue, 4 Mar 2025 09:22:07 -0500 (EST)
Received: from smtpclient.apple (unknown [209.251.233.5]) (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 DCDFD19510D; Tue, 4 Mar 2025 09:22:06 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <7C3C0A20-FE79-4EBB-98A4-E4CADEED07D5@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3F048CB5-BA08-4BA0-8A4B-2831C705F523"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Date: Tue, 04 Mar 2025 09:21:56 -0500
In-Reply-To: <CH0PR11MB5739C7D0A262F054C515C8339FC82@CH0PR11MB5739.namprd11.prod.outlook.com>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>
References: <CH0PR11MB5739C7D0A262F054C515C8339FC82@CH0PR11MB5739.namprd11.prod.outlook.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=PsKGImnB9he7CdnNWy0u8bc37X2trWydUUanZzT7LPY=; b=HXXuOhaIMjpN+52tFm8n1R+5DM1DNdf4MOzPUfc9T4xxztNj9MqdQ5wnEL6h78tJaUiP6Z6cbrpL7YUYN4mqEa7fOC02m/kE53b2wM1qc74kad2sJau38ACNuBN8doWaAoS3TdgVxC8+fFZM/6rGeESvZv2MCCzbkjFwfbJnZoLFM/Kv3BWzbtJk/QxekCN1B6hiSX2qzQZcKkDYuL6rPQPI+GAm25mw7NTSAXlHtgQcgVwz1Lek9qa+CS1lGTZYk1jYe/A/Jzw3emJh2ebQfec/IejXp8z6E9HhZikYff4PPkMfbw23yLnOlzbC4igcz5/HetPoLE2yStRBonnCrA==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Message-ID-Hash: 7OG2H5PFCWBT3TRUQVGGSRR5CNJZPT6Y
X-Message-ID-Hash: 7OG2H5PFCWBT3TRUQVGGSRR5CNJZPT6Y
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: LAMPS <spasm@ietf.org>, Sean Turner <sean@sn3rd.com>
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/5TNHmychxROZaB1E6x0HRe1g3nE>
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>

I think the format is settled.  The normative language is not settled.

Russ

> On Mar 4, 2025, at 8:21 AM, Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org> wrote:
> 
> Hey @Sean Turner <mailto:sean@sn3rd.com> / @Russ Housley <mailto:housley@vigilsec.com>
>  
> The PQC hackathon group is planning out what we’re gonna be working on in two weeks. Private keys is of great importance to all, but we notice that https://datatracker.ietf.org/doc/draft-ietf-lamps-dilithium-certificates/ did not get updated by submission cutoff. So can you please post in this thread the private key ASN.1 that will eventually be in the draft that you would like us to hack at?
>  
>  
>  
> - - -
> Mike Ounsworth
> Software Security Architect
> (pronouns: he/him)

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