From: Peng Fan <peng.fan@nxp.com>
To: Volodymyr Babchuk <vlad.babchuk@gmail.com>
Cc: Julien Grall <julien@xen.org>,
Oleksandr Andrushchenko <Oleksandr_Andrushchenko@epam.com>,
"tee-dev@lists.linaro.org" <tee-dev@lists.linaro.org>,
Xen-devel <xen-devel@lists.xenproject.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Stefano Babic <sbabic@denx.de>
Subject: RE: [Tee-dev] TEE with XEN
Date: Tue, 16 Jun 2020 02:02:20 +0000 [thread overview]
Message-ID: <DB6PR0402MB2760E57975E39930582D8A61889D0@DB6PR0402MB2760.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOcqxo2B4cnJdqERr81rVzJKb=Rj=kmotd7Cui9nOMy52wVKmg@mail.gmail.com>
Hi,
> Subject: Re: [Tee-dev] TEE with XEN
>
> Hi Peng,
>
> On Mon, 15 Jun 2020 at 05:07, Peng Fan <peng.fan@nxp.com> wrote:
> >
> > Hi All,
> >
> > While enabling trusty os with xen, I took same approach as OP-TEE,
> > with OP-TEE running in secure world. But I am also thinking this might
> > introduce potential issue is that secure world OS communicate with DomU.
> > If there are some misbehavior in secure world OS, it might let XEN
> > hypervisor not work proper.
> >
> > In my setup, trusty os sometimes panic in secure world, xen will not
> > able to control the panic core anymore.
> >
> > So I am thinking whether we need to emulating secure world in a XEN VM
> > which is the VM running DomU. Just like what ACRN did to run trusty
> > os.
>
> Well, it depends on whom you are trusting more. Both XEN and TEE are
> minimal OS implementations with aim at security.
XEN is targeting safety.
TEE is targeting security.
I'm speaking about generic
> TEE OS, not about particular OS like OP-TEE or Trusty. Problem is that, if TEE is
> running inside VM, it will be susceptible to a hypervisor misbehaviour. You
> need to understand that Xen and privileged domain (dom0, mostly) can access
> memory of any guest.
> At least, in default configuration. There are means to harden this setup. But
> anyways, Xen can't be stopped from reading TEE's secrets.
Yes. Understand.
>
> If this is okay for your needs, then you can run TEE as a VM of course.
>
> So, this is heavilly depends on your security threats model. There can't be
> universal solution. Also, I'm proposing to check Google's requirements for
> Trusty environment.
Let me try to ask Google guys to see any feedback.
Thanks,
Peng.
> Do they allow it to run outside of TrustZone? For example, GPD TEE System
> Architecture document clearly says that TEE should be separated from REE by
> hardware mechanisms that are not controlled by REE (section 2.2.1). I believe,
> that should be a similar document for Trusty.
>
> --
> WBR Volodymyr Babchuk aka lorc [+380976646013]
> mailto: vlad.babchuk@gmail.com
next prev parent reply other threads:[~2020-06-16 2:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 2:07 TEE with XEN Peng Fan
2020-06-16 1:24 ` [Tee-dev] " Volodymyr Babchuk
2020-06-16 2:02 ` Peng Fan [this message]
2020-06-18 18:05 ` Julien Grall
2020-06-18 22:17 ` Stefano Stabellini
2020-06-19 8:49 ` Bertrand Marquis
2020-06-19 8:45 ` Bertrand Marquis
2020-06-19 8:52 ` Peng Fan
2020-06-19 8:58 ` Bertrand Marquis
2020-06-19 9:05 ` Peng Fan
2020-06-19 9:12 ` Volodymyr Babchuk
2020-06-19 9:50 ` Peng Fan
2020-06-19 10:11 ` Volodymyr Babchuk
2020-06-19 9:51 ` Bertrand Marquis
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=DB6PR0402MB2760E57975E39930582D8A61889D0@DB6PR0402MB2760.eurprd04.prod.outlook.com \
--to=peng.fan@nxp.com \
--cc=Oleksandr_Andrushchenko@epam.com \
--cc=jens.wiklander@linaro.org \
--cc=julien@xen.org \
--cc=sbabic@denx.de \
--cc=tee-dev@lists.linaro.org \
--cc=vlad.babchuk@gmail.com \
--cc=xen-devel@lists.xenproject.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).