Re: [feature] PQC KEM

[cyper@tutanota.com]

Avoid low-entropy passphrase. (I am aware of key file which is yet another passphase pass to pbkdf)
Avoid pbkdf cause the default one argon2 is not fips compliant.
Enable public recipient access.

29 Jun 2026 at 17:42 by gmazyland@gmail.com:

> 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")?
>
> Milan
>