From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Cihula, Joseph" <joseph.cihula@intel.com>
Cc: linux-kernel@vger.kernel.org, "Wang,
Shane" <shane.wang@intel.com>, "Wei, Gang" <gang.wei@intel.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Chris Wright <chrisw@redhat.com>,
Jan Beulich <jbeulich@novell.com>,
mingo@elte.hu, tytso@mit.edu
Subject: Re: [RFC][PATCH 3/3] TXT: Intel(R) TXT and tboot kernel support
Date: Thu, 09 Oct 2008 10:25:05 -0700 [thread overview]
Message-ID: <48EE3E71.8010604@goop.org> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892005AC10E3@orsmsx416.amr.corp.intel.com>
Cihula, Joseph wrote:
> --- a/security/Kconfig Mon Oct 06 12:50:47 2008 -0700
> +++ b/security/Kconfig Tue Oct 07 00:13:02 2008 -0700
> @@ -115,6 +115,23 @@ config SECURITY_DEFAULT_MMAP_MIN_ADDR
> /proc/sys/vm/mmap_min_addr tunable.
>
>
> +config TXT
>
This should be X86_TXT; perhaps even X86_INTEL_TXT unless someone else
is likely to implement this stuff. ("TXT" is awfully generic.)
> + bool "Enable Intel(R) Trusted Execution Technology (TXT)"
> + depends on EXPERIMENTAL && X86
> + help
> + This option enables support for booting the kernel with
> + the Trusted Boot (tboot) module. This will utilize
> + Intel(R) Trusted Execution Technology (TXT) to perform a
> + measured launch of the kernel. If the system does not
> + support TXT, this will have no effect.
> +
> + See <http://www.intel.com/technology/security/> for more
> + information about Intel(R) TXT.
> + And see <http://tboot.sourceforge.net> for more information
> + about tboot.
> +
> + If you are unsure as to whether this is required, answer N.
> +
> source security/selinux/Kconfig
> source security/smack/Kconfig
>
J
next prev parent reply other threads:[~2008-10-09 17:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 20:34 [RFC][PATCH 3/3] TXT: Intel(R) TXT and tboot kernel support Cihula, Joseph
2008-10-07 21:05 ` James Morris
2008-10-07 21:09 ` Cihula, Joseph
2008-10-07 21:44 ` James Morris
2008-10-09 13:05 ` Pavel Machek
2008-10-09 17:50 ` Chris Wright
2008-10-09 20:35 ` Cihula, Joseph
2008-10-09 21:34 ` Chris Wright
2008-10-09 17:25 ` Jeremy Fitzhardinge [this message]
2008-10-09 18:28 ` Chris Wright
2008-10-09 18:39 ` Cihula, Joseph
2008-10-08 0:52 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 23:29 Joseph Cihula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EE3E71.8010604@goop.org \
--to=jeremy@goop.org \
--cc=arjan.van.de.ven@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=chrisw@redhat.com \
--cc=gang.wei@intel.com \
--cc=jbeulich@novell.com \
--cc=joseph.cihula@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shane.wang@intel.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox