From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: A _good_ and valid use for TPM
Date: Sun, 22 Feb 2009 16:33:47 +0100 [thread overview]
Message-ID: <49A1705B.7030702@gmail.com> (raw)
In-Reply-To: <a5d587fb0902220649j68f5e3f0o532e8190d2fbb379@mail.gmail.com>
> For some reason he wants to store the data encrypted in multiple
> locations rather than using a simple terminal to retreive the data
> over network which makes things needlessly hard.
He perhaps needs important amount of computing power. And in his case
"all in centre" may require too much bandwidth
> Now I am not sure how secure this solution is. You can usually remove
> the battery to reset BIOS password, reflash the BIOS, etc.
Many boards save the data in flash memory so removing power won't reset
password. Second flash chip if it's dedicated can be covered with
concrete too and resetting pins can be removed. Besides with coreboot
everything this can be well controlled - you can embed the config to flash.
>
> Since manufacturers claim (or used to) that you can pry the TPM chip
> off your board and it will still work the board is bootstrapped by the
> main CPU, not the TPM. This makes it possible to short some pins on
> the TPM chip so that is cannot be accessed during boot, boot a virtual
> machine, and have the BIOS initialize the chip inside that.
>
It would require some modifications to virtual machine to skip some
initilisation but is entirely possible and needs to be done only once to
cover 99% of motherboards
> There's also the possibility to remove the RAM from a running computer
> given you find out what kind of RAM it uses and get a different
> compatible computer.
concrete :)
>
> Generally this shifts the attack from the realm of plain vandalism to
> the realm of planned attack which is certainly a bonus.
>
> Still I would rather rely on a custom solution because I would know
> exactly what it does. The manufacturers of PC mainboards tend to not
> release exact specifications and there are often serious problems.
>
> Still finding the flaw in the particular mainboard would probably take
> some non-trivial effort.
There are only few kinds of tpm chips so it's enough that someone cracks
the corresponding ship to make the attack trivial. As a matter of fact
few year from now it may be easier to get a universal reader for all tpm
chips then a reader for a specific flash chip
> If the attacker just wants to break something there would likely be
> easier targets. If you are specifically targeted you are doomed.
Yes. Once an attacker has the device he is able to retrieve all the data
in. Only putting physical obstacles may slow the attacker down. And I
doubt that a cost of such operation can be over $10000 no matter what
protection you use.
>
> Now to the TPM support in GRUB.
>
> This makes the TPM support debate seem quite pointless.
>
It isn't. Supporing tpm may help it becoming widespread, commonplace and
acceptable, exactly what we try to avoid
Regards
Vladimir 'phcoder' Serbinenko
next prev parent reply other threads:[~2009-02-22 15:33 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 17:43 A _good_ and valid use for TPM Alex Besogonov
2009-02-19 19:30 ` phcoder
2009-02-19 21:00 ` Alex Besogonov
2009-02-20 0:29 ` Jan Alsenz
2009-02-20 1:03 ` Alex Besogonov
2009-02-20 7:47 ` Jan Alsenz
2009-02-22 1:14 ` Alex Besogonov
2009-02-27 19:59 ` Robert Millan
2009-02-21 13:46 ` Robert Millan
2009-02-21 14:20 ` Jan Alsenz
2009-02-21 14:34 ` Robert Millan
2009-02-21 15:00 ` Jan Alsenz
2009-02-21 20:08 ` Robert Millan
2009-02-22 1:21 ` Alex Besogonov
2009-02-22 9:44 ` phcoder
2009-02-22 14:49 ` Michal Suchanek
2009-02-22 15:33 ` phcoder [this message]
2009-02-23 2:34 ` step21
2009-02-23 13:35 ` Michal Suchanek
2009-02-27 20:07 ` Robert Millan
2009-02-27 20:03 ` Robert Millan
2009-02-21 16:29 ` Alex Besogonov
2009-02-21 17:03 ` phcoder
2009-02-21 20:23 ` Robert Millan
2009-02-21 20:21 ` Robert Millan
2009-02-22 1:26 ` Alex Besogonov
2009-02-27 20:13 ` Robert Millan
2009-02-20 7:45 ` Michael Gorven
2009-02-20 11:27 ` phcoder
2009-02-20 12:12 ` Michael Gorven
2009-02-20 17:31 ` Jan Alsenz
2009-02-20 18:35 ` Vesa Jääskeläinen
2009-02-20 19:35 ` Jan Alsenz
2009-02-21 13:59 ` Robert Millan
2009-02-21 13:51 ` Robert Millan
2009-02-21 15:29 ` Michael Gorven
2009-02-21 20:31 ` Robert Millan
2009-02-21 20:43 ` Michael Gorven
2009-02-21 21:04 ` Robert Millan
2009-02-21 21:17 ` Jan Alsenz
2009-02-21 21:27 ` phcoder
2009-02-21 21:32 ` Robert Millan
2009-02-21 21:57 ` Jan Alsenz
2009-02-21 23:19 ` Robert Millan
2009-02-21 21:04 ` Jan Alsenz
2009-02-21 21:27 ` Robert Millan
2009-02-22 2:10 ` Isaac Dupree
2009-02-27 20:28 ` Robert Millan
2009-02-21 16:48 ` Alex Besogonov
2009-02-21 20:39 ` Robert Millan
2009-02-22 1:02 ` Alex Besogonov
2009-02-27 20:33 ` Robert Millan
2009-02-21 16:58 ` Alex Besogonov
2009-02-21 17:08 ` phcoder
2009-02-21 20:43 ` Robert Millan
2009-02-21 13:31 ` Robert Millan
-- strict thread matches above, loose matches on Subject: below --
2009-02-21 2:27 Alex Besogonov
2009-02-18 14:10 Alex Besogonov
2009-02-18 14:52 ` Isaac Dupree
2009-02-18 15:10 ` Alex Besogonov
2009-02-18 22:03 ` Isaac Dupree
2009-02-19 9:46 ` Alex Besogonov
2009-02-18 9:10 Alex Besogonov
2009-02-18 12:16 ` phcoder
[not found] ` <499C7809.6030203@student.ethz.ch>
2009-02-19 10:21 ` Alex Besogonov
2009-02-19 15:05 ` phcoder
2009-02-19 15:38 ` Colin D Bennett
2009-02-19 16:29 ` phcoder
2009-02-21 13:38 ` Robert Millan
2009-02-21 13:43 ` phcoder
2009-02-21 14:00 ` Jan Alsenz
2009-02-19 15:44 ` Michal Suchanek
2009-02-19 16:02 ` phcoder
2009-02-21 13:22 ` Robert Millan
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=49A1705B.7030702@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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.