All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] FYI: how to (really) cleanly shutdown the system	when root is on multiple stacked block devices
Date: Sun, 27 Jun 2010 04:53:29 +0200	[thread overview]
Message-ID: <20100627025329.GA4942@tansi.org> (raw)
In-Reply-To: <1277605715.3239.103.camel@fermat.scientia.net>

On Sun, Jun 27, 2010 at 04:28:35AM +0200, Christoph Anton Mitterer wrote:
> On Sun, 2010-06-27 at 01:34 +0200, Arno Wagner wrote:
> > Hmm. You know, encrypted root is a problem and pretty difficult
> > to do in the rfirt place. Why not just encrypt the critical 
> > parts, like /var /home /root? The rest only holds binaries
> > and config files anyways, which are not that sensitive...
> They're actually very sensitive, against compromise "when I'm not there"
> and the device is e.g. shut down (or even running).

For running, I recomend looking up physical memory freezing.
It allows you to cool down the memory, pull the pwer plug and
read the complete memeory contents up to a few minutes later on 
an external device. The keys are in there.

For not running, there are numerous ways to still attack the system.

> An attacker with access to my device could easily add e.g. a rootkit
> when I'm not there, which just waits until I once decrypt the "important
> stuff" and sends the key/data back home.

The current consensus in much of the security community is that
if an attacker has that level of physical access, you are screwed
anyways.  

> dm-crypte largely protects you from this. 

Only against very low-powered attackers. Against these I reccomend
a better lock on the door.

> Even if it doesn't give you
> mathematical integrity/authenticity, it's still very difficult for an
> attacker to do reasonable attacks (other then destroying your data)
> because he neither know where to change, nor to which value.

There are all kinds of possibilities to install keyloggers and other 
malicious software. Your kernel, for example, cannot be encrypted.
Keyloggers in all sizes and shapes, including inside your keyboard
can be installed. Other things can be done. 

Face it, you are using the wrong tool if protection against 
manipulation with physical access is your goal. For that 
I would recommend a safe that is intended to have a PC running
inside it. Not too cheap, but tamper-obvious. 

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 

  reply	other threads:[~2010-06-27  2:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 11:59 [dm-crypt] FYI: how to (really) cleanly shutdown the system when root is on multiple stacked block devices Christoph Anton Mitterer
2010-06-26 12:52 ` Arno Wagner
2010-06-26 14:21   ` Christoph Anton Mitterer
2010-06-26 18:36     ` Arno Wagner
2010-06-26 19:24       ` Milan Broz
2010-06-26 23:13         ` Christoph Anton Mitterer
2010-06-26 23:34           ` Arno Wagner
2010-06-27  0:20             ` markus reichelt
2010-06-27  8:35               ` Milan Broz
2010-06-27 12:03                 ` Christoph Anton Mitterer
2010-07-02 18:48                 ` markus reichelt
2010-07-02 19:29                   ` Christoph Anton Mitterer
2010-06-27  2:28             ` Christoph Anton Mitterer
2010-06-27  2:53               ` Arno Wagner [this message]
2010-06-27 11:57                 ` Christoph Anton Mitterer
2010-06-26 23:30         ` Arno Wagner
2010-06-27  2:31 ` Christoph Anton Mitterer
2010-06-27  2:39   ` Christoph Anton Mitterer
2010-06-27  2:56   ` Arno Wagner
2010-06-27 12:21     ` Christoph Anton Mitterer

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=20100627025329.GA4942@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.