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: Wed, 30 Dec 2009 00:02:22 +0100	[thread overview]
Message-ID: <4B3A8A7E.9000002@gmail.com> (raw)
In-Reply-To: <20091229211536.GA31271@fancy-poultry.org>

Heinz Diehl wrote:
> On 29.12.2009, Arno Wagner wrote: 
> 
>> I don't agree. But you have to think outside of the box and use a
>> separate, uncompromised boot medium that the attacker did not have
>> access to.
> 
> Sorry, but I can't see how this would help. The attacker installs a
> hardware keylogger and just doesn't care.

I don't see the averae script kiddie install a hardware keylogger in a 
modern laptop.

If you have an intelligence agency after you you're screwed anyway. 
They'll use a tempest attack or something so you won't even notice that 
you gave them your password (I don't have a tempest proof room in my 
house, perhaps other people have?).

So it's a matter of security management. For highly confidential data 
you need ($$$) a tempest proof environment with armed guards. For only 
slightly sensitive data, simple disk encryption and some measures 
against script kiddies are usually enough.

Olivier

  reply	other threads:[~2009-12-29 23:02 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
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 [this message]
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=4B3A8A7E.9000002@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.