All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@redhat.com>,
	pmoore@redhat.com, mgrepl@redhat.com
Cc: selinux@tycho.nsa.gov
Subject: Re: Strange AVC with latest rawhide kernel.
Date: Thu, 25 Feb 2016 15:36:11 -0500	[thread overview]
Message-ID: <1456432571.3702.69.camel@redhat.com> (raw)
In-Reply-To: <56CF5A54.7020600@tycho.nsa.gov>

On Thu, 2016-02-25 at 14:47 -0500, Stephen Smalley wrote:
> On 02/25/2016 02:37 PM, Eric Paris wrote:
> > 
> > You added a type bounds right before this broke...  Does the parent
> > type have entrypoint? If not, maybe that's where it got stripped...
> That would match the behavior he described (although he should get
> an 
> audit message of the form op=security_compute_av reason=bounds.. in 
> audit.log or dmesg in that case).  The kernel automatically reduces 
> permissions as required by typebounds.  The corresponding logic
> never 
> made its way into the libsepol compute_av code, so audit2why
> wouldn't 
> know about it, and sesearch merely searches for TE rules; it doesn't
> do 
> anything about typebounds.  We should probably update libsepol 
> compute_av (for that, and eventually for xperms).

Eric is right.  I added the following policy and got the error again.

policy_module(mypol, 1.0)

require {
	type svirt_lxc_net_t;
	type docker_t;
}
typebounds docker_t svirt_lxc_net_t;


Then I added this policy and it worked.

policy_module(mypol, 1.0)

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

So typebounds removed the entrypoint access from svirt_lxc_net_t, but
none of the tools realized this.

  parent reply	other threads:[~2016-02-25 20:36 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
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 [this message]
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=1456432571.3702.69.camel@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=eparis@redhat.com \
    --cc=mgrepl@redhat.com \
    --cc=pmoore@redhat.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.