From: James Morris <jmorris@namei.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-sgx@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: Some LSM and SGX remarks before parting of for two weeks
Date: Fri, 12 Jul 2019 13:12:23 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1907121303080.17953@namei.org> (raw)
In-Reply-To: <20190712021055.22qijpsahsy3gpmp@linux.intel.com>
On Fri, 12 Jul 2019, Jarkko Sakkinen wrote:
> Before going to a two week vacation (sending v21 today), I'll make some
> remarks on SGX and LSM's:
>
> 1. Currently all patch sets proposing LSM changes are missing a problem
> statement and describe a solution to an undescribed problem.
> 2. When speaking of SELinux I haven't seen any draft's on how would
> define a policy module with the new constructs. Does not have to
> be a full policy modules but more like snippets demosntrating that
> "this would work".
> 3. All the SELinux discussion is centered on type based policies.
> Potentially one could isolate enclaves with some UBAC or RBAC
> based model. That could be good first step and might not even
> require LSM changes.
Unless I misunderstand what you mean here, RBAC and UBAC in SELinux still
require LSM hooks, and are typically integrated with Type Enforcement.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-07-12 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 2:10 Some LSM and SGX remarks before parting of for two weeks Jarkko Sakkinen
2019-07-12 3:12 ` James Morris [this message]
2019-07-12 5:14 ` 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=alpine.LRH.2.21.1907121303080.17953@namei.org \
--to=jmorris@namei.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-sgx@vger.kernel.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).