This is the best summary I could come up with:
Guardrails have been in place where the Firefox browser has enabled Wayland by default (when running on recent GTK versions) but as of today that code has been removed… Firefox will try to move forward with stable releases where Wayland will ship by default!
Mozilla Bug 1752398 to “ship the Wayland backend to release” has been closed this evening!
After the ticket was open for the past two years, it’s now deemed ready to hopefully ship enabled for Firefox 121!
This patch drops the “early beta or earlier” check to let Wayland support be enabled by default when running on recent GTK versions (GTK 3.24.30 threshold).
Firefox 121 is due for release around 19 December and if all continues to hold, it will finally ship with the Wayland back-end enabled by default as another big step forward.
With KDE Plasma 6.0 using Wayland by default, XWayland rootful mode improving, and other (X)Wayland progress, 2024 could very well be the year of Wayland shining in the Linux desktop limelight.
The original article contains 168 words, the summary contains 168 words. Saved 0%. I’m a bot and I’m open source!
This is the best summary I could come up with:
Hundreds of Windows and Linux computer models from virtually all hardware makers are vulnerable to a new attack that executes malicious firmware early in the boot-up sequence, a feat that allows infections that are nearly impossible to detect or remove using current defense mechanisms.
The attack—dubbed LogoFAIL by the researchers who devised it—is notable for the relative ease in carrying it out, the breadth of both consumer- and enterprise-grade models that are susceptible, and the high level of control it gains over them.
LogoFAIL is a constellation of two dozen newly discovered vulnerabilities that have lurked for years, if not decades, in Unified Extensible Firmware Interfaces responsible for booting modern devices that run Windows or Linux.
The participating companies comprise nearly the entirety of the x64 and ARM CPU ecosystem, starting with UEFI suppliers AMI, Insyde, and Phoenix (sometimes still called IBVs or independent BIOS vendors); device manufacturers such as Lenovo, Dell, and HP; and the makers of the CPUs that go inside the devices, usually Intel, AMD or designers of ARM CPUs.
As its name suggests, LogoFAIL involves logos, specifically those of the hardware seller that are displayed on the device screen early in the boot process, while the UEFI is still running.
LogoFAIL is a newly discovered set of high-impact security vulnerabilities affecting different image parsing libraries used in the system firmware by various vendors during the device boot process.
The original article contains 663 words, the summary contains 232 words. Saved 65%. I’m a bot and I’m open source!