Linux-Security-Module Archive on lore.kernel.org
 help / color / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>
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 08:14:49 +0300
Message-ID: <20190712051449.sywsnncepdasxjbi@linux.intel.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1907121303080.17953@namei.org>

On Fri, Jul 12, 2019 at 01:12:23PM +1000, James Morris wrote:
> 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.

OK, I was thinking something like with normal DAC just to have SGID
for enclaves. Just learning basic SELinux concepts. Still quite alien
world to me.

/Jarkko

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12  2:10 Jarkko Sakkinen
2019-07-12  3:12 ` James Morris
2019-07-12  5:14   ` Jarkko Sakkinen [this message]

Reply instructions:

You may reply publically 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=20190712051449.sywsnncepdasxjbi@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=jmorris@namei.org \
    --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

Linux-Security-Module Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-security-module/0 linux-security-module/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-security-module linux-security-module/ https://lore.kernel.org/linux-security-module \
		linux-security-module@vger.kernel.org linux-security-module@archiver.kernel.org
	public-inbox-index linux-security-module


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-security-module


AGPL code for this site: git clone https://public-inbox.org/ public-inbox