From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, monty.wiseman@ge.com,
Monty Wiseman <montywiseman32@gmail.com>,
Matthew Garrett <mjg59@google.com>
Subject: Re: Documenting the proposal for TPM 2.0 security in the face of bus interposer attacks
Date: Wed, 21 Nov 2018 11:14:35 +0200 [thread overview]
Message-ID: <20181121091435.GA10223@linux.intel.com> (raw)
In-Reply-To: <20181121071819.GD3640@linux.intel.com>
On Wed, Nov 21, 2018 at 09:18:19AM +0200, Jarkko Sakkinen wrote:
> On Tue, Nov 20, 2018 at 10:42:01PM -0700, Jason Gunthorpe wrote:
> > > Why you wouldn't use DMA to spy the RAM?
> >
> > The platform has to use IOMMU to prevent improper DMA access from
> > places like PCI-E slots if you are using measured boot and want to
> > defend against HW tampering.
>
> Yes. This is what I wanted to point out. Windows 10 has VBS to
> achieve something like this.
>
> https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/oem-vbs
Some trials like Qubes are in existence (uses Xen).
I've been thinking should Linux have a thin hypervisor solely for VBS
like use in order to gain wider adoption.
/Jarkko
next prev parent reply other threads:[~2018-11-21 9:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 17:34 Documenting the proposal for TPM 2.0 security in the face of bus interposer attacks James Bottomley
2018-11-19 20:05 ` Jason Gunthorpe
2018-11-19 20:20 ` James Bottomley
2018-11-19 21:19 ` Jason Gunthorpe
2018-11-19 21:34 ` James Bottomley
2018-11-19 21:44 ` Jason Gunthorpe
2018-11-19 22:36 ` James Bottomley
2018-11-19 23:08 ` Jason Gunthorpe
2018-11-20 0:54 ` James Bottomley
2018-11-20 3:05 ` Jason Gunthorpe
2018-11-20 17:17 ` James Bottomley
2018-11-20 21:33 ` Jason Gunthorpe
2018-11-20 22:34 ` James Bottomley
2018-11-20 23:39 ` Jason Gunthorpe
2018-11-21 2:24 ` EXTERNAL: " Jeremy Boone
2018-11-21 5:16 ` Jason Gunthorpe
2018-11-20 23:52 ` Jarkko Sakkinen
2018-11-20 23:41 ` Jarkko Sakkinen
2018-11-20 11:10 ` Jarkko Sakkinen
2018-11-20 12:41 ` Jarkko Sakkinen
2018-11-20 17:25 ` James Bottomley
2018-11-20 23:13 ` Jarkko Sakkinen
2018-11-20 23:58 ` James Bottomley
2018-11-21 0:33 ` EXTERNAL: " Jeremy Boone
2018-11-21 6:37 ` Jarkko Sakkinen
2018-11-21 5:42 ` Jason Gunthorpe
2018-11-21 7:18 ` Jarkko Sakkinen
[not found] ` <F10185EF-C618-45DC-B1F3-0053B8FE417F@gmail.com>
2018-11-21 9:07 ` Jarkko Sakkinen
2018-11-21 9:14 ` Jarkko Sakkinen [this message]
2018-11-20 17:23 ` James Bottomley
2018-11-20 23:12 ` Jarkko Sakkinen
2018-12-10 16:33 ` Ken Goldman
2018-12-10 17:30 ` James Bottomley
2018-12-11 21:47 ` Ken Goldman
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=20181121091435.GA10223@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.com \
--cc=monty.wiseman@ge.com \
--cc=montywiseman32@gmail.com \
/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).