SElinux blocking issues list F41

here is list of F41 beta where SElinux rules are blocking…

SELinux is preventing abrt-dump-journ from connectto access on the unix_stream_socket /run/systemd/userdb/io.systemd.Home.

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

If you believe that abrt-dump-journ should be allowed connectto access on the io.systemd.Home 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 'abrt-dump-journ' --raw | audit2allow -M my-abrtdumpjourn
# semodule -X 300 -i my-abrtdumpjourn.pp

Additional Information:
Source Context                system_u:system_r:abrt_dump_oops_t:s0
Target Context                system_u:system_r:systemd_homed_t:s0
Target Objects                /run/systemd/userdb/io.systemd.Home [
                              unix_stream_socket ]
Source                        abrt-dump-journ
Source Path                   abrt-dump-journ
Port                          <Unknown>
Host                          fedora
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.20-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.20-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     fedora
Platform                      Linux fedora 6.11.2-300.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri Oct  4 16:44:08 UTC 2024
                              x86_64
Alert Count                   44
First Seen                    2024-10-09 18:37:42 +07
Last Seen                     2024-10-10 10:43:26 +07
Local ID                      a979e7ff-d206-4248-bf15-831d92e62330

Raw Audit Messages
type=AVC msg=audit(1728531806.622:878): avc:  denied  { connectto } for  pid=1683 comm="abrt-dump-journ" path="/run/systemd/userdb/io.systemd.Home" scontext=system_u:system_r:abrt_dump_oops_t:s0 tcontext=system_u:system_r:systemd_homed_t:s0 tclass=unix_stream_socket permissive=0


Hash: abrt-dump-journ,abrt_dump_oops_t,systemd_homed_t,unix_stream_socket,connectto
SELinux is preventing systemd-homed from read access on the directory home.

*****  Plugin catchall_labels (83.8 confidence) suggests   *******************

