From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Extract master key from running system
Date: Thu, 28 Jul 2011 09:14:01 +0200 [thread overview]
Message-ID: <4E310C39.7090200@redhat.com> (raw)
In-Reply-To: <20110728050428.GA5441@tansi.org>
On 07/28/2011 07:04 AM, Arno Wagner wrote:
> I have to admit that there is no info in the FAQ because when I wrote
> that I did not have time to find out. In the mean time I have had
> an opportunity to do so, so I should probably update the FAQ. First,
> I think trying to dump will not create additional damage. Here is what
> works on my machine:
>
> cryptsetup luksDump --dump-master-key
For luksDump you need valid LUKS header.
btw I added script which tries to extract master key automatically
fro active device and prepares cryptsetup parameters.
http://code.google.com/p/cryptsetup/source/browse/trunk/misc/luks-header-from-active
The steps there are quite straightforward.
Milan
next prev parent reply other threads:[~2011-07-28 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 3:07 [dm-crypt] Extract master key from running system Brian
2011-07-28 5:04 ` Arno Wagner
2011-07-28 7:14 ` Milan Broz [this message]
2011-07-30 18:42 ` 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=4E310C39.7090200@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