diff options
| author | Eric Paris <eparis@redhat.com> | 2009-03-05 13:40:35 -0500 |
|---|---|---|
| committer | James Morris <jmorris@namei.org> | 2009-03-06 08:50:18 +1100 |
| commit | 6a25b27d602aac24f3c642722377ba5d778417ec (patch) | |
| tree | ba334617326c65ccd98e7f4733c75fa0ac2ae5ca /net/bluetooth/cmtp/sock.c | |
| parent | 113a0e4590881ce579ca992a80ddc562b3372ede (diff) | |
| download | blackbird-op-linux-6a25b27d602aac24f3c642722377ba5d778417ec.tar.gz blackbird-op-linux-6a25b27d602aac24f3c642722377ba5d778417ec.zip | |
SELinux: open perm for sock files
When I did open permissions I didn't think any sockets would have an open.
Turns out AF_UNIX sockets can have an open when they are bound to the
filesystem namespace. This patch adds a new SOCK_FILE__OPEN permission.
It's safe to add this as the open perms are already predicated on
capabilities and capabilities means we have unknown perm handling so
systems should be as backwards compatible as the policy wants them to
be.
https://bugzilla.redhat.com/show_bug.cgi?id=475224
Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'net/bluetooth/cmtp/sock.c')
0 files changed, 0 insertions, 0 deletions
