Hide Forgot
I've been running as staff_t/sysadm_t. This is my list of denials. Please include as many as you think appropriate. I can supply more log messages for any you request. Some we likely just don't want, and that is ok. #============= colord_t ============== allow colord_t systemd_hwdb_etc_t:file { getattr open read }; #============= init_t ============== allow init_t systemd_logind_var_run_t:file { create rename setattr write }; #============= staff_dbusd_t ============== allow staff_dbusd_t staff_t:unix_stream_socket { accept getattr getopt }; #============= staff_gkeyringd_t ============== allow staff_gkeyringd_t staff_t:unix_stream_socket connectto; allow staff_gkeyringd_t user_tmp_t:sock_file write; #============= staff_sudo_t ============== allow staff_sudo_t init_t:process getpgid; #============= staff_t ============== allow staff_t cgroup_t:dir { add_name create remove_name rmdir write }; allow staff_t fwupd_cache_t:file { open read }; allow staff_t gpg_agent_t:process signull; allow staff_t init_t:process signal; allow staff_t init_t:unix_stream_socket ioctl; allow staff_t mount_t:process { signal signull }; #!!!! This avc can be allowed using the boolean 'selinuxuser_use_ssh_chroot' allow staff_t self:capability setuid; allow staff_t self:capability { sys_admin sys_ptrace }; allow staff_t sshd_key_t:file open; allow staff_t sysfs_t:file write; #!!!! This avc can be allowed using the boolean 'xserver_clients_write_xshm' allow staff_t xserver_tmpfs_t:file write; #============= systemd_logind_t ============== allow systemd_logind_t tmpfs_t:file getattr; #============= telepathy_logger_t ============== allow telepathy_logger_t staff_t:process sigchld; allow telepathy_logger_t staff_t:unix_stream_socket connectto; allow telepathy_logger_t user_tmp_t:sock_file write; allow telepathy_mission_control_t staff_t:process sigchld; allow telepathy_mission_control_t staff_t:unix_stream_socket connectto; allow telepathy_mission_control_t user_tmp_t:sock_file write;
Could you attach also raw avc msgs? Thank you.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.