From: Ondrej Kozina <okozina@redhat.com>
To: cryptsetup@lists.linux.dev
Cc: oSumAtrIX <johan.melkonyan1@web.de>
Subject: Re: Derive encryption key from PIN
Date: Tue, 14 Jul 2026 13:19:26 +0200 [thread overview]
Message-ID: <e70a671d-c181-4178-8900-bf7fc1f7686f@redhat.com> (raw)
In-Reply-To: <CAK+fmzxwSgHcYw5FL-8RV4SBUyb6stzsdm_DaWURvOsfRnv3Dw@mail.gmail.com>
On 14/07/2026 13:10, oSumAtrIX wrote:
> Hi,
>
>> What do we talk about? systemd-tpm2 cryptsetup plugin? IIUCT it uses
>> secret stored in TPM2 to get LUKS2 keyslot passphrase or KEK. The KEK
>> later enter KDF to derive keyslot encryption key. And the keyslot
>> contains encrypted volume key (MEK).
>>
>> Or, there's some other plugin or application that seals the actual
>> volume key?!
>>
>> If there's something that could be improved in systemd-tmp2 plugin,
>> please open RFE on systemd. They maintain the plugins for cryptsetup.
>>
>> Best regards
>> O.
>
> Please note that I have limited knowledge regarding the infrastructure
> of LUKS or cryptsetup. Therefore, I would appreciate guidance on the
> appropriate contact for my issue.
From your description, I think it's related to systemd-tpm2 plugin. In
that case you can contact systemd people via systemd-devel list[1] or
take a look at systemd-tpm2 plugin sources[2].
I have ported systemd plugins into native libcryptsetup plugins some
time ago (hosted in systemd repository), but there were many changes to
those plugins over the time so the best approach would be to take a look
and open RFE or Issue with issue description if there are concerns about it.
[1] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[2] https://github.com/systemd/systemd/
Best regards
O.
next prev parent reply other threads:[~2026-07-14 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 10:27 Derive encryption key from PIN oSumAtrIX
2026-07-14 10:57 ` Ondrej Kozina
2026-07-14 11:10 ` oSumAtrIX
2026-07-14 11:19 ` Ondrej Kozina [this message]
2026-07-14 11:07 ` Milan Broz
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=e70a671d-c181-4178-8900-bf7fc1f7686f@redhat.com \
--to=okozina@redhat.com \
--cc=cryptsetup@lists.linux.dev \
--cc=johan.melkonyan1@web.de \
/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