GNOME Bugzilla – Bug 796315
make cirrus black list more SELinux friendly
Last modified: 2018-06-20 16:09:49 UTC
It's too hard to ensure custom.conf gets the right security label when it's created by printf from the udev rule. If we do the editing in a separate binary, that binary can transition to the right context and the ensure the label is correct.
Created attachment 372313 [details] [review] utils: add new gdm-disable-wayland binary We currently disable wayland for cirrus by calling printf from a udev rule. This works, but it's a little too open coded to easily write SELinux policy for. This commit introduces a new program, gdm-disable-wayland, that does the same thing, but in a dedicated binary. A future commit will change the udev rule to use the binary.
Created attachment 372314 [details] [review] data: change cirrus blacklist to use gdm-disable-wayland Now that we have a gdm-disable-wayland binary for disabling wayland at boot, we should use it. This commit changes the cirrus udev rule to use gdm-disable-wayland, rather than running sh and printf.
Attachment 372313 [details] pushed as 2dc57da - utils: add new gdm-disable-wayland binary Attachment 372314 [details] pushed as a913eea - data: change cirrus blacklist to use gdm-disable-wayland
*** Bug 796314 has been marked as a duplicate of this bug. ***
*** Bug 796311 has been marked as a duplicate of this bug. ***
This is might also fix https://gitlab.gnome.org/GNOME/gdm/issues/394 in gnome-3-28.