From: Pavel Machek <pavel@ucw.cz>
To: "Wang, Shane" <shane.wang@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"Cihula, Joseph" <joseph.cihula@intel.com>
Subject: Re: [GIT PULL] x86/txt for v2.6.32
Date: Wed, 30 Sep 2009 08:54:48 +0200 [thread overview]
Message-ID: <20090930065448.GB11652@elf.ucw.cz> (raw)
In-Reply-To: <037F493892196B458CD3E193E8EBAD4F01ED9FE3B1@pdsmsx502.ccr.corp.intel.com>
On Wed 2009-09-30 10:16:55, Wang, Shane wrote:
> Arjan van de Ven wrote:
> > On Tue, 29 Sep 2009 19:13:18 +0200
> > Pavel Machek <pavel@ucw.cz> wrote:
> >
> >> Ok, and what prevents me from commenting out the MAC checking code?
> >>
> >
> > because the bios verified some code that verified the kernel which
> > includes the MAC checking code .. as part of returning from S3 ?
>
> Yes, S3 sleep/resume cause another cycle to build the measured environment.
> i.e. SINIT will verify tboot, tboot will verify kernel mem, kernel will verify userspace mem.
> If you comment out the MAC checking code in any party, the chain will lost and S3 resume will fail.
>
Ok, that means that you are protecting integrity but not secrecy?
Should that be written down in documentation, along with threat model?
So I modify the RAM content so that BIOS does not think measured
environment existed before suspend?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-09-30 6:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 20:51 H. Peter Anvin
2009-09-26 9:56 ` Pavel Machek
2009-09-26 21:44 ` Rafael J. Wysocki
2009-09-28 21:02 ` Pavel Machek
2009-09-28 21:07 ` Rafael J. Wysocki
2009-09-28 21:11 ` H. Peter Anvin
2009-09-28 21:17 ` Pavel Machek
2009-09-29 6:34 ` Shane Wang
2009-09-29 17:13 ` Pavel Machek
2009-09-29 17:19 ` Arjan van de Ven
2009-09-30 2:16 ` Wang, Shane
2009-09-30 6:54 ` Pavel Machek [this message]
2009-10-02 17:02 ` Wang, Shane
2009-10-02 17:18 ` H. Peter Anvin
2009-10-03 15:00 ` Henrique de Moraes Holschuh
2009-10-03 20:19 ` Pavel Machek
2009-10-03 20:36 ` Henrique de Moraes Holschuh
2009-10-03 20:44 ` Roland Dreier
2009-10-06 8:12 ` Pavel Machek
2009-10-07 16:47 ` Cihula, Joseph
2009-10-17 19:28 ` Pavel Machek
2009-10-03 21:10 ` Arjan van de Ven
2009-10-03 21:56 ` Henrique de Moraes Holschuh
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=20090930065448.GB11652@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=joseph.cihula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=shane.wang@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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®