All of lore.kernel.org
 help / color / mirror / Atom feed
From: "[lesh] Ivan Nikolic" <lesh@sysphere.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] encrypted root: prevent / detect tampering with kernel / initrd
Date: Tue, 29 Dec 2009 11:23:10 +0100	[thread overview]
Message-ID: <20091229102310.GI24454@sysphere.members.linode.com> (raw)
In-Reply-To: <20091228231158.GB16466@fancy-poultry.org>

[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]

you can set bios password for every boot (if you trust your bios, this would mean that for any 
software tampering your machine has to be taken appart, disk unplugged, etc. but most bioses had a lot of backdoor
passwords few years back, don't know how it is now, but not very nice I suppose)

so, to be extra sure, somekind of sum of unencrypted files is nice, yes.
that would mean that person would have to get past bios, boot another system, modify your kernel to make your hashing 
program lie to you (know in advance that you use one, and which) and that is hard enough for me:)
(and is the most feaseable software hack idea those "if there is phisical access game over" people are talking about)

if you are that paranoid, you cary your initrd/kernel on usb with you.

btw,
those problems can be addressed with an evil child of drm, chain of trust.
http://theinvisiblethings.blogspot.com/2009/01/why-do-i-miss-microsoft-bitlocker.html


I'm gonna setup the hash thing right now :)


* Heinz Diehl (htd@fancy-poultry.org) 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.
> 
> "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).
> 
> 			     
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
PGP 0x96085C00 http://lesh.sysphere.org

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-12-29 10:23 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 [this message]
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=20091229102310.GI24454@sysphere.members.linode.com \
    --to=lesh@sysphere.org \
    --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.