From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Dr. Greg Wettstein" <gw@idfusion.org>
Cc: Jethro Beekman <jethro@fortanix.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Andy Lutomirski <luto@kernel.org>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"serge.ayoun@intel.com" <serge.ayoun@intel.com>,
"shay.katz-zamir@intel.com" <shay.katz-zamir@intel.com>
Subject: Re: x86/sgx: v23-rc2
Date: Tue, 18 Feb 2020 17:52:47 +0200 [thread overview]
Message-ID: <20200218155247.GA18374@linux.intel.com> (raw)
In-Reply-To: <20200218104243.GA13967@wind.enjellic.com>
On Tue, Feb 18, 2020 at 04:42:43AM -0600, Dr. Greg Wettstein wrote:
> I believe an accurate summary of Dr. Beekman's concerns are as
> follows:
>
> 1.) He envisions a need for an enclave orchestrator that uses root
> privileges to open the SGX driver device and then drop privileges,
> presumably in a permanent fashion. The orchestrator would then use
> the filehandle to load and initialize multiple enclaves on request.
>
> 2.) The enclave orchestrator may be run in an environment that has
> SECCOMP limitations on the ability to conduct filesystem operations.
Also UDS sockets with SCM_RIGHTS should work.
/Jarkko
next prev parent reply other threads:[~2020-02-18 15:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 11:37 x86/sgx: v23-rc2 Jarkko Sakkinen
2019-10-10 13:37 ` Jarkko Sakkinen
2019-10-10 17:09 ` Sean Christopherson
2019-10-10 17:39 ` Sean Christopherson
2019-10-11 16:37 ` Jethro Beekman
2019-10-11 18:15 ` Sean Christopherson
2019-10-14 8:43 ` Jethro Beekman
2019-10-17 17:57 ` Sean Christopherson
2020-02-13 14:10 ` Jethro Beekman
2020-02-15 7:24 ` Jarkko Sakkinen
2020-02-17 8:52 ` Jethro Beekman
2020-02-17 18:55 ` Jarkko Sakkinen
2020-02-17 18:56 ` Jarkko Sakkinen
2020-02-18 10:42 ` Dr. Greg Wettstein
2020-02-18 15:00 ` Andy Lutomirski
2020-02-22 3:16 ` Dr. Greg
2020-02-22 5:41 ` Andy Lutomirski
2020-03-01 10:42 ` Dr. Greg
2020-02-23 17:13 ` Jarkko Sakkinen
2020-02-18 15:52 ` Jarkko Sakkinen [this message]
2020-02-19 16:26 ` Dr. Greg
2020-02-20 19:57 ` Jarkko Sakkinen
2020-02-21 1:19 ` Dr. Greg
2020-02-21 13:00 ` Jarkko Sakkinen
2020-03-05 19:51 ` Sean Christopherson
2020-03-05 20:34 ` Jethro Beekman
2020-03-05 21:00 ` Sean Christopherson
2020-03-06 18:34 ` Jarkko Sakkinen
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=20200218155247.GA18374@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gw@idfusion.org \
--cc=jethro@fortanix.com \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=serge.ayoun@intel.com \
--cc=shay.katz-zamir@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.