Bug 1049644 - SELinux is preventing /usr/sbin/dhclient from 'name_bind' accesses on the udp_socket .
Summary: SELinux is preventing /usr/sbin/dhclient from 'name_bind' accesses on the udp...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 19
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:97034a896516a71caa7a9494692...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-07 22:59 UTC by Richard Z.
Modified: 2014-01-13 13:45 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-13 13:45:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard Z. 2014-01-07 22:59:58 UTC
Description of problem:
I did try to create a WIFI access point with KDE version of NM gui. Did not modify any dhcp related options in the GUI, all I did was to set SSID and security/password. I did try to set firwall policy to home.

Another alert came saying that I need 
 setsebool -P nis_enabled 1
SELinux is preventing /usr/sbin/dhclient from 'name_bind' accesses on the udp_socket .

*****  Plugin catchall_boolean (89.3 confidence) suggests  *******************

If you want to allow system to run with NIS
Then you must tell SELinux about this by enabling the 'nis_enabled' boolean.
You can read 'None' man page for more details.
Do
setsebool -P nis_enabled 1

*****  Plugin catchall (11.6 confidence) suggests  ***************************

If you believe that dhclient should be allowed name_bind access on the  udp_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 dhclient /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:dhcpc_t:s0
Target Context                system_u:object_r:ephemeral_port_t:s0
Target Objects                 [ udp_socket ]
Source                        dhclient
Source Path                   /usr/sbin/dhclient
Port                          46321
Host                          (removed)
Source RPM Packages           dhclient-4.2.5-23.fc19.i686
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-74.16.fc19.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.12.6-200.fc19.i686.PAE #1 SMP
                              Mon Dec 23 16:58:40 UTC 2013 i686 i686
Alert Count                   3
First Seen                    2014-01-07 23:45:14 CET
Last Seen                     2014-01-07 23:47:07 CET
Local ID                      704288d5-c76c-44f8-9339-c5f357433657

Raw Audit Messages
type=AVC msg=audit(1389134827.979:6066): avc:  denied  { name_bind } for  pid=11947 comm="dhclient" src=46321 scontext=system_u:system_r:dhcpc_t:s0 tcontext=system_u:object_r:ephemeral_port_t:s0 tclass=udp_socket


type=SYSCALL msg=audit(1389134827.979:6066): arch=i386 syscall=socketcall success=no exit=EACCES a0=2 a1=bfa384e0 a2=b7591000 a3=b69a2008 items=0 ppid=1021 pid=11947 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=dhclient exe=/usr/sbin/dhclient subj=system_u:system_r:dhcpc_t:s0 key=(null)

Hash: dhclient,dhcpc_t,ephemeral_port_t,udp_socket,name_bind

Additional info:
reporter:       libreport-2.1.10
hashmarkername: setroubleshoot
kernel:         3.12.6-200.fc19.i686.PAE
type:           libreport

Comment 1 Daniel Walsh 2014-01-08 15:37:48 UTC
Did everything work without turning on this boolean?

Comment 2 Richard Z. 2014-01-08 22:20:20 UTC
unfortunately, it does not work very well at all yet and I did not have the time to fully investigate all aspects.

* "internet" is mobile broadband (LTE), the MIFI combination is perhaps less tested
* firewall was too restrictive so it may have provoked dhclient to do some unusual workarounds

Comment 3 Richard Z. 2014-01-10 11:41:43 UTC
I have disabled nis_enabled again and everything still seems to work


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