Cryptsetup development
 help / color / mirror / Atom feed
* Derive encryption key from PIN
@ 2026-07-14 10:27 oSumAtrIX
  2026-07-14 10:57 ` Ondrej Kozina
  2026-07-14 11:07 ` Milan Broz
  0 siblings, 2 replies; 5+ messages in thread
From: oSumAtrIX @ 2026-07-14 10:27 UTC (permalink / raw)
  To: cryptsetup

Hello,

I found this email in the README of the cryptsetup GitLab repository.

I am reaching out because I noticed that the PIN used to unseal the
decryption key from the TPM is not used to derive the decryption key.
The PIN is merely used as a policy, when it can also function in a
cryptographic context. The sealed key can further be encrypted with
the PIN, so that even a full compromise of the TPM including the
sealed key does not reveal the decryption key in cleartext. According
to
https://www.sstic.org/media/SSTIC2011/SSTIC-actes/bitlocker/SSTIC2011-Slides-bitlocker-bordes.pdf
BitLocker implements a KDF from the TPM PIN, but it seems to be
missing in LUKS.

Sincerely,
Ohan Melkonyan

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-07-14 11:19 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2026-07-14 11:07 ` Milan Broz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox