linux-kernel - Re: [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support

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:	Sun, 24 May 2009 21:42:31 +0200
From:	Pavel Machek <pavel@....cz>
To:	"Cihula, Joseph" <joseph.cihula@...el.com>
Cc:	James Morris <jmorris@...ei.org>, Theodore Tso <tytso@....edu>,
	"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>,
	pavel@....cz
Subject: Re: [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel
	support

Hi!

> >   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?)

Linus says he hates drm but does not want to stop it through legal
means, because its impossible. Does that mean we should merge any
random drm crap? I hope not.

> >   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.

So some of the technology is useful -> we merge all of it?

> 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.

Sorry, but that article is full of hype, nothing balanced on it. Plus
it speaks about different technology. Plus it is intentionally
misleading.

>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 don't see where you got that nonsense.

Try using atomic bomb for something good. Then try to use tv remote
control for something bad.

TXT was specifically designed to enable atomic bombs^W^W drm, and I
see no other reasonable use.
 
> 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.

I certainly hope booting secure sandbox is root-only operation... is
it?
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/