From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
"Schaufler, Casey" <casey.schaufler@intel.com>,
James Morris <jmorris@namei.org>,
linux-sgx@vger.kernel.org, Dave Hansen <dave.hansen@intel.com>,
Cedric Xing <cedric.xing@intel.com>,
Jethro Beekman <jethro@fortanix.com>,
"Dr . Greg Wettstein" <greg@enjellic.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
LSM List <linux-security-module@vger.kernel.org>
Subject: Re: [RFC PATCH v3 04/12] x86/sgx: Require userspace to define enclave pages' protection bits
Date: Thu, 1 Aug 2019 19:38:39 +0300 [thread overview]
Message-ID: <20190801163839.wvcnq57hity4wwrk@linux.intel.com> (raw)
In-Reply-To: <CALCETrXMAwHod_KZYPGWjTjg-fxOb1=02=Qj2g1o624wOPfPZQ@mail.gmail.com>
On Mon, Jul 15, 2019 at 03:29:23PM -0700, Andy Lutomirski wrote:
> I would say it differently: regardless of exactly how /dev/sgx/enclave
> is wired up under the hood, we want a way that a process can be
> granted permission to usefully run enclaves without being granted
> permission to execute whatever bytes of code it wants. Preferably
> without requiring LSMs to maintain some form of enclave signature
> whitelist.
Would it be better to have a signer whitelist instead or some
combination? E.g. you could whiteliste either by signer or
enclave signature.
/Jarkko
next prev parent reply other threads:[~2019-08-01 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190617222438.2080-1-sean.j.christopherson@intel.com>
[not found] ` <20190617222438.2080-10-sean.j.christopherson@intel.com>
[not found] ` <0c4f75a0ae2fdeee6db07f3a224918f321163d56.camel@linux.intel.com>
[not found] ` <alpine.LRH.2.21.1906200702040.28119@namei.org>
2019-06-23 17:16 ` [RFC PATCH v3 09/12] LSM: x86/sgx: Introduce ->enclave_load() hook for Intel SGX Dr. Greg
2019-06-26 20:39 ` James Morris
[not found] ` <20190617222438.2080-5-sean.j.christopherson@intel.com>
[not found] ` <dc3d59c2783ea81d85d4d447bd1a4a2d5fe51421.camel@linux.intel.com>
[not found] ` <20190619152018.GC1203@linux.intel.com>
[not found] ` <20190620221702.GE20474@linux.intel.com>
[not found] ` <20190707190809.GE19593@linux.intel.com>
[not found] ` <1b7369a08e98dd08a4f8bb19b16479f12bee130f.camel@linux.intel.com>
[not found] ` <20190708161932.GE20433@linux.intel.com>
[not found] ` <20190709160634.3yupyabf5svnj4ds@linux.intel.com>
[not found] ` <20190710172553.GE4348@linux.intel.com>
2019-07-15 22:29 ` [RFC PATCH v3 04/12] x86/sgx: Require userspace to define enclave pages' protection bits Andy Lutomirski
2019-08-01 16:38 ` Jarkko Sakkinen [this message]
2019-08-04 22:20 ` Andy Lutomirski
2019-08-05 20:51 ` Jarkko Sakkinen
2019-08-05 21:30 ` Andy Lutomirski
2019-08-07 18:51 ` 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=20190801163839.wvcnq57hity4wwrk@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=casey.schaufler@intel.com \
--cc=cedric.xing@intel.com \
--cc=dave.hansen@intel.com \
--cc=greg@enjellic.com \
--cc=jethro@fortanix.com \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=sean.j.christopherson@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 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).