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: Strange AVC with latest rawhide kernel.
Date: Thu, 25 Feb 2016 13:02:49 -0500 [thread overview]
Message-ID: <1456423369.3702.42.camel@redhat.com> (raw)
audit2allow -wla
type=AVC msg=audit(1456422969.279:1434): avc: denied { entrypoint }
for pid=23847 comm="exe" path="/usr/bin/bash" dev="dm-2" ino=25165968
scontext=system_u:system_r:svirt_lxc_net_t:s0:c337,c895
tcontext=system_u:object_r:svirt_sandbox_file_t:s0:c337,c895
tclass=file permissive=0
Was caused by:
Unknown - would be allowed by active policy
Possible mismatch between this policy and the one under
which the audit message was generated.
Possible mismatch between current in-memory boolean
settings vs. permanent ones.
When trying to run a docker container on Rawhide, I am seeing this AVC.
The policy as audit2allow -w shows allows svirt_sandbox_file_t as an
entrypoint for svirt_lxc_net_t.
# sesearch -A -s svirt_lxc_net_t -t svirt_sandbox_file_t -c file -p
entrypoint
Found 1 semantic av rules:
allow svirt_sandbox_domain file_type : file entrypoint ;
But when I run try to start the container, docker blocks the access. I
don't see any constraints that would block this, and don't think
NO_NEW_PRIV is enabled any way, and I don't think it would be involved
here.
Any idea why SELinux is blocking the access?
next reply other threads:[~2016-02-25 18:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 18:02 Daniel J Walsh [this message]
2016-02-25 18:06 ` Strange AVC with latest rawhide kernel 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
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=1456423369.3702.42.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.