If you want to allow systemd-homed to have read access on the home directory
Then you need to change the label on home
Do
# semanage fcontext -a -t FILE_TYPE 'home'
where FILE_TYPE is one of the following: NetworkManager_etc_rw_t, NetworkManager_etc_t, abrt_etc_t, admin_home_t, aiccu_etc_t, alsa_etc_rw_t, alsa_home_t, antivirus_conf_t, antivirus_home_t, asterisk_etc_t, audio_home_t, auth_home_t, avahi_conf_t, bin_t, bitlbee_conf_t, bluetooth_conf_t, boot_t, boothd_etc_t, bootloader_etc_t, cache_home_t, cert_t, cgconfig_etc_t, cgrules_etc_t, chrome_sandbox_home_t, cluster_conf_t, cobbler_etc_t, condor_conf_t, config_home_t, conntrackd_conf_t, container_config_t, container_file_t, container_home_t, container_ro_file_t, container_runtime_tmpfs_t, couchdb_conf_t, courier_etc_t, cpucontrol_conf_t, cupsd_etc_t, cupsd_rw_etc_t, cvs_home_t, data_home_t, dbus_home_t, dbusd_etc_t, ddclient_etc_t, device_t, devpts_t, dhcp_etc_t, dictd_etc_t, dnsmasq_etc_t, dovecot_cert_t, dovecot_etc_t, etc_mail_t, etc_runtime_t, etc_t, exports_t, fdo_conf_rw_t, fdo_conf_t, fdo_home_t, fetchmail_etc_t, fetchmail_home_t, file_context_t, fingerd_etc_t, firewalld_etc_rw_t, firstboot_etc_t, fonts_cache_t, fonts_t, ftpd_etc_t, fwupd_cert_t, gconf_etc_t, gconf_home_t, gdomap_conf_t, getty_etc_t, git_user_content_t, gkeyringd_gnome_home_t, gnome_home_t, gpg_secret_t, gpm_conf_t, gstreamer_home_t, hddtemp_etc_t, home_bin_t, home_cert_t, home_root_t, hostname_etc_t, httpd_config_t, httpd_user_content_t, httpd_user_script_exec_t, ibacm_conf_t, icc_data_home_t, iceauth_home_t, init_var_lib_t, init_var_run_t, innd_etc_t, insights_client_etc_rw_t, insights_client_etc_t, irc_conf_t, irc_home_t, irc_tmp_t, irssi_etc_t, irssi_home_t, kdump_etc_t, kismet_home_t, krb5_conf_t, krb5_home_t, krb5_host_rcache_t, krb5kdc_conf_t, kubernetes_file_t, l2tp_conf_t, lib_t, likewise_etc_t, lircd_etc_t, local_login_home_t, locale_t, lvm_etc_t, machineid_t, mail_home_rw_t, mail_home_t, mail_spool_t, man_cache_t, man_t, mandb_home_t, mcelog_etc_t, mdadm_conf_t, mdevctl_conf_t, minidlna_conf_t, minissdpd_conf_t, mock_etc_t, modules_conf_t, mozilla_conf_t, mozilla_home_t, mozilla_plugin_rw_t, mpd_etc_t, mpd_home_t, mpd_user_data_t, mplayer_etc_t, mplayer_home_t, mptcpd_etc_t, mrtg_etc_t, mscan_etc_t, munin_etc_t, mysqld_etc_t, mysqld_home_t, nagios_etc_t, named_conf_t, net_conf_t, nrpe_etc_t, nscd_var_run_t, nslcd_conf_t, ntop_etc_t, ntp_conf_t, nut_conf_t, opendnssec_conf_t, openshift_var_lib_t, openvpn_etc_rw_t, openvpn_etc_t, openvswitch_rw_t, oracleasm_conf_t, pads_config_t, passt_etc_t, pdns_conf_t, pegasus_conf_t, pingd_etc_t, pkcs11_modules_conf_t, pki_tomcat_cert_t, polipo_cache_home_t, polipo_config_home_t, polipo_etc_t, portreserve_etc_t, postfix_etc_t, postgresql_etc_t, postgrey_etc_t, pppd_etc_t, prelude_correlator_config_t, printconf_t, proc_t, procmail_home_t, psad_etc_t, ptal_etc_t, pulseaudio_home_t, puppet_etc_t, qatlib_conf_t, qmail_etc_t, rabbitmq_conf_t, radiusd_etc_t, radvd_etc_t, redis_conf_t, rhnsd_conf_t, rhsmcertd_config_t, rlogind_home_t, root_t, rssh_ro_t, rssh_rw_t, rsync_etc_t, samba_cert_t, samba_etc_t, sandbox_file_t, sanlock_conf_t, screen_home_t, shell_exec_t, shorewall_etc_t, slapd_cert_t, slapd_etc_t, snapperd_conf_t, snort_etc_t, soundd_etc_t, spamc_home_t, spamd_etc_t, speech_dispatcher_home_t, squid_conf_t, src_t, ssh_home_t, sslh_config_t, sssd_conf_t, sssd_public_t, stunnel_etc_t, svc_conf_t, svirt_home_t, sysfs_t, syslog_conf_t, system_conf_t, system_db_t, systemd_conf_t, systemd_home_t, systemd_homed_crypto_luks_t, systemd_homed_library_dir_t, systemd_homed_runtime_dir_t, systemd_hwdb_etc_t, systemd_userdbd_runtime_t, targetclid_home_t, telepathy_cache_home_t, telepathy_data_home_t, telepathy_gabble_cache_home_t, telepathy_logger_cache_home_t, telepathy_logger_data_home_t, telepathy_mission_control_cache_home_t, telepathy_mission_control_data_home_t, telepathy_mission_control_home_t, telepathy_sunshine_home_t, texlive_home_t, textrel_shlib_t, tftpd_etc_t, thumb_home_t, tmp_t, tmpfs_t, tor_etc_t, tuned_etc_t, tuned_rw_etc_t, tvtime_home_t, udev_etc_t, udev_var_run_t, ulogd_etc_t, uml_ro_t, uml_rw_t, unlabeled_t, user_fonts_cache_t, user_fonts_config_t, user_fonts_t, user_home_dir_t, user_home_t, user_tmp_t, userhelper_conf_t, usr_t, var_lib_t, var_run_t, varnishd_etc_t, virt_content_t, virt_etc_t, virt_home_t, virt_var_lib_t, virtlogd_etc_t, vmware_conf_t, vmware_file_t, vmware_sys_conf_t, webalizer_etc_t, wine_home_t, wireshark_home_t, xauth_home_t, xdm_etc_t, xdm_home_t, xdm_rw_etc_t, xserver_etc_t, ypserv_conf_t, zarafa_etc_t, zebra_conf_t.
Then execute:
restorecon -v 'home'


*****  Plugin catchall (17.1 confidence) suggests   **************************

If you believe that systemd-homed should be allowed read access on the home directory 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 'systemd-homed' --raw | audit2allow -M my-systemdhomed
# semodule -X 300 -i my-systemdhomed.pp

Additional Information:
Source Context                system_u:system_r:systemd_homed_t:s0
Target Context                system_u:object_r:var_t:s0
Target Objects                home [ dir ]
Source                        systemd-homed
Source Path                   systemd-homed
Port                          <Unknown>
Host                          fedora
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.20-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.20-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     fedora
Platform                      Linux fedora 6.11.2-300.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri Oct  4 16:44:08 UTC 2024
                              x86_64
Alert Count                   9
First Seen                    2024-10-09 18:07:34 +07
Last Seen                     2024-10-10 10:46:04 +07
Local ID                      8b2c8b42-b9db-4b15-913d-7097e8bf2bde

Raw Audit Messages
type=AVC msg=audit(1728531964.180:105): avc:  denied  { read } for  pid=1575 comm="systemd-homed" name="home" dev="dm-0" ino=782987 scontext=system_u:system_r:systemd_homed_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir permissive=0


Hash: systemd-homed,systemd_homed_t,var_t,dir,read
SELinux is preventing iio-sensor-prox from create access on the unix_dgram_socket labeled iiosensorproxy_t.

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

