IETF Logo Mail Archive

[lamps] Re: [EXT] Re: [EXTERNAL] Re: Seed as private key for ML-DSA and ML-KEM

Bas Westerbaan <bas@cloudflare.com> Wed, 04 September 2024 09:03 UTC

Return-Path: <bas@cloudflare.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA374C1D6FCE for <spasm@ietfa.amsl.com>; Wed, 4 Sep 2024 02:03:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cloudflare.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SaKzph_mZpIf for <spasm@ietfa.amsl.com>; Wed, 4 Sep 2024 02:03:12 -0700 (PDT)
Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EED1C18DBA6 for <spasm@ietf.org>; Wed, 4 Sep 2024 02:03:08 -0700 (PDT)
Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-e026a2238d8so6456586276.0 for <spasm@ietf.org>; Wed, 04 Sep 2024 02:03:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google09082023; t=1725440587; x=1726045387; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dSNvIcPP6nMWd1cx9H+fpTqhiv8VhGBQJ7DCruXOGcE=; b=BOmKlm+ORB9mUTGNrAtS/M8uJQJy0Zl9ZpnN5AsSdWWQUTyn0rTemfM6K9yicSqvor F58nqm6d65Aie7k/bL++7UBtk9wLSpyoxWX79Ef0kqtotv4NuQ6KB+K1a7IKFz101Ecd lcnQDtMQ2a8u7kTsOEWLuPS4qzs4gORCtOj9eUf305g0sqNqvG8ACZLWOptoVPnXvwmC 3JHW/tjKMfxsdVk4JAeEsdzShTqerKoC1zS1TMzUN6X1SOM1pOo4BNEUoZcN/LFw2qJ1 TVNPEy8jPYfHIxkFq7sO03mIW8+IT+okdqphJHPbIE3tlzl9UV06eGyCvCBfJsoIuEXt ih4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725440587; x=1726045387; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dSNvIcPP6nMWd1cx9H+fpTqhiv8VhGBQJ7DCruXOGcE=; b=HQ+gG7pBbfj4TVMBASCC2eYONmTImoJ3ZFByj9WMxRvnz288riqY3TIvOsyOQPHVA6 GUnjT1aGUC7IxQGoxntn7F3qhASJCRDm1StT6DliuimYsob9KzKmsNYkPopRRfp2/4Uq +uzX8jQNj7SfFJmHSd3SkWZbb4jKYlKTOiP9mljaR3qduTH79prJ2KFY7XsG2eKDgjBs OBxNGq4WQs37WRAza5Cse8ZezSOj3vdJEP2BEVSZpO8Z1nfmS5VDgzFBQRkFIpVeatRn c2rJWPNI/nCnxoIiHiOYPSgisQ9lRJkvBVbtitIHkFev/52kBbAj0i4ILIdVam2ZoaFO 73+w==
X-Forwarded-Encrypted: i=1; AJvYcCWCCuoaWwlN1Elm2pVLZ7qal2zod9ozfxGkq0kD0oUpNMZuAsNFvhQUB4iyrrv0ovm0rboM1A==@ietf.org
X-Gm-Message-State: AOJu0YxArtQ4oHw9ULxVGL1FwYmASwCZxIKZvkTb3udK4aom0znYPZqv wzhy9D1GvIcT/fvL0XqBA4fS4mVnsUA6vOZkNwbEOYGb/trL4ESrRhGE4lzO5xSfZdDZ/kqby8Y z14YXgpMAAswXb8on+P75rYfhiudzCndkoHBG8g==
X-Google-Smtp-Source: AGHT+IGCZ/8U0AixSoG6HUOSzVJIeiAgdtIlq8kGYrKAuon4czZyh293d3mrVCLzKzmIcuaYSAvdb5q1Q/WMLzMncBg=
X-Received: by 2002:a05:6902:f8a:b0:e13:ca39:f80d with SMTP id 3f1490d57ef6-e1a7a1c2addmr19123181276.38.1725440587463; Wed, 04 Sep 2024 02:03:07 -0700 (PDT)
MIME-Version: 1.0
References: <CAMjbhoUOLfcRHT12ubSsPMEnDGT=UJUCvy34VX+qJYmyoFbscg@mail.gmail.com> <CAF8qwaCb8BJLqZQ__9+QsQ1+dWw426BwS4J+vQkUwfjWhdevnA@mail.gmail.com> <CH0PR11MB573952F98971721CF82D30B59F8F2@CH0PR11MB5739.namprd11.prod.outlook.com> <CAMm+LwjKs7X3cRCzUeaAjHJRThkWh_W3DxCFyE7SOwtYYJGLyA@mail.gmail.com> <CH0PR11MB5739C68B1041F8201434B1D89F882@CH0PR11MB5739.namprd11.prod.outlook.com> <CAMm+Lwjhcv+nT_LN5sebmZDCZo1rMU2gL5nqWMZNZjpR9LPxLg@mail.gmail.com> <BN0P110MB1419F2FC4A92C5EBADD8C3509088A@BN0P110MB1419.NAMP110.PROD.OUTLOOK.COM> <CH0PR11MB57396195C5A1A5C6B6FF020C9F882@CH0PR11MB5739.namprd11.prod.outlook.com> <BN0P110MB1419D12393CF13C73B14B1569088A@BN0P110MB1419.NAMP110.PROD.OUTLOOK.COM> <CAMm+LwhZhChwbfyWYUt3WcgG+yMZBFHOz2A0Fvi7PLtAZfq3+A@mail.gmail.com>
In-Reply-To: <CAMm+LwhZhChwbfyWYUt3WcgG+yMZBFHOz2A0Fvi7PLtAZfq3+A@mail.gmail.com>
From: Bas Westerbaan <bas@cloudflare.com>
Date: Wed, 04 Sep 2024 11:02:56 +0200
Message-ID: <CAMjbhoXdYoP9Hx9A1LpOsjrQ6Bym0bz183pKjipH1Bj_VjGHJQ@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary="0000000000004c855606214771c6"
Message-ID-Hash: CJYTUAMCWNFD3FSZEHZS2NEP6U6PTY53
X-Message-ID-Hash: CJYTUAMCWNFD3FSZEHZS2NEP6U6PTY53
X-MailFrom: bas@cloudflare.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: "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>, Mike Ounsworth <Mike.Ounsworth@entrust.com>, David Benjamin <davidben@chromium.org>, LAMPS <spasm@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [lamps] Re: [EXT] Re: [EXTERNAL] Re: Seed as private key for ML-DSA and ML-KEM
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/h45FEv_atYGTQq1k83J67HQDi6k>
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>

It's important to get this straight. Plain concatenation makes most sense
to me. The order in FIPS 203 is (d, z), so all implementations I've seen so
far went for d || z (64 bytes) as the format of the seed. I don't see a
reason to do things differently.

Best,

 Bas

On Wed, Sep 4, 2024 at 12:56 AM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

> Not wanting to reopen this but...
>
> I can't find a place where the NIST spec specifies how to get from a 64
> byte seed to z, d. The competition code had a scheme for going from a 32
> byte seed but that is gone.
>
> If we are going to use (z,d), we have to specify how to serialize, whether
> that is concatenation (my preference) or an ASN.1 wrapper.
>

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