Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1711455 [details] SeLinux warning for geclue Description of problem: SeLinux denies connectto access to /run/samba/winbindd/pipe to various processes. Version-Release number of selected component (if applicable): How reproducible: Very. Steps to Reproduce: 1. authselect select winbind 2. add an ntlm_auth based acl and http_access 3. reboot Actual results: Multiple selinux notifications appear - polkitd - ntlm_auth - named - qmgr - sshd - pickup - smtp - pkla_check_auth - (geoclue) Expected results: No selinux notifications should happen Additional info: Reported by setroubleshooter SELinux is preventing (geoclue) from connectto access on the unix_stream_socket /run/samba/winbindd/pipe. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that (geoclue) should be allowed connectto access on the pipe unix_stream_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: # ausearch -c '(geoclue)' --raw | audit2allow -M my-geoclue # semodule -X 300 -i my-geoclue.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:system_r:unconfined_service_t:s0 Target Objects /run/samba/winbindd/pipe [ unix_stream_socket ] Source (geoclue) Source Path (geoclue) Port <Unknown> Host central.nonlinearknowledge.com Source RPM Packages Target RPM Packages
Hi, Unfortunately more information is required to understand. Was there any other significant change made on your system? How the geoclue service was started? # systemctl status geoclue The avc denials: # ausearch -i -m avc,user_avc,selinux_err,user_selinux_err -ts today List of processes: # ps -eo pid,ppid,command,context
Created attachment 1715614 [details] # systemctl status systemctl status polkit
Created attachment 1715615 [details] # ausearch -i -m avc,user_avc,selinux_err,user_selinux_err -ts today # ausearch -i -m avc,user_avc,selinux_err,user_selinux_err -ts today
Created attachment 1715616 [details] # ps -eo pid,ppid,command,context # ps -eo pid,ppid,command,context
Thank you for the commands output: there are multiple processes labeled unconfined_service_t, like: 1812 1729 /usr/sbin/smbd -D --option= system_u:system_r:unconfined_service_t:s0 It indicates this service and related ones were started from command line, not as a systemd service unit. Could you please terminate these processes and start all services using systemd means and check again?
These were not started by hand. These happen even after a system reboot.
semanage fcontext -l Shows entries for smbd and nmbd and the files are correctly labeled # ls -Z /usr/sbin/smbd system_u:object_r:smbd_exec_t:s0 /usr/sbin/smbd But I don't see anything for /usr/sbin/samba
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.