From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Lazsg-0001v0-1T for mharc-grub-devel@gnu.org; Sat, 21 Feb 2009 16:59:30 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lazsd-0001ti-BX for grub-devel@gnu.org; Sat, 21 Feb 2009 16:59:27 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lazsa-0001rm-Sb for grub-devel@gnu.org; Sat, 21 Feb 2009 16:59:25 -0500 Received: from [199.232.76.173] (port=55660 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lazsa-0001re-KV for grub-devel@gnu.org; Sat, 21 Feb 2009 16:59:24 -0500 Received: from xsmtp1.ethz.ch ([82.130.70.13]:19634) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lazsa-0002N8-4g for grub-devel@gnu.org; Sat, 21 Feb 2009 16:59:24 -0500 Received: from xfe1.d.ethz.ch ([82.130.124.41]) by xsmtp1.ethz.ch with Microsoft SMTPSVC(6.0.3790.3959); Sat, 21 Feb 2009 22:59:23 +0100 Received: from [192.168.2.105] ([81.221.97.38]) by xfe1.d.ethz.ch over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sat, 21 Feb 2009 22:59:22 +0100 Message-ID: <49A078DE.6090207@student.ethz.ch> Date: Sat, 21 Feb 2009 22:57:50 +0100 From: Jan Alsenz User-Agent: Thunderbird 2.0.0.19 (X11/20090104) MIME-Version: 1.0 To: The development of GRUB 2 References: <200902211729.52450.michael@gorven.za.net> <20090221203136.GF18492@thorin> <200902212243.31194.michael@gorven.za.net> <20090221210439.GJ18492@thorin> <49A06F4E.1000802@student.ethz.ch> <20090221213201.GB19131@thorin> In-Reply-To: <20090221213201.GB19131@thorin> X-Enigmail-Version: 0.95.7 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig23F94DA8BCA22FE49E2344CC" X-OriginalArrivalTime: 21 Feb 2009 21:59:22.0795 (UTC) FILETIME=[A76C67B0:01C9946F] X-detected-operating-system: by monty-python.gnu.org: Windows 2000 SP4, XP SP1+ 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 21:59:28 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig23F94DA8BCA22FE49E2344CC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Robert Millan wrote: > On Sat, Feb 21, 2009 at 10:17:02PM +0100, Jan Alsenz wrote: >>> First of all, I think it's a poor approach, because there's no way to= garantee >>> the TPM is doing what it's supposed to (can you read its source code?= how do >>> you know for sure there are no backdoors?). >> As I said before: you can make the very same argument for every single= part of >> your PC. >> Why do you trust Intel or AMD with your CPU? They are also involved in= the TCG! >=20 > You took the least relevant part of my argument, and assumed this is th= e reason > I object to TPMs. Please check the rest of my previous mail. I didn't assume that. And I picked this argument because it is the only o= ne I object! Because I think it is not an argument... > Anyway, it's obvious that I trust my CPU because I have no other choice= =2E The > context in which I said this, is different: there are better choices th= ere. =2E.. and since you seem to agree, please don't use it. You seem to assume, that I really like the idea of a TPM, or something li= ke that. I can assure you, that this is not the case. My only goal is to keep the discussion based on facts and reason. Which way too often get lost in thi= s kind of discussion (and I want to stress that this is not an accusation to any= one here). Greets, Jan --------------enig23F94DA8BCA22FE49E2344CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmgeOQACgkQfZylhtn4XvcAQACfUCh+ADDCKpHkRI9qd3e5jMr+ K9kAn1iPQ60OGL0PfMy/0A202EU+RVIs =fWWJ -----END PGP SIGNATURE----- --------------enig23F94DA8BCA22FE49E2344CC--