Bug 878354 - CIM providers can't use cimxml.socket
Summary: CIM providers can't use cimxml.socket
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-20 09:08 UTC by Radek Novacek
Modified: 2016-12-01 00:31 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-07 04:32:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Radek Novacek 2012-11-20 09:08:09 UTC
I'm getting following AVC denial:

time->Tue Nov 20 10:01:12 2012
type=SYSCALL msg=audit(1353402072.877:816): arch=c000003e syscall=42 success=no exit=-13 a0=7 a1=7f09c21aae80 a2=6e a3=20 items=0 ppid=1 pid=2069 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="cimprovagt" exe="/usr/sbin/cimprovagt" subj=system_u:system_r:pegasus_t:s0 key=(null)
type=AVC msg=audit(1353402072.877:816): avc:  denied  { write } for  pid=2069 comm="cimprovagt" name="cimxml.socket" dev="tmpfs" ino=20335 scontext=system_u:system_r:pegasus_t:s0 tcontext=system_u:object_r:pegasus_var_run_t:s0 tclass=sock_file

This causes that CIM providers don't work at all.

selinux-policy-3.11.1-54.fc18.noarch
tog-pegasus-2.11.1-11.fc18.x86_64

Comment 1 Miroslav Grepl 2012-11-20 12:09:46 UTC
Fixed in selinux-policy-3.11.1-55.fc18

Comment 2 Radek Novacek 2012-11-23 13:36:23 UTC
Thank you, -55 fixes the issue, but another problem appears once the previous one disappears:

type=SYSCALL msg=audit(1353684774.859:377): arch=c000003e syscall=42 success=no exit=-13 a0=7 a1=7f0e5f162eb0 a2=6e a3=20 items=0 ppid=1 pid=1164 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="cimprovagt" exe="/usr/sbin/cimprovagt" subj=system_u:system_r:pegasus_t:s0 key=(null)
type=AVC msg=audit(1353684774.859:377): avc:  denied  { connectto } for  pid=1164 comm="cimprovagt" path="/run/tog-pegasus/cimxml.socket" scontext=system_u:system_r:pegasus_t:s0 tcontext=system_u:system_r:pegasus_t:s0 tclass=unix_stream_socket

Could you fix that too?

Comment 3 Miroslav Grepl 2012-11-23 14:39:40 UTC
Radek,
could you switch to permissive to see if you get more AVC msgs?

Comment 4 Radek Novacek 2012-11-23 14:59:20 UTC
Thanks for the tip, I'm also getting following two AVC messages:

time->Fri Nov 23 15:49:02 2012
type=SYSCALL msg=audit(1353682142.653:2375): arch=c000003e syscall=2 success=yes exit=31 a0=7f0e48014610 a1=241 a2=1b6 a3=238 items=0 ppid=1 pid=1164 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="cimprovagt" exe="/usr/sbin/cimprovagt" subj=system_u:system_r:pegasus_t:s0 key=(null)
type=AVC msg=audit(1353682142.653:2375): avc:  denied  { write } for  pid=1164 comm="cimprovagt" name="flags" dev="sysfs" ino=11313 scontext=system_u:system_r:pegasus_t:s0 tcontext=system_u:object_r:sysfs_t:s0 tclass=file
----
time->Fri Nov 23 15:49:02 2012
type=SYSCALL msg=audit(1353682142.653:2376): arch=c000003e syscall=1 success=yes exit=6 a0=1f a1=7f0e43fff000 a2=6 a3=22 items=0 ppid=1 pid=1164 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="cimprovagt" exe="/usr/sbin/cimprovagt" subj=system_u:system_r:pegasus_t:s0 key=(null)
type=AVC msg=audit(1353682142.653:2376): avc:  denied  { net_admin } for  pid=1164 comm="cimprovagt" capability=12  scontext=system_u:system_r:pegasus_t:s0 tcontext=system_u:system_r:pegasus_t:s0 tclass=capability

The first one looks like selinux forbids the provider to write to /sys/class/net/<interface>/flags.

Comment 5 Miroslav Grepl 2012-11-26 07:44:20 UTC
Fixed in selinux-policy-3.11.1-56.fc18

commit fbd5a98f8c9b2f822c3be3efe6bbc07e7d5c01ca
Author: Miroslav Grepl <mgrepl>
Date:   Mon Nov 26 08:42:02 2012 +0100

    Allow pegasus_t to have net_admin capability
    Allow pegasus_t to write /sys/class/net/<interface>/flags

Comment 6 Fedora Update System 2012-11-28 20:58:30 UTC
selinux-policy-3.11.1-57.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-57.fc18

Comment 7 Fedora Update System 2012-11-30 06:37:03 UTC
Package selinux-policy-3.11.1-57.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-57.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19374/selinux-policy-3.11.1-57.fc18
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2012-12-02 19:31:00 UTC
Package selinux-policy-3.11.1-59.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-59.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19374/selinux-policy-3.11.1-59.fc18
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2012-12-06 20:13:33 UTC
Package selinux-policy-3.11.1-60.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-60.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19374/selinux-policy-3.11.1-60.fc18
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2012-12-07 04:32:10 UTC
selinux-policy-3.11.1-60.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.