Bug 912811 - SELinux is preventing /usr/lib/systemd/systemd-hostnamed from 'setopt' accesses on the unix_dgram_socket .
Summary: SELinux is preventing /usr/lib/systemd/systemd-hostnamed from 'setopt' access...
Keywords:
Status: CLOSED DUPLICATE of bug 912616
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:450fe684bec7524effa6bcaf9c0...
: 912812 912814 912815 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-19 18:09 UTC by shrijit.panicker
Modified: 2013-02-20 06:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-20 06:40:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description shrijit.panicker 2013-02-19 18:09:36 UTC
Description of problem:
SELinux is preventing /usr/lib/systemd/systemd-hostnamed from 'setopt' accesses on the unix_dgram_socket .

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that systemd-hostnamed should be allowed setopt access on the  unix_dgram_socket by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep systemd-hostnam /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:systemd_hostnamed_t:s0
Target Context                system_u:system_r:systemd_hostnamed_t:s0
Target Objects                 [ unix_dgram_socket ]
Source                        systemd-hostnam
Source Path                   /usr/lib/systemd/systemd-hostnamed
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           systemd-197-1.fc18.1.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.11.1-78.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 3.7.8-202.fc18.x86_64 #1 SMP Fri
                              Feb 15 17:33:07 UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-02-19 21:29:22 IST
Last Seen                     2013-02-19 21:29:22 IST
Local ID                      a0be108e-ddc3-4ee1-88af-8f6e837ecec6

Raw Audit Messages
type=AVC msg=audit(1361289562.141:400): avc:  denied  { setopt } for  pid=2570 comm="systemd-hostnam" scontext=system_u:system_r:systemd_hostnamed_t:s0 tcontext=system_u:system_r:systemd_hostnamed_t:s0 tclass=unix_dgram_socket


type=SYSCALL msg=audit(1361289562.141:400): arch=x86_64 syscall=setsockopt success=yes exit=0 a0=3 a1=1 a2=7 a3=7fffa2187288 items=0 ppid=1 pid=2570 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=systemd-hostnam exe=/usr/lib/systemd/systemd-hostnamed subj=system_u:system_r:systemd_hostnamed_t:s0 key=(null)

Hash: systemd-hostnam,systemd_hostnamed_t,systemd_hostnamed_t,unix_dgram_socket,setopt

audit2allow

#============= systemd_hostnamed_t ==============
allow systemd_hostnamed_t self:unix_dgram_socket setopt;

audit2allow -R

#============= systemd_hostnamed_t ==============
allow systemd_hostnamed_t self:unix_dgram_socket setopt;


Additional info:
hashmarkername: setroubleshoot
kernel:         3.7.8-202.fc18.x86_64
type:           libreport

Comment 1 Miroslav Grepl 2013-02-20 06:38:41 UTC
*** Bug 912812 has been marked as a duplicate of this bug. ***

Comment 2 Miroslav Grepl 2013-02-20 06:38:58 UTC
*** Bug 912814 has been marked as a duplicate of this bug. ***

Comment 3 Miroslav Grepl 2013-02-20 06:39:06 UTC
*** Bug 912815 has been marked as a duplicate of this bug. ***

Comment 4 Miroslav Grepl 2013-02-20 06:40:00 UTC

*** This bug has been marked as a duplicate of bug 912616 ***


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