All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Sessink <oliviersessink@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] encrypted root: prevent / detect tampering with kernel / initrd
Date: Tue, 29 Dec 2009 11:05:03 +0100	[thread overview]
Message-ID: <4B39D44F.8040201@gmail.com> (raw)
In-Reply-To: <20091228231158.GB16466@fancy-poultry.org>

Heinz Diehl wrote:
> On 28.12.2009, Olivier Sessink wrote: 
> 
>> yes you are 100% right from a perfect security viewpoint. However,
>> we're looking at a "regular user" deployment, and we know that our
>> regular users are not going to look after their devices as good as
>> most IT security professionals will do (they might even carry their
>> password in their wallet, or tell the password over the phone). So
>> our aim is not 100% perfect security, but just "make it (a lot)
>> harder" to get to the data.
> 
> Anybody who has the skills and the motivation to modify your kernel/initrd
> is far from being your "regular user", and is most likely able and has the
> expertise to do other things to your machine as well.

I'm not so sure about that. Most script kiddies can modify an initrd 
(just google for 'dm-crypt evil maid' and you'll find at least one 
script-kiddie level recipe). But I don't think there are many script 
kiddies that can do a TEMPEST attack or install a physical keylogger in 
a laptop.

> "Please repeat with me: there is no way to avoid or detect backdoors if
> physical access to the machine has ever been granted." (Werner Koch on
> gnupg-users 19.02.2009 on exactly the same topic).

add to that: "encryption is not perfect if your house is not TEMPEST 
proof or burglar proof, or if you can be blackmailed, or if you have 
children that can be kidnapped, or if they simply drug you, etc. etc."

If somebody is really determined to get to your data they will succeed, 
skilled or not skilled. I suppose everybody on this list knows this one: 
http://imgs.xkcd.com/comics/security.png

Olivier

  reply	other threads:[~2009-12-29 10:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 20:28 [dm-crypt] encrypted root: prevent / detect tampering with kernel / initrd Olivier Sessink
2009-12-28 21:20 ` Luca Berra
2009-12-28 21:41   ` Olivier Sessink
2009-12-28 23:11     ` Heinz Diehl
2009-12-29 10:05       ` Olivier Sessink [this message]
2009-12-29 10:23       ` [lesh] Ivan Nikolic
2009-12-29 12:25       ` Olivier Sessink
2009-12-29 12:37         ` Milan Broz
2009-12-29 20:24       ` Arno Wagner
2009-12-29 21:15         ` Heinz Diehl
2009-12-29 23:02           ` Olivier Sessink
2009-12-30  2:52           ` Arno Wagner
2009-12-30 14:16             ` Heinz Diehl
2009-12-30 15:34               ` Arno Wagner
2009-12-29 21:31         ` Hannes Erven
2009-12-29 21:41           ` Gregy
2009-12-30  2:53           ` Arno Wagner
2009-12-28 22:41 ` Zdenek Kaspar
2009-12-28 22:51   ` Zdenek Kaspar
2009-12-28 22:57 ` Heinz Diehl
2009-12-29 20:18 ` Arno Wagner
2009-12-29 22:52   ` Olivier Sessink
2009-12-30  2:56     ` Arno Wagner
2009-12-30 10:48       ` Olivier Sessink
2009-12-30 15:28         ` 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=4B39D44F.8040201@gmail.com \
    --to=oliviersessink@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 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.