Introduced release of the distribution kit Fedora Linux 45. For download prepared products Fedora Workstation, Fedora KDE Plasma Desktop, Fedora Server, Fedora IoT, Fedora CoreOS, Fedora Cloud Base, Fedora IoT Edition, Fedora Silverblue, Fedora Kinoite and Live builds delivered in the form of spins with custom Xfce environments, MATE, Cinnamon, LXDE, Phosh, Miracle, LXQt, Budgie, Sway and Cosmic. Builds are generated for x86_64, Power64 and ARM64 (AArch64) architectures.
The most significant changes in Fedora Linux 45:
- The GNOME desktop environment has been updated to branch 51, which offers optimizations for improving the smoothness of output and eliminating stuttering during animation and under heavy system load. There is an option to automatically change landscape and portrait screen orientations when you rotate a device with an accelerometer.
Added the ability to forward smart cards when connecting to a desktop remotely. Added support for authentication through corporate web services to the login screen. Vector images of cursors supplied in SVG format are used. - In the installation iso images of atomically updated editions of Fedora Atomic Desktop (Silverblue, Kinoite, etc.), instead of the classic GTK-based Anaconda installer, the new Anaconda WebUI installer based on the web interface, already used in Fedora Workstation and in live builds. The new installer supports remote installation management – users can now boot Fedora on the target system with the “inst.webui.remote” option and manage the installation through a web browser on another computer with PIN authentication and traffic encryption.
- All RPM repository configuration files that are initially installed when connecting a repository are movedfrom /etc/yum.repos.d to /usr/share/dnf5/repos.d. PGP keys have been moved to /usr/share/pki/rpm-gpg. The change will make it easier to separate initial repository settings from user-modified configuration files.
- In RPM, by default is enabled to check packages using digital signatures. When trying to install packages without a signature or with an incorrect signature, an error will now be displayed unless the user explicitly started the rpm with the “–nosignature” flag. Previously, only hash integrity checks were performed at the RPM level, and the authenticity of packages from repositories was checked in YUM and DNF.
/Reports, release notes, official announcements.