From: Ralf Ramsauer <ralf+dm@ramses-pyramidenbau.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] How to derive master key in plain dm-crypt mode
Date: Wed, 10 Dec 2014 18:01:13 +0200 [thread overview]
Message-ID: <54886E49.60902@ramses-pyramidenbau.de> (raw)
In-Reply-To: <54886D11.60908@ramses-pyramidenbau.de>
On 12/10/2014 05:56 PM, Ralf Ramsauer wrote:
> On 12/10/2014 01:48 PM, Jian-Ming Zheng wrote:
>> Hi,
>>
>> In plain dm-crypt mode, there is no encrypted master key on the device
>> (i.e., no metadata header). Is a master key derived from the user
>> passphrase and used to en-/decrypt the device? If yes, how to derive
>> the master key from the passphrase in plain mode?
Oh I'm sorry. I stand corrected.
I skipped a word when I read your message. I skipped the "plain" part.
I can't answer your question as I don't know how the key is derived from
the passphrase using plain mode.
But I'm pretty sure someone one this list will know it.
But I can tell you, that if your device is mounted, you can use dmsetup
to dump the masterkey:
# dmsetup table --showkeys DEVICENAME
cheers
Ralf
> Hi,
>
> No.
>
> In short words and to sum it up:
> The passphrase is used to generate some "intermediate" key, using a Key
> Derivation Function. In case of Luks, this function is PBKDF2.
> This derived key is used to decrypt a Keyslot in the Luks header of your
> volume, which contains the actual masterkey.
>
> So having only the passphrase is not sufficient to derive a volume's
> masterkey.
>
> cheers
> Ralf
>> Thanks.
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
next prev parent reply other threads:[~2014-12-10 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 11:48 [dm-crypt] How to derive master key in plain dm-crypt mode Jian-Ming Zheng
2014-12-10 15:56 ` Ralf Ramsauer
2014-12-10 16:01 ` Ralf Ramsauer [this message]
2014-12-11 2:16 ` Jian-Ming Zheng
2014-12-10 22:34 ` Robert Nichols
2014-12-11 1:37 ` Arno Wagner
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=54886E49.60902@ramses-pyramidenbau.de \
--to=ralf+dm@ramses-pyramidenbau.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.