SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
5.7.1 is installed and running perfectly (that's the short version ).
Well, I dug around in my rather tall stack of notes and, near the bottom, found a piece of paper that says it has been 9 years since I last compiled a kernel. Seems like just yesterday.
Did a fresh install from the latest AlienBob -current.iso while I was at it.
Every package I run on a regular basis works as it should. Ditto, all audio and video, including streaming.
Oh, and this is all with the nouveau driver, which surprised me.
Last edited by cwizardone; 06-07-2020 at 07:45 PM.
Perhaps we can expect other 6-year LTS kernels to be selected from time to time, in the future :-)
This makes all LTS kernels from 4.4 to the current 5.4 to have 6 years of support. I wonder if they're just going to announce 6 year support from the start or still wait several months to a year until announcing extended support?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
"Google Engineer Uncovers Holes In Linux's Speculative Execution Mitigations"
Written by Michael Larabel on 9 June 2020 at 07:04 AM EDT.
Quote:
There are some urgent fixes pending for the x86/x86_64 speculative execution handling for the Linux kernel following a Google security engineer discovering these issues, including one of the fixes address a situation that unfairly impacted AMD CPUs.
Queued up this morning in x86/urgent are a number of fixes to the Linux kernel's speculative execution mitigations........
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Year 2020, Round 37
Another batch of kernel updates has been scheduled for release on Thursday, 11 June 2020, at approximately 18:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Wednesday (depending on your time zone).
There will be 24 patches in the 5.7.2 update, 41 in 5.6.18, 34 in 5.4.46, 25 in 4.19.128, 46 in 4.14.184, 42 in 4.9.227 and, finally, 36 patches in the 4.4.227 update.
Linux 3.16.85
From: Ben Hutchings
Date: Thu Jun 11 2020 - 14:35:24 EST
I'm announcing the release of the 3.16.85 kernel. This is probably
the last release in the 3.16 stable series, unless some critical fix
comes up later this month.
All users of the 3.16 kernel series should upgrade.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Here we go again.
Quote:
Another Attack Vector Uncovered For Bypassing Linux Lockdown Via ACPI Tables
Written by Michael Larabel in Linux Security on 15 June 2020 at 07:06 AM EDT.
--
This weekend we reported on how injecting ACPI tables could lead to bypassing Linux's lockdown / UEFI Secure Boot protections and let attackers load unsigned kernel modules. That earlier issue was found on a patched version of the Ubuntu 18.04 LTS kernel while now a similar attack vector has been discovered on the mainline Linux kernel..............
I applied the patch in the article's linked page to my current kernel, 5.4.46, and it is running just fine. Just thought I'd put that out there for anyone thinking of closing this particular security hole right now
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.