| 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
| ||
|
Date: Fri, 29 May 2009 11:47:54 +0200 From: Pavel Machek <pavel@....cz> To: rms <rms@....org> Cc: Theodore Tso <tytso@....edu>, joseph.cihula@...el.com, jmorris@...ei.org, linux-kernel@...r.kernel.org, mingo@...e.hu, arjan@...ux.intel.com, hpa@...or.com, andi@...stfloor.org, chrisw@...s-sol.org, jbeulich@...ell.com, peterm@...hat.com, gang.wei@...el.com, shane.wang@...el.com, gnu@...d.com Subject: Re: [RFC v3][PATCH 2/2] intel_txt: Intel(R) TXT and tboot kernel support On Wed 2009-05-27 13:15:14, rms wrote: > This scheme must be very different from anything I've heard of before. > Can you tell me where to find a description? > I want to study whether it really avoids being affected by GPLv3, > and how we can fight against it. Some description is here: http://en.wikipedia.org/wiki/Trusted_Execution_Technology . And yes, I believe it avoids GPLv3: TXT allows user (I _hope_ it is root-only) to boot tamper-free sandbox. As long as Windows (or something) runs in the sandbox, I believe even GPLv3 would allow that. OTOH... I do not think mainline kernel should support this. It does not add anything to the user's security, and allows all kinds of nasty DRMs. 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/
Powered by blists - more mailing lists