Friendica Social Network

Welcome to Friendica.Eskimo.Com

Home of Censorship Free Hosting

E-mail, Web Hosting, Linux Shell Accounts terminal or full remote desktops.

Sign Up For A Free Trial Here

Please tell your friends about federated social media site that speaks several fediverse protocols thus serving as a hub uniting them, hubzilla.eskimo.com, also check out friendica.eskimo.com, federated macroblogging social media site, mastodon.eskimo.com a federated microblogging site, and yacy.eskimo.com an uncensored federated search engine. All Free!

captainkangaroo via Linux 5 months ago • lemmy

Intel Linux Patch Would Report Outdated CPU Microcode As A Security Vulnerability

A patch posted on Thursday by one of Intel's long-time Linux kernel engineers would begin treating outdated Intel CPU microcode as a security vulnerability that would be reported to user-space via the existing sysfs vulnerabilities reporting.

^{www.phoronix.com}

125 2 1

ouch 5 months ago • lemmy

The Linux kernel would maintain a list of the latest Intel microcode versions for each CPU family, which is based on the data from the Intel microcode GitHub repository. In turn this list would need to be kept updated with new Linux kernel releases and as Intel pushes out new CPU microcode files.

Sounds like that would be outdated for everyone without a rolling distro.

4 3 1

Atemu 5 months ago • lemmy

Stable distros can and will backport security fixes. Good ones that is.

10 1

AndrewZabar 5 months ago • lemmy

Yeah, methinks this will be one of those alerts pretty much everyone will be like "yeah, yeah, I know" and click to silence those notifications.

1 1

trolololol 5 months ago • lemmy

Sounds like a user space application, there's no place for this in the kernel. So would you need to upgrade kennel and reboot to update the list? Nonsense.

This entry was edited (5 months ago)

2 1

ryannathans 5 months ago • lemmy

If that's the case, why wouldn't they put the microcode in the kernel?

Nanook 5 months ago friendica (DFRN)

@DaPorkchop_ Oddly, if you build your own kernel and remove the system provided one, the package gets automatically removed as well which is weird, because it is really still needed regardless.

Nanook 5 months ago friendica (DFRN)

@ryannathans Why bloat the kernel with the microcode for every intel processor that might need it (and there is a similar thing for AMD) when you don't have that specific processor? It does make more sense for it to be a separate, especially on memory constrained systems. I mean if you've got 256GB of RAM probably not a big deal but if you've got 256MB a big deal.

electricprism 5 months ago • lemmy

How about a Linux Patch that reports binary blobs wirh no source AS __ Security Vulnerabilities __

Or are we not allowed to criticize the back doors that hackers gain access to.

13 1 1

mvirts 5 months ago • lemmy

So the patch is just copying the existing warning to a standard location?

1 1

ryannathans 5 months ago • lemmy

The kernel compilation is already configurable between megabytes and gigabyte+

Distros pick their featureset

This entry was edited (5 months ago)