Cryptsetup development
 help / color / mirror / Atom feed
From: cyper@tutanota.com
To: Arno Wagner <arno@wagner.name>
Cc: Milan Broz <gmazyland@gmail.com>,
	Cryptsetup <cryptsetup@lists.linux.dev>
Subject: Re: [feature] PQC KEM
Date: Tue, 30 Jun 2026 15:51:34 +0200 (CEST)	[thread overview]
Message-ID: <OwNn5ye--F-9@tutanota.com> (raw)
In-Reply-To: <akK8KlVr8s3ZHdvb@tansi.org>

PQC is not primary benefit, asymmetric key model is. I’m kinda curious about how such use case is valid.


29 Jun 2026 at 19:40 by wagner@arnowagner.info:

> 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
>


      reply	other threads:[~2026-06-30 13:51 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
2026-06-30 13:51     ` cyper [this message]

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=OwNn5ye--F-9@tutanota.com \
    --to=cyper@tutanota.com \
    --cc=arno@wagner.name \
    --cc=cryptsetup@lists.linux.dev \
    --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