lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 14 May 2009 18:45:29 -0700
From:	"Cihula, Joseph" <joseph.cihula@...el.com>
To:	James Morris <jmorris@...ei.org>, Theodore Tso <tytso@....edu>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"hpa@...or.com" <hpa@...or.com>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"chrisw@...s-sol.org" <chrisw@...s-sol.org>,
	"jbeulich@...ell.com" <jbeulich@...ell.com>,
	"peterm@...hat.com" <peterm@...hat.com>,
	"Wei, Gang" <gang.wei@...el.com>,
	"Wang, Shane" <shane.wang@...el.com>, John Gilmore <gnu@...d.com>
Subject: RE: [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel
 support

> From: James Morris [mailto:jmorris@...ei.org]
> Sent: Thursday, May 14, 2009 5:18 PM
>
> On Tue, 12 May 2009, Theodore Tso wrote:
>
> > So we should expect a certain amount of controversy and people
> > lobbying to resist the acceptance of this patch.
>
> FWIW, here's my response to an earlier private enquiry from John on the
> topic:
>
>   I'd prefer discussion to be public, so I don't mind leaving more
>   detailed discussion to that.
>
>   There has been considerable discussion on the issue, following Linus'
>   statement (which I'm sure you're aware of):
>
>   http://marc.info/?l=linux-kernel&m=105115686114064&w=2
>
>   My position is similar -- people can decide for themselves whether they
>   want to use DRM technology.  I'm also confident that technical measures
>   taken to prevent real freedom will always be broken (when have they ever
>   not been?)
>
>   I also feel there may be genuinely useful applications of some of the
>   technology (e.g. sealing disk encryption keys in the TPM a la
>   BitLocker).
>
>
> I'm fairly neutral on the technology itself and feel that "market
> pressure" from users as well as local regulatory policy (e.g. anti-trust
> laws) should determine how the technology is used, rather than the views
> of a few kernel hackers.
>
>
> - James
> --
> James Morris
> <jmorris@...ei.org>

For a balanced view on Trusted Computing, people should also read David Safford's (IBM) rebuttal whitepaper at: http://www.research.ibm.com/gsal/tcpa/tcpa_rebuttal.pdf.

As James points out, there has been a lot written, argued, and debated about Trusted Computing and I would encourage those who are concerned about it to read the discussions and then look at the documentation and presentations on Intel(R) Trusted Execution Technology (Intel(R) TXT).  Any technology can be used for good or bad, but Intel has tried to ensure that users have control of TXT.

I would also encourage those who are concerned about these patches to look at the Linux code and tboot code to satisfy themselves that it is providing exactly what we have claimed.

Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