Re: [feature] PQC KEM

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 [email protected]:

> On 6/29/26 6:27 PM, [email protected] wrote:
>
>> Interested in introducing a new LUKS2 "xwing" keyslot type unlocked by a=
n 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 attracti=
ve in multiple user/image enrollment cases.
>> 2) if per-device fresh wrapping key is desired
>>
>>
>> I've implemented such keyslot type and tested.=C2=A0 But don't know if t=
he aforementioned two cases is worth discussion.
>>
>
> This is typically something that should be done through LUKS2 external to=
ken 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
>