From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] encrypted root: prevent / detect tampering with kernel / initrd
Date: Tue, 29 Dec 2009 21:18:49 +0100 [thread overview]
Message-ID: <20091229201848.GA17029@tansi.org> (raw)
In-Reply-To: <4B3914FB.7060008@gmail.com>
On Mon, Dec 28, 2009 at 09:28:43PM +0100, Olivier Sessink wrote:
> Hi all,
>
> I was wondering if there are some 'common' ways to prevent tampering
> with the unencrypted kernel and initrd in the case of an encrypted root
> filesystem?
No. Any "common" way would automatically become ineffective. Your
only chance is to do something unexpected and hence uncommon.
> If somebody has access to your computer they could change
> the initrd and kernel and make your encryption useless (e.g. store the
> password in /boot, or send it over the network, etc. etc.). It shouldn't
> be too hard to make this at least very difficult.
It is theoretically impossible and practically very hard.
> I was thinking along the lines of:
> - check a checksum of the MBR and partition table
=> Fake the check
> - check a checksum of the complete /boot filesystem
=> See above
> - check the pointers in the kernel system call table (detects many rootkits)
=> See above.
> - check for virtualization (any virtual rootkits)
=> Very hard and the check can be removed.
> - ...? any better ideas how to detect tampering?
>
> Obviously all of this should be done by a binary inside the encrypted
> filesystem - everything in /boot (kernel and initrd) is not to be
> trusted. That means we can only warn the user after the password is
> probably gone already, but this is better than nothing.
>
> Any comments, ideas or links ?
With an attacker competent enough to do this type of tampering
you are screwed as long as you rely on the on-disk information.
But here is something easy: Use an external boot medium for
verification, e.g. a memory-stick installed Knoppix with some
custom check script you call manually or automatically. Keep
the external checker system separate from the laptop. With
that the ideas you outlined above would work. You can, e.g.,
compary MBR and files in /boot to checksums or good copies.
I currently have an 8GB SuperTalent Stick with the Knoppix
DVD installed on it in my vallet. Adding packages and your own
data/programs is possible as it has a writable filesystem
(writes get ovelayed on top of the read-only DVD image).
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
next prev parent reply other threads:[~2009-12-29 20:18 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
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 [this message]
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=20091229201848.GA17029@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.