Cryptsetup development
 help / color / mirror / Atom feed
From: Arno Wagner <wagner@arnowagner.info>
To: Milan Broz <gmazyland@gmail.com>
Cc: cyper@tutanota.com, Cryptsetup <cryptsetup@lists.linux.dev>
Subject: Re: [feature] PQC KEM
Date: Mon, 29 Jun 2026 20:40:42 +0200	[thread overview]
Message-ID: <akK8KlVr8s3ZHdvb@tansi.org> (raw)
In-Reply-To: <eeba13d0-3337-4213-8751-53de0838c474@gmail.com>

On Mon, Jun 29, 2026 at 18:42:03 CEST, Milan Broz wrote:
> On 6/29/26 6:27 PM, cyper@tutanota.com wrote:
> > Interested in introducing a new LUKS2 "xwing" keyslot type unlocked by an X-Wing
> > post-quantum hybrid KEM (ML-KEM-768 + X25519, draft-connolly-cfrg-xwing-kem)
> > instead of a passphrase to encrypt the kek (volume key)?
> > 
> > 1) asymmetric model won't shine in single user case but will be attractive in multiple user/image enrollment cases.
> > 2) if per-device fresh wrapping key is desired
> > 
> > 
> > I've implemented such keyslot type and tested.  But don't know if the aforementioned two cases is worth discussion.
> 
> This is typically something that should be done through LUKS2 external token while keeping keyslot
> encryption as it is defined in LUKS. (Maybe you did it that way, no idea.)
> 
> Anyway, what security issue this solves (except "it is PQC")?

That seems to be the key question. 

Also refer to https://www.cs.auckland.ac.nz/~pgut001/pubs/bollocks.pdf

Arno

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  parent reply	other threads:[~2026-06-29 18:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29 16:27 [feature] PQC KEM cyper
2026-06-29 16:42 ` Milan Broz
2026-06-29 17:50   ` cyper
2026-06-29 18:40   ` Arno Wagner [this message]
2026-06-30 13:51     ` cyper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=akK8KlVr8s3ZHdvb@tansi.org \
    --to=wagner@arnowagner.info \
    --cc=arno@wagner.name \
    --cc=cryptsetup@lists.linux.dev \
    --cc=cyper@tutanota.com \
    --cc=gmazyland@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox