From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] keys from RAM dumps, hibernation files
Date: Fri, 14 Nov 2014 08:31:46 +0100 [thread overview]
Message-ID: <5465AFE2.30902@gmail.com> (raw)
In-Reply-To: <c397603c459c70e0c3edf9307c9fb23b.squirrel@ssl.verfeiert.org>
On 11/14/2014 12:33 AM, Sven Eschenberg wrote:
> On Thu, November 13, 2014 17:35, Michael Enßlin wrote:
>> Hi,
>>
>> LuksClose _should_ wipe all remains of the key from memory.
>
> Actually unmapping the crypto target in dm-crypt should do that. The
> luksClose operation of cryptsetup is one example that initiates unmapping.
Yes and it does it. As the same as if you use low-level "dmsetup remove".
Anyway, you can try it:
I tested it with the AES key finder (cold boot utilities)
on memory image from suspended virtual machine
(plus you need to find dmcrypt crypt structure with plain key).
After luksClose and luksSuspend all previously visible keys in RAM
must disappear.
Milan
next prev parent reply other threads:[~2014-11-14 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 14:21 [dm-crypt] keys from RAM dumps, hibernation files Lars Winterfeld
2014-11-13 16:35 ` Michael Enßlin
2014-11-13 23:33 ` Sven Eschenberg
2014-11-14 7:31 ` Milan Broz [this message]
2014-11-14 7:06 ` Heinz Diehl
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=5465AFE2.30902@gmail.com \
--to=gmazyland@gmail.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