IETF Logo Mail Archive

[openpgp] Storing post-quantum keys for use in openpgp

Robert Lee <robert.lee@proton.ch> Thu, 22 August 2024 16:29 UTC

Return-Path: <robert.lee@proton.ch>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51D3EC1519AA for <openpgp@ietfa.amsl.com>; Thu, 22 Aug 2024 09:29:05 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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=proton.ch
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 CR8jaex6ydMG for <openpgp@ietfa.amsl.com>; Thu, 22 Aug 2024 09:29:00 -0700 (PDT)
Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 2247CC151066 for <openpgp@ietf.org>; Thu, 22 Aug 2024 09:28:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.ch; s=lz4hc3myongn3p64uyl63jee7i.protonmail; t=1724344137; x=1724603337; bh=DXF1qCA0lPmKp5UAkBZPOgt2MSyjduPCYwzhqOm6/L0=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=lgpjdF+1HWzYFGy3CecxHF4U9uobKB1A6NIsbfYFN8ZzqqgdcSoUMiuA4XQtv/6A2 la+wxHuCarTZihLZn8gapT0p2wzGtaATZVQVrkfyOkYuFXLVIWgvAKc/32to3lOLnI +Cot8pyLnJAStnzFXJ4l292rxXtzxzt2rJDwfZ6XHA+V0xiTWlpDnN1tQfBtzteKf5 KNydjHHlwgFHgPrxCwxf6LNjjjzK6tZ26cXkBCkvPopAkAw+1FVKdY4SLk6wSrCJEx tGYw71WTMEGIArRpivxR81EyKxDfYdHdsEI4SYO4Gx9htUqxBr6efrMP/VJtAkU4Ik jXB7SQqERrbSg==
Date: Thu, 22 Aug 2024 16:28:51 +0000
To: openpgp@ietf.org
From: Robert Lee <robert.lee@proton.ch>
Message-ID: <Z6en3yocy_HaqI3Rl2AUeIQLDOREbMIsegFXTES9HllQTam58UHMW9a21aGnSMcLj7VKpFlqX-QErWI8C98EgkjfkZ0-wRB-H0UQjuPy4N4=@proton.ch>
Feedback-ID: 96447522:user:proton
X-Pm-Message-ID: 8fcb2b7a1fc7f4aba70a17e5d590d84176a08edc
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------900b90711334902df430ba62975b720d3aed4d3eeb4080426492f34242e64851"; charset="utf-8"
Message-ID-Hash: YHJ4IVRWKS6XIMVCKPH773ZCDHQCLGVM
X-Message-ID-Hash: YHJ4IVRWKS6XIMVCKPH773ZCDHQCLGVM
X-MailFrom: robert.lee@proton.ch
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-openpgp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [openpgp] Storing post-quantum keys for use in openpgp
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/2dg-DrWt4DgIoX8uTalCa-kzE38>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Owner: <mailto:openpgp-owner@ietf.org>
List-Post: <mailto:openpgp@ietf.org>
List-Subscribe: <mailto:openpgp-join@ietf.org>
List-Unsubscribe: <mailto:openpgp-leave@ietf.org>

Hello all,



In amongst the efforts for standardising post-quantum cryptography in openPGP we'll need to also consider how to store the new post-quantum secure keys in PGP private key blocks.



In the latest Crypto Dispatch by Filippo Valsorda [1], he proposes implementors of post-quantum crypto ignore the existence of the proposed serialisation format for decapsulation keys in favour of only using seeds as the storage format for ML-KEM keys.



Is this something that could/should be adopted in openpgp or not?  I found the arguments in favour of only using seeds convincing, I also like anything that can remove complexity where possible.  However, I accept that there may be reasons why this is not practical in openpgp?  I look forward to hearing what others think.



Best Regards,

Rob Lee



[1] https://words.filippo.io/dispatches/ml-kem-seeds/

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