Fedora 34 intends to remove SELinux on-the-fly disabling and switch to shipping KDE with Wayland

Scheduled for implementation in Fedora 34 change, removing the ability to disable SELinux while running. The ability to switch between "enforcing" and "permissive" modes during the boot process will be preserved. After SELinux is initialized, LSM handlers will be set to read-only mode, which can improve protection against attacks that disable SELinux after exploiting vulnerabilities that allow changing the contents of kernel memory.

To disable SELinux, you will need to reboot the system, passing the "selinux=0" parameter on the kernel command line. Disabling via changing /etc/selinux/config (SELINUX=disabled) will not be supported. Formerly in the Linux kernel 5.6 SELinux module unloading support has been deprecated.

Also, in Fedora 34 proposed by change default builds with KDE desktop to use Wayland by default. The X11-based session is planned to be upgraded to an option.
Running KDE on top of Wayland is currently experimental, but in KDE Plasma 5.20 this mode of operation is going to be brought to parity in functionality with the mode of running on top of X11. Including in the KDE 5.20 session based on Wayland, problems with screencasting and middle-mouse paste will be resolved. To work when using NVIDIA proprietary drivers, the kwin-wayland-nvidia package will be used. Compatibility with X11 applications will be provided using the XWayland component.

As an argument against X11 based session default persistence is mentioned stagnation X11 server, which has practically ceased development in recent years and only fixes of dangerous errors and vulnerabilities are made to the code. Moving the default build to Wayland will be an incentive for increased development activity related to support for new graphics technologies in KDE, as the move to Wayland of the GNOME session in Fedora 25 once affected development.

Source: opennet.ru

Add a comment