|| ||"Tom \"spot\" Callaway" <tcallawa-H+wXaHxf7aLQT0dZR+AlfA-AT-public.gmane.org> |
|| ||Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA-AT-public.gmane.org> |
|| ||Re: enable CONFIG_INTEL_TXT |
|| ||Thu, 01 Apr 2010 09:54:46 -0400|
|| ||Eric Paris <eparis-H+wXaHxf7aLQT0dZR+AlfA-AT-public.gmane.org>, gcwilson-r/Jw6+rmf7HQT0dZR+AlfA-AT-public.gmane.org,
James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg-AT-public.gmane.org>, kernel-TuqUDEhatI4ANWPb/1PvSmm0pvjS0E/A-AT-public.gmane.org|
|| ||Article, Thread
On 04/01/2010 09:38 AM, Stephen Smalley wrote:
> As far as I know the security of TXT in no way relies upon keeping the
> SINIT module closed source.
And yet, Intel refuses to open source it, quite adamantly.
On top of that, even if they did open source it, the hardcoded key
requirement prevents anyone from actually using the SINIT module when
built from source (well, except perhaps Intel and whomever they gave the
to post comments)