Linux Action News 277

An Ubuntu expiration date approaches, openSUSE has a new handy solution, and the container security issue that remains unfixed.

An Ubuntu expiration date approaches, openSUSE has a new handy solution, and the container security issue that remains unfixed.

Sponsored By:

Kolide: Kolide can help you nail third-party audits and internal compliance goals with endpoint security for your entire fleet. Linode: Sign up using the link on this page and receive a $100 60-day credit towards your new account.

Support Linux Action News

Links:

Ubuntu 18.04 LTS End Of Life — Ubuntu 18.04 ‘Bionic Beaver’ is reaching End of Standard Support this April, also known sometimes as End Of Life (EOL).Ubuntu 22.04.2 Point Release Delayed by 2 Weeks — Ubuntu 22.04.2 LTS was due for release on Thursday, February 9. However, the release has had to be delayed by two weeks, and is now scheduled to arrive on Thursday, February 23.Ubuntu ProUbuntu Extended Security MaintenanceWine 8.0 is out now with major compatibility improvements — One of the major changes here is the conversion to the PE format for various modules. This format is used by Windows, and an important milestone for Wine to increase compatibility with copy protection, 32-bit applications on 64-bit hosts, Windows debuggers and more.openSUSE Making It Easier To Install H.264 Codec Support — Inspired by the Fedora / Red Hat and Cisco collaboration around OpenH264 support, openSUSE/SUSE set out for a similar arrangement with Cicsco and its OpenH264 codecs.
Linux 6.2-rc5 Released — Due to an uptick in activity this week and the downtime around Christmas / end-of-year holidays, Torvalds is planning on this cycle spanning through Linux 6.2-rc8 before going gold.Linux 6.3 To Remove Obsolete GPU Drivers: ATI Rage 128, 3Dfx, S3 Savage, i810 & More — Hitting the chopping block with the Linux 6.3 kernel are the following DRM drivers: i810, mga, r128, savage, sis, tdfx, and via.Kernel Security Korner — The issue involved in that compromise became known as CVE-2019-5736 and a complex workaround was implemented in runC to prevent similar vulnerabilities in the future.