From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LayMS-00026z-OS for mharc-grub-devel@gnu.org; Sat, 21 Feb 2009 15:22:08 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LayMR-00024u-3O for grub-devel@gnu.org; Sat, 21 Feb 2009 15:22:07 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LayMQ-000241-4I for grub-devel@gnu.org; Sat, 21 Feb 2009 15:22:06 -0500 Received: from [199.232.76.173] (port=37645 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LayMP-00023u-GU for grub-devel@gnu.org; Sat, 21 Feb 2009 15:22:05 -0500 Received: from aybabtu.com ([69.60.117.155]:39016) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LayMP-00073X-55 for grub-devel@gnu.org; Sat, 21 Feb 2009 15:22:05 -0500 Received: from [192.168.10.10] (helo=thorin) by aybabtu.com with esmtp (Exim 4.69) (envelope-from ) id 1LayFn-00006p-Em for grub-devel@gnu.org; Sat, 21 Feb 2009 21:15:15 +0100 Received: from rmh by thorin with local (Exim 4.69) (envelope-from ) id 1LayMI-0004t9-HT for grub-devel@gnu.org; Sat, 21 Feb 2009 21:21:58 +0100 Date: Sat, 21 Feb 2009 21:21:58 +0100 From: Robert Millan To: The development of GRUB 2 Message-ID: <20090221202158.GD18492@thorin> References: <499DB343.9020301@gmail.com> <499DF97E.1080800@student.ethz.ch> <20090221134607.GJ16068@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: free as in freedom X-Message-Flag: Worried about Outlook viruses? Switch to Thunderbird! www.mozilla.com/thunderbird X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.18 (2008-05-17) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: A _good_ and valid use for TPM X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2009 20:22:07 -0000 On Sat, Feb 21, 2009 at 06:29:01PM +0200, Alex Besogonov wrote: > On Sat, Feb 21, 2009 at 3:46 PM, Robert Millan wrote: > >> Yes, I'm trying to do remote attestation. > > You're confusing things. I think you simply want to ensure data integrity, and > > the TPM doesn't even do that: it simply puts the problem in hands of a third > > party. > No, I'm not confusing anything. > > > "remote attestation" is only useful when you want to coerce others into > > running your (generaly proprietary) software. I hope this is not what you > > want to do. > It's exactly what I want to do (minus the 'coercing' part). I want to > ensure that devices run only my unmodified software (which I consider > secure) and only in this case provide decryption keys for sensitive > data. Of course, it done not for DRM purposes, but rather to protect > sensitive data from theft (real theft, not copyright infringement). There's no fundamental difference between hardening a device and using that as your root of trust and using someone else's hardened device and using that as your root of trust. The only differences are: - One more link in the trust chain (irrelevant). - Because it's _someone else's_ computer (the TPM), you're irrationally assuming that its security is flawless. - Because it's someone else's computer, this helps them get their foot in your door. Next time you notice, each PC will be verified by one of these, and then you can kiss all your freedom goodbye. > >> Well, I spoke phcoder on Jabber - there might be a way to do this. > >> He's going to investigate it. > > This is unnecessary. Once GRUB supports crypto, it can simply load > > itself from an encrypted filesystem on disk. An image can be of > > arbitrary size. > Nope. Still no way to test system integrity. I was repliing to the idea of implementing sha-1 checks in the MBR. Please don't bring it out of context. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all."