From: Ross Philipson <ross.philipson@oracle.com>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, corbet@lwn.net,
konrad.wilk@oracle.com, kanth.ghatraju@oracle.com,
daniel.kiper@oracle.com, boris.ostrovsky@oracle.com,
dpsmith@apertussolutions.com, ross.philipson@oracle.com
Subject: [PATCH 0/1] [RFC] Secure Launch boot protocol
Date: Mon, 11 Mar 2019 11:04:22 -0400 [thread overview]
Message-ID: <20190311150423.15979-1-ross.philipson@oracle.com> (raw)
All,
As is noted in the patch that follows, the open source project called
Trenchboot aims to make Linux directly bootable into a secure late launch
environment via Intel TXT or AMD SKINIT. This new feature is referred to as
Secure Launch as seen in the subject lines. In addition to changes to the
Linux kernel to support this feature, boot loaders will also have additional
functionality to initiate the secure late launch.
The patch that follows introduces a new boot parameter. There are of course
other patches that add further functionality to achieve our aims including the
changes to boot loaders that consume this parameter. This posting is as an early
RFC to elicit feedback on whether this is an acceptable approach for our boot
protocol and an acceptable usage of boot parameters.
The project is in its early stages; it is hosted here:
https://github.com/trenchboot
For an overview of the Secure Launch architecture:
https://github.com/TrenchBoot/documentation/blob/master/documentation/Architecture.md"
Links:
https://www.intel.com/content/dam/www/public/us/en/documents/guides/intel-txt-software-development-guide.pdf
https://www.amd.com/system/files/TechDocs/24593.pdf
Thank you,
Ross Philipson
Ross Philipson (1):
x86: Secure Launch boot protocol
Documentation/x86/boot.txt | 15 +++++++++++++++
arch/x86/Kconfig | 7 +++++++
arch/x86/boot/Makefile | 2 +-
arch/x86/boot/header.S | 3 ++-
arch/x86/boot/tools/build.c | 16 ++++++++++++++++
arch/x86/include/uapi/asm/bootparam.h | 1 +
6 files changed, 42 insertions(+), 2 deletions(-)
--
2.13.6
next reply other threads:[~2019-03-11 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 15:04 Ross Philipson [this message]
2019-03-11 15:04 ` [PATCH 1/1] x86: " Ross Philipson
2019-03-12 17:34 ` hpa
2019-03-14 18:53 ` Konrad Rzeszutek Wilk
2019-03-15 2:21 ` hpa
2019-03-28 18:15 ` [PATCH 0/1] [RFC] " H. Peter Anvin
2019-03-28 18:37 ` Daniel Kiper
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=20190311150423.15979-1-ross.philipson@oracle.com \
--to=ross.philipson@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.kiper@oracle.com \
--cc=dpsmith@apertussolutions.com \
--cc=hpa@zytor.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®