From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Help/Question
Date: Tue, 14 Jan 2014 08:06:27 +0100 [thread overview]
Message-ID: <20140114070627.GC18564@tansi.org> (raw)
In-Reply-To: <52D49224.1020900@vfemail.net>
I assume you mean "vulnerable"....
All software-based encryption is vulnerable to cold-boot
attacks, LUKS is no exception. There is nothing that can
be done about it, and hence there is no discussion.
An attacker can also simply go the full way and not cold
boot, but remove the RAM modules and read them externally.
This has been shown to work for a removal time in the
minute range.
Unless very carefully implemented, hardware encryption is
vulnerable too. And, of course, anybody with access to
running hardware with openend crypto containers can just
try to break into it.
Arno
On Tue, Jan 14, 2014 at 02:25:56 CET, Timothy Alexander wrote:
> Hello,
>
> I have a question. Is LUKS viable to a cold boot attack. TrueCrypt
> is, but I'm not sure about LUKS. If it is, is there any discussion
> of encrypting keys in RAM (assuming the computer is immediately
> turned off, hibernating, or a container is unmounted).
>
> Thank you,
>
> Timothy
>
> -------------------------------------------------
>
> VFEmail.net - http://www.vfemail.net
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
> $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk!
> No bandwidth quotas!
> Commercial and Bulk Mail Options!
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
prev parent reply other threads:[~2014-01-14 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 1:25 [dm-crypt] Help/Question Timothy Alexander
2014-01-14 7:06 ` Arno Wagner [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=20140114070627.GC18564@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 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.