From: Kees Cook <keescook@chromium.org>
To: Borislav Petkov <bp@alien8.de>, Kees Cook <keescook@chromium.org>,
Matthew Garrett <matthew.garrett@nebula.com>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] x86: Lock down MSR writing in secure boot
Date: Sat, 9 Feb 2013 07:10:16 -0800 [thread overview]
Message-ID: <CAGXu5j+XTq6vyn176fHCDDgkLtVyBwEC8J3DUDVhy9z87ODF2Q@mail.gmail.com> (raw)
In-Reply-To: <20130209092925.GA17728@pd.tnic>
On Sat, Feb 9, 2013 at 1:29 AM, Borislav Petkov <bp@alien8.de> wrote:
> On Fri, Feb 08, 2013 at 10:45:35PM -0800, Kees Cook wrote:
>> Also, _reading_ MSRs from userspace arguably has utility that doesn't
>> compromise ring-0.
>
> And to come back to the original question: what is that utility, who
> would need it on a secure boot system and why?
I have used it for double-checking the state of VMX (is it disabled
and locked), and for making sure that XD isn't masked, checking
thermal stuff, etc. I'm not arguing to keep the MSR driver while in
secure mode, mind you, I was just pointing out that like /dev/mem
there could be some utility to keeping the read half around. That
said, it could also be seen as an info leak. *shrug* My goal was just
to make sure it wasn't writable in the secure boot mode.
-Kees
--
Kees Cook
Chrome OS Security
next prev parent reply other threads:[~2013-02-09 15:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 19:12 [PATCH] x86: Lock down MSR writing in secure boot Kees Cook
2013-02-08 19:17 ` H. Peter Anvin
2013-02-08 19:18 ` Kees Cook
2013-02-08 19:42 ` H. Peter Anvin
2013-02-08 20:14 ` Kees Cook
2013-02-08 20:18 ` H. Peter Anvin
2013-02-08 20:28 ` Kees Cook
2013-02-08 20:34 ` Matthew Garrett
2013-02-08 21:02 ` Kees Cook
2013-02-08 21:07 ` Matthew Garrett
2013-02-08 21:14 ` Josh Boyer
2013-02-08 23:09 ` Andy Lutomirski
2013-02-08 22:30 ` H. Peter Anvin
2013-02-08 23:06 ` Borislav Petkov
2013-02-08 23:26 ` Matthew Garrett
2013-02-09 1:22 ` H. Peter Anvin
2013-02-09 1:29 ` Matthew Garrett
2013-02-09 6:45 ` Kees Cook
2013-02-09 9:29 ` Borislav Petkov
2013-02-09 15:10 ` Kees Cook [this message]
2013-02-09 15:11 ` Matthew Garrett
2013-02-13 0:48 ` H. Peter Anvin
2013-02-13 5:39 ` Matthew Garrett
2013-02-13 6:12 ` H. Peter Anvin
2013-02-13 6:27 ` Matthew Garrett
2013-02-13 6:33 ` H. Peter Anvin
2013-02-13 6:41 ` Matthew Garrett
2013-02-13 17:20 ` H. Peter Anvin
2013-02-13 17:26 ` Matthew Garrett
2013-02-13 17:51 ` Casey Schaufler
2013-02-13 17:56 ` Matthew Garrett
2013-02-13 18:44 ` H. Peter Anvin
2013-02-13 18:51 ` Matthew Garrett
2013-02-13 22:26 ` H. Peter Anvin
2013-02-13 22:58 ` Casey Schaufler
2013-02-14 0:25 ` H. Peter Anvin
2013-02-14 0:44 ` Casey Schaufler
2013-02-14 1:04 ` Matthew Garrett
2013-02-14 1:08 ` H. Peter Anvin
2013-02-14 2:46 ` Matthew Garrett
2013-02-14 1:34 ` Casey Schaufler
2013-02-13 8:27 ` Paolo Bonzini
2013-02-13 17:21 ` H. Peter Anvin
2013-02-13 17:22 ` H. Peter Anvin
2013-02-13 19:55 ` Paolo Bonzini
2013-02-13 22:24 ` H. Peter Anvin
2013-02-08 19:17 ` Matthew Garrett
2013-02-08 19:21 ` Kees Cook
2013-02-08 19:27 ` Matthew Garrett
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=CAGXu5j+XTq6vyn176fHCDDgkLtVyBwEC8J3DUDVhy9z87ODF2Q@mail.gmail.com \
--to=keescook@chromium.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthew.garrett@nebula.com \
--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;
as well as URLs for NNTP newsgroup(s).