From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] The encrypted LUKS Master Key
Date: Sat, 14 Nov 2009 19:22:01 +0100 [thread overview]
Message-ID: <4AFEF549.1020203@redhat.com> (raw)
In-Reply-To: <20091114172820.8962FCBEAB@ws5-11.us4.outblaze.com>
On 11/14/2009 06:28 PM, Si St wrote:
> A Question:
>
> Where is the encrypted MK located that decrypts the dm-encrypted partition?
In the kesylot area (keyslot areas starts after that visible part of LUKS header),
encrypted by the same cipher as data and obfuscated by algorithm
described in LUKS specification http://code.google.com/p/cryptsetup/wiki/Specification
> I believe to understand the point so far that the decrypted MK is never written to disk, only to the memory.
yes, decrypted MK is never stored on disk, only used to set dm-crypt mapping using dm-ioctl.
For LUKS, the MK itself is generated using random data, passphrase only unlocks the keyslot area
where is the MK stored.
To exact specification please read the LUKS documentation above.
Milan
--
mbroz@redhat.com
prev parent reply other threads:[~2009-11-14 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 17:28 [dm-crypt] The encrypted LUKS Master Key Si St
2009-11-14 18:22 ` Milan Broz [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=4AFEF549.1020203@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.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