All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, Paul Moore <paul@paul-moore.com>
Cc: selinux@tycho.nsa.gov, Eric Paris <eparis@redhat.com>
Subject: Re: Strange AVC with latest rawhide kernel.
Date: Fri, 26 Feb 2016 11:33:46 -0500	[thread overview]
Message-ID: <1456504426.3481.44.camel@redhat.com> (raw)
In-Reply-To: <56D07421.3090301@tycho.nsa.gov>

On Fri, 2016-02-26 at 10:49 -0500, Stephen Smalley wrote:
> On 02/26/2016 10:46 AM, Paul Moore wrote:
> > 
> > On Fri, Feb 26, 2016 at 7:54 AM, Daniel J Walsh <dwalsh@redhat.com>
> > wrote:
> > > 
> > > On Thu, 2016-02-25 at 15:54 -0500, Stephen Smalley wrote:
> > > > 
> > > > On 02/25/2016 03:28 PM, Daniel J Walsh wrote:
> > > > > 
> > > > > Currently typebounds only allows one instance.
> > > > It is a hierarchy, where each child has a single parent.  So
> > > > you can
> > > > define hierarchies like:
> > > > typebounds unconfined_t docker_t;
> > > > typebounds docker_t svirt_lxc_net_t;
> > > > and then they can both transition because they are both
> > > > ancestors.
> > > Awesome idea.
> > Would that resolve all your problems Dan with Docker, runc, etc.?
> > > 
> > > From our discussions the other day I thought you needed the
> > > ability to
> > transition to svirt_lxc_net_t from domains other than unconfined_t
> > and
> > docker_t ... or was I misunderstanding you?
> > 
> Note that it is only exec-based transitions that are affected by 
> NO_NEW_PRIVS, so one can always leverage dynamic transitions (i.e. 
> setcon) without requiring typebounds.
> 
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to Selinux-request@tycho
> .nsa.gov.
> 
> 

BTW I turned on the expand-check=1 in semanage.conf and semodule -B
went nuts and crashed.

On this policy.

policy_module(mypol, 1.0)

require {
	type svirt_lxc_net_t;
	type docker_t;
	type svirt_sandbox_file_t;
	type unconfined_t;
}
allow unconfined_t svirt_sandbox_file_t:file entrypoint;
allow docker_t svirt_sandbox_file_t:file entrypoint;
typebounds unconfined_t docker_t;
typebounds docker_t svirt_lxc_net_t;

  reply	other threads:[~2016-02-26 16:33 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 18:02 Strange AVC with latest rawhide kernel Daniel J Walsh
2016-02-25 18:06 ` Stephen Smalley
2016-02-25 18:18 ` Stephen Smalley
2016-02-25 18:59   ` Daniel J Walsh
2016-02-25 19:12     ` Stephen Smalley
2016-02-25 19:36       ` Daniel J Walsh
2016-02-25 19:37       ` Eric Paris
2016-02-25 19:47         ` Stephen Smalley
2016-02-25 20:28           ` Daniel J Walsh
2016-02-25 20:54             ` Stephen Smalley
2016-02-26 12:54               ` Daniel J Walsh
2016-02-26 15:46                 ` Paul Moore
2016-02-26 15:49                   ` Stephen Smalley
2016-02-26 16:33                     ` Daniel J Walsh [this message]
2016-02-26 19:50                       ` James Carter
2016-02-26 20:30                         ` Daniel J Walsh
2016-02-29 16:27                           ` James Carter
2016-02-29 17:27                             ` Daniel J Walsh
2016-02-26 17:13                     ` Paul Moore
2016-02-26 19:41                       ` Daniel J Walsh
2016-02-26 16:31                   ` Daniel J Walsh
2016-02-26 17:15                     ` Paul Moore
2016-02-26 19:42                       ` Daniel J Walsh
2016-02-25 20:36           ` Daniel J Walsh
2016-02-29 10:10             ` Miroslav Grepl
2016-02-25 19:25   ` Daniel J Walsh
2016-02-25 19:05 ` Paul Moore

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=1456504426.3481.44.camel@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=eparis@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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.