Bug 1727379
Summary: | sysadm_u users cannot log into graphical sessions | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Mason Loring Bliss <mbliss> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | high | Docs Contact: | Jan Fiala <jafiala> |
Priority: | medium | ||
Version: | 7.6 | CC: | jafiala, lagordon, lvrabec, mmalik, plautrba, ssekidde, vmojzis, vpakolu, zpytela |
Target Milestone: | rc | ||
Target Release: | 7.8 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.13.1-253.el7 | Doc Type: | Enhancement |
Doc Text: |
.sysadm_u users can now log in to graphical sessions
Previously, Linux users mapped to the `sysadm_u` SELinux user were unable to log in to graphical sessions. The SELinux policy has been updated to allow these users to use graphical sessions while conforming to DISA STIG requirements. If the `xdm_sysadm_login` Boolean is enabled, the `sysadm_u` user can now successfully log in to X Window System session from the GNOME Display Manager.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-31 19:11:00 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mason Loring Bliss
2019-07-05 18:56:16 UTC
Additional notes: The xdm_exec_bootloader boolean seems to impact the misbehaviour cosmetically. Here is the output from "ausearch -m avc -m user_avc -i -ts today | audit2allow" gathered on my VM: #============= NetworkManager_t ============== allow NetworkManager_t systemd_resolved_t:dbus send_msg; #============= accountsd_t ============== allow accountsd_t sysadm_t:dbus send_msg; #============= boltd_t ============== allow boltd_t sysadm_t:dbus send_msg; #============= colord_t ============== allow colord_t sysadm_t:dbus send_msg; #============= rhsmcertd_t ============== allow rhsmcertd_t sysadm_t:dbus send_msg; #============= rtkit_daemon_t ============== allow rtkit_daemon_t sysadm_t:dbus send_msg; allow rtkit_daemon_t sysadm_t:process setsched; #============= sysadm_gkeyringd_t ============== allow sysadm_gkeyringd_t sysadm_t:unix_stream_socket connectto; allow sysadm_gkeyringd_t system_dbusd_t:dbus send_msg; allow sysadm_gkeyringd_t system_dbusd_t:unix_stream_socket connectto; allow sysadm_gkeyringd_t systemd_logind_t:dbus send_msg; #============= sysadm_t ============== allow sysadm_t accountsd_t:dbus send_msg; allow sysadm_t boltd_t:dbus send_msg; allow sysadm_t colord_t:dbus send_msg; allow sysadm_t rhsmcertd_t:dbus send_msg; allow sysadm_t rtkit_daemon_t:dbus send_msg; allow sysadm_t self:netlink_selinux_socket { bind create }; allow sysadm_t system_dbusd_t:dbus acquire_svc; #============= systemd_logind_t ============== allow systemd_logind_t sysadm_gkeyringd_t:dbus send_msg; Based on the list of suggested rules, I believe that important ones contain system_dbusd_t type and netlink_selinux_socket class. The rest of rules depend on what packages/services are installed/enabled. Here is the local policy module which the problem on my VM: # cat mypolicy.cil ( allow sysadm_t sysadm_t ( dbus ( acquire_svc ))) ( allow sysadm_t sysadm_t ( netlink_selinux_socket ( bind create ))) ( allow sysadm_t system_dbusd_t ( dbus ( acquire_svc ))) ( allow sysadm_gkeyringd_t sysadm_t ( unix_stream_socket ( connectto ))) ( allow sysadm_gkeyringd_t system_dbusd_t ( dbus ( send_msg ))) ( allow sysadm_gkeyringd_t system_dbusd_t ( unix_stream_socket ( connectto ))) ( allow sysadm_gkeyringd_t systemd_logind_t ( dbus ( send_msg ))) ( allow systemd_logind_t sysadm_gkeyringd_t ( dbus ( send_msg ))) ( allow sysadm_gkeyringd_t sysadm_t ( dbus ( acquire_svc ))) # semodule -i mypolicy.cil # Now, I can successfully log into X session as sysadm_u user in enforcing mode. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:1007 |