If you believe that iio-sensor-prox should be allowed create access on unix_dgram_socket labeled iiosensorproxy_t 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 'iio-sensor-prox' --raw | audit2allow -M my-iiosensorprox
# semodule -X 300 -i my-iiosensorprox.pp

Additional Information:
Source Context                system_u:system_r:iiosensorproxy_t:s0
Target Context                system_u:system_r:iiosensorproxy_t:s0
Target Objects                Unknown [ unix_dgram_socket ]
Source                        iio-sensor-prox
Source Path                   iio-sensor-prox
Port                          <Unknown>
Host                          fedora
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.20-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.20-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     fedora
Platform                      Linux fedora 6.11.2-300.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri Oct  4 16:44:08 UTC 2024
                              x86_64
Alert Count                   135
First Seen                    2024-10-09 18:07:34 +07
Last Seen                     2024-10-10 10:46:04 +07
Local ID                      8f105b30-80db-4b31-a2d5-8c1a7e1833c2

Raw Audit Messages
type=AVC msg=audit(1728531964.258:145): avc:  denied  { create } for  pid=1553 comm="iio-sensor-prox" scontext=system_u:system_r:iiosensorproxy_t:s0 tcontext=system_u:system_r:iiosensorproxy_t:s0 tclass=unix_dgram_socket permissive=0


Hash: iio-sensor-prox,iiosensorproxy_t,iiosensorproxy_t,unix_dgram_socket,create
SELinux is preventing iio-sensor-prox from write access on the file current_trigger.

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

If you believe that iio-sensor-prox should be allowed write access on the current_trigger file 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 'iio-sensor-prox' --raw | audit2allow -M my-iiosensorprox
# semodule -X 300 -i my-iiosensorprox.pp

Additional Information:
Source Context                system_u:system_r:iiosensorproxy_t:s0
Target Context                system_u:object_r:sysfs_t:s0
Target Objects                current_trigger [ file ]
Source                        iio-sensor-prox
Source Path                   iio-sensor-prox
Port                          <Unknown>
Host                          fedora
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.20-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.20-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     fedora
Platform                      Linux fedora 6.11.2-300.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri Oct  4 16:44:08 UTC 2024
                              x86_64
Alert Count                   72
First Seen                    2024-10-09 18:07:34 +07
Last Seen                     2024-10-10 10:46:04 +07
Local ID                      e6497453-41c9-4f15-9f8e-7aac32e3ca21

Raw Audit Messages
type=AVC msg=audit(1728531964.258:147): avc:  denied  { write } for  pid=1553 comm="iio-sensor-prox" name="current_trigger" dev="sysfs" ino=61945 scontext=system_u:system_r:iiosensorproxy_t:s0 tcontext=system_u:object_r:sysfs_t:s0 tclass=file permissive=0


Hash: iio-sensor-prox,iiosensorproxy_t,sysfs_t,file,write
SELinux is preventing iio-sensor-prox from write access on the directory trigger.

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

If you believe that iio-sensor-prox should be allowed write access on the trigger directory 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 'iio-sensor-prox' --raw | audit2allow -M my-iiosensorprox
# semodule -X 300 -i my-iiosensorprox.pp

Additional Information:
Source Context                system_u:system_r:iiosensorproxy_t:s0
Target Context                system_u:object_r:sysfs_t:s0
Target Objects                trigger [ dir ]
Source                        iio-sensor-prox
Source Path                   iio-sensor-prox
Port                          <Unknown>
Host                          fedora
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.20-1.fc41.noarch
Local Policy RPM              selinux-policy-targeted-41.20-1.fc41.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     fedora
Platform                      Linux fedora 6.11.2-300.fc41.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri Oct  4 16:44:08 UTC 2024
                              x86_64
Alert Count                   18
First Seen                    2024-10-09 18:07:34 +07
Last Seen                     2024-10-10 10:46:04 +07
Local ID                      2956b2a4-e8be-45fb-8957-742082d7d5f7

Raw Audit Messages
type=AVC msg=audit(1728531964.258:146): avc:  denied  { write } for  pid=1553 comm="iio-sensor-prox" name="trigger" dev="sysfs" ino=61944 scontext=system_u:system_r:iiosensorproxy_t:s0 tcontext=system_u:object_r:sysfs_t:s0 tclass=dir permissive=0


Hash: iio-sensor-prox,iiosensorproxy_t,sysfs_t,dir,write

Hi, please install the setroubleshoot package, if you don’t have it already, and use the dialog which will pop up on any new SELinux violation to report a new bug into RH Bugzilla. The SELinux developer will then look at it. Thanks!

I had it, but cant report sll as a bug grayed out so i posted here all from that app with all details it gave me

I will report all what i can as bug report

Just in case some file is mis-labeled, do sudo touch /.autorelabel and reboot.

1 Like

You first need to click on something like “If you believe this is a bug…” and then you can report the bug. Share a screenshot of the window, if you can’t figure it out.

I have setroubleshoot installed but the SELinux dialog doesn’t give me any reporting options besides “Notify Admin” which just generates an email. Screenshot:

If you select the troubleshoot button, there is a report bug button on that screen.