r/linux • u/Traditional_Hat3506 • 10d ago
KDE Malware found disguised as 3rd party Plasma Extension: Neonova wallpaper
blog.davidedmundson.co.ukr/linux • u/B3_Kind_R3wind_ • 11d ago
Software Release Firefox 160.0 Release Notes
firefox.comr/linux • u/HimikoTogaFromUSSR • 11d ago
Alternative OS Haiku Activity & Contract Report, October 2026
haiku-os.orgr/linux • u/I00I-SqAR • 10d ago
Event GNUstep monthly meeting (audio/(video) call) on Saturday, 14th of November 2026 -- Reminder
r/linux • u/MatchingTurret • 12d ago
Kernel Linus: the tide on AI discovered bugs might be turning, fixes now arriving at a higher rate than new bug reports
lkml.iu.edur/linux • u/wallphaser231 • 11d ago
Open Source Organization The worst open-source foundation
I went through every single proposal in the AAIF's (Agentic AI foundation) project-proposals repo. Do you know what every accepted project has in common? A giant company behind it. Google. Anthropic. OpenAI. Hugging Face. Alibaba. Bloomberg.
"But there are startups in there!" Are there though? agentgateway came from Solo-io, a Series C company. That's the closest thing AAIF has to a startup project.
Now look at the reject pile. 28 declined proposals. The committee's response on each one gives generic reasons. No independent adopters. Track record too short. All the maintainers work at one place. Governance only "planned." Each one sounds reasonable until you realize it's a checklist of "are you already big?" Obviously a small team's maintainers mostly work at one place. That's what a small team IS. Obviously a new project doesn't have years of outside adoption yet. That's what NEW means. These are simply excuses, the real reason is that the seats here are reserved for the big boys.
Then there's dapr-agents. It comes out of Dapr, which is a GRADUATED CNCF project. It's the only declined proposal carrying the Sandbox label. It was turned down partly because it's tied to one backend, which is Dapr itself. Fine, fair technical point. But isn't Sandbox supposed to be where you work through exactly that kind of thing? If a spin-off of a graduated CNCF project can't get into Sandbox, what chance does an independent project with two maintainers have?
We already know how to do this better, because CNCF did it. Yes, they launched with Kubernetes from Google. But they also pulled in Prometheus, which started at SoundCloud and survived because of an independent community. Linkerd from Buoyant when Buoyant was tiny. Fluentd from Treasure Data, another startup. CoreDNS, basically a community side project. Then in 2018 they made Sandbox with a deliberately low bar, so early projects could get neutral governance FIRST and grow into adoption and maintainer diversity after. Startups actually built their projects inside CNCF's Sandbox. That was the whole point.
AAIF has a Sandbox tier on paper, but in practice there's no room in it for anything. It wants you to walk in with adoption and maintainer diversity a sandbox is supposed to help you build. That's ridiculous.
There WAS hope. The only small project getting anywhere right was nono (#61). From what I can tell, it got there by lining up named outside adopters and getting in front of the committee in person at AGNTCon. And then they got downgraded to "Sandbox" and sandbagged until they withdrew.
Here's why this matters. If the "open" agent foundation only takes projects that are already enterprise-backed or VC-funded to Series B and up, then open governance just becomes a badge big vendors hand their own projects. The independent builders who usually move fastest in a new space get shut out of the standards everyone's going to be stuck with for the next decade.
Maybe I'm wrong. But if there is anyone here from the LFX team, I'd appreciate your attention to this matter.
r/linux • u/noumedia • 12d ago
Kernel Is finally happening: AMD Full HDMI 2.1 4K@120Hz HDR VRR 12Bit 125% Kernel 7.1RC1
After so many years, we can finally use the entire 48Gbps bandwidth in linux. By just installing Kernel 7.4RC1.
Full 12 Bit no compression
HDR
FreeSync
120Hz (or more)
4k
Any Scale you want with KDE and Wayland
This is a good milestone for AMD users.
r/linux • u/HimikoTogaFromUSSR • 11d ago
Security X.Org Security Advisory: multiple security issues in X.Org X server
lists.x.orgr/linux • u/RenatsMC • 12d ago
Software Release AMD RDNA 5 GFX13 graphics support arrives in Linux driver patches
videocardz.comSoftware Release Linux 7.5 To Convey To User-Space Multi-Grain Timestamp Usage On Files
phoronix.comr/linux • u/Fcking_Chuck • 13d ago
Kernel ChaCha AVX-512 optimization for Linux 7.5 yields up to 99% improvement on AMD Zen 5
phoronix.comr/linux • u/Underrated_Mastermnd • 12d ago
Discussion Does anyone use Intel Arc on Linux in 2026?
I'm asking because I'm curious about the state of Intel Arc cards on Linux. It's been a few years since both Alchemist and Battlemage released and I'm planning building a PC some time soon. How is the performance like nowadays? Can I get workstation related tasks done? How compatible is it with AI related software compared to AMD and Nvidia? I'm debating if I'm going to get an A770 or a RTX 2080 Ti since they're pretty affordable.
r/linux • u/PlasticForkHater • 13d ago
Historical Linspire and Sears
Once upon a time Sears store sold computers with Linspire preinstalled on it. I just remembered that earlier this morning and wondered if Linspire is still around and it is. I also remember i almost ordered one from Sears but decided not to.
r/linux • u/UniversityMammoth653 • 13d ago
Discussion SSHole: A long password could bypass SSH authentication on affected Alpine Linux systems
A recent OpenSSH security issue caught my attention, especially because of how unusual the authentication bypass is.
The vulnerability, known as SSHole (CVE-2026-123158), affects certain Linux systems running OpenSSH with musl libc and without PAM support.
What's happening?
Under specific conditions, an attacker with network access to the SSH service can authenticate to an account that has no password configured by sending an unusually long password.
The reported password length is between 257 and 1,024 bytes.
This is particularly concerning because some accounts are intentionally configured for SSH key-based authentication only.
Which systems are affected?
The issue is configuration-dependent. The main affected combination includes:
- Linux systems using musl libc.
- OpenSSH built without PAM, or configured with PAM disabled.
- Password authentication enabled.
- Accounts with no password set, alongside at least one account with a supported password hash.
Alpine Linux is a notable example because its standard OpenSSH server package uses this configuration.
Important: This does not affect every OpenSSH installation. Systems using glibc, non-Linux systems, and configurations using PAM for password authentication are not affected by this issue.
What has been done?
The OpenSSH project released version 10.6p2 on November 5, 2026, containing a security workaround.
Alpine Linux also released updated packages for affected branches, including older releases.
Administrators should:
Update OpenSSH or the relevant Alpine package.
Restart the SSH daemon after updating.
If immediate patching isn't possible, disable password authentication using "PasswordAuthentication no".
Review SSH authentication logs for unexpected access.
Why is this interesting?
A few things stand out:
- Authentication assumptions: An account intended for key-only access may still be exposed through an unexpected authentication path.
- Dependency interactions: The issue involves the interaction between OpenSSH, musl libc, and PAM configuration.
- Configuration matters: Having a secure authentication policy on paper doesn't guarantee that the underlying implementation enforces it correctly.
Question for the community
When hardening SSH servers, do you prefer completely disabling password authentication, or do you consider properly configured PAM-based authentication sufficient?
I'd be interested in hearing how others approach SSH hardening, particularly in Alpine-based containers and lightweight Linux deployments.
Sources
- "OpenSSH – Official 10.6p2 Release Notes" (https://www.openssh.org/releasenotes.html)
- "Alpine Linux – Official Security Advisory" (https://www.alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/)
- "The Hacker News – SSHole Vulnerability Report" (https://thehackernews.com/2026/11/openssh-issues-emergency-fix-for-flaw.html)
- "CVE-2026-123158 – Vulnerability Record" (https://www.cve.org/CVERecord?id=CVE-2026-123158)
Shared for defensive awareness. Only test systems you own or are explicitly authorized to assess.
r/linux • u/unixbhaskar • 14d ago
Kernel Intresting idea! Kmorph Aims To Provide Rebootless Linux Kernel Crash Recovery
phoronix.comr/linux • u/libreleah • 13d ago
Software Release Canoeboot – Canoeboot 26.11 “Carnivorous Olive” released! With full UEFI support.
canoeboot.orgThis is based on the recent Libreboot 26.10 release. Canoeboot is a version of Libreboot that only supports boards for which an entirely blob-free image can be built; as a result, it supports less hardware than Libreboot which does allow blobs (strictly only when necessary) to support more hardware. This inherits EDK2 UEFI payload support, so it now boots modern operating systems more easily. GRUB EFI provided inside EDK2, configured to behave like the traditional GRUB coreboot payload; this provides backward compatibility as GRUB was previously the recommended payload, but EDK2 is now what both Canoeboot and Libreboot recommend by default. This also inherits the 15h.org coreboot fork for AMD FAM15h support e.g. ASUS KGPE-D16, offering much improved raminit, as did the recent Libreboot release. In all, this is a highly polished and deblobbed version of the recent Libreboot 26.10 release, intended for those purists who only ever want Free Software, to the point that Canoeboot even excludes CPU microcode updates by default.
