From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Retrieve the Passphrase from RAM Memory
Date: Tue, 27 Sep 2011 12:17:51 +0200 [thread overview]
Message-ID: <20110927101751.GA18567@tansi.org> (raw)
In-Reply-To: <CACFtf0c_ZU7eLsct1g7Cdyijb0-UG9L8JzJLH0CR90RdQU8WDA@mail.gmail.com>
On Mon, Sep 26, 2011 at 11:34:05PM -0300, Eduardo Schultze wrote:
> Hello,
>
> I'm a Security Information student at Unisinos College, Brazil. As a paper
> during this semester it was me and my colleagues choice to write a paper
> about LUKS on Ubuntu 10.4.
>
> My question is - Is it possible to retrieve the passphrase from RAM memory
> after a successful authentication and shutdown? Is this case we would turn
> the system on, authenticate, turn off, and then check if the passphrase
> would still be in the RAM memory even with the turned off computer.
No. The passphrase is not stored and the PBKDF2 iterations
prevent reconstructing it.
However, you can get the master key. DRAM keeps state only for
seconds after turn-off. You can freeze the RAM (I pelive some people
around Ross Anderson have done that with some success) to extend that
time.
> If not, would it be possible to dump the RAM memory and retrieve the
> passphrase (now with the system turned on)?
>
> I looked for these answers at the FAQ section but couldn't find it.
They are not there, because they have low relevance in practice.
If somebody gets access to the physical machine while
the container is unlocked, you should assume they can get access
to the data. They would still not get the passphrase.
For the memory-dump, you can extrapolate the techniques used
in FAQ item
"How do I recover the master key from a mapped LUKS container?
Or you can just try every 256 bit word from the memory dump.
As you do not need iterations if you have the master key, that
should be doable pretty fast. Incidentally, that is one of the
ways DeCSS (break of DVD encryption) got the key from a software
player.
As to your paper, good choice! I also suggest you put in
a section about LUKS usability (of paramount importance
with security software, but often forgotten) and the typical
problems people have. The mailing-list archive should
provide plenty of examples.
Is the paper going to be in english? If so, I would like
to get a copy once it is finished. Might be instructive to
get an outside view.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2011-09-27 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 2:34 [dm-crypt] Retrieve the Passphrase from RAM Memory Eduardo Schultze
2011-09-27 9:07 ` ken
2011-09-27 10:17 ` Arno Wagner [this message]
2011-09-27 11:13 ` Roscoe
2011-09-27 10:47 ` Roscoe
2011-09-27 11:50 ` Milan Broz
2011-09-27 14:44 ` Karl O. Pinc
2011-09-27 16:55 ` Milan Broz
2011-09-27 11:53 ` octane indice
2011-09-27 12:26 ` Milan Broz
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=20110927101751.GA18567@tansi.org \
--to=arno@wagner.name \
--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