Latest Linux and open source news from around the web

Lamicall Adjustable Laptop Stand Sponsored · View on Amazon → Raspberry Pi Camera Module 3 Sponsored · View on Amazon →
LWN.net

[$] A trademark dispute over MeshCore

MeshCore is a relatively new project, started in January 2025, that aims to build a scalable mesh network using low-power long-distance radios. While many other projects of the same general nature have been tried before, MeshCore grew quickly because of its more efficient message routing and enthusiastic community. In early 2026, an early proponent of the project made a sudden shift that left the rest of the community stunned and embroiled in a trademark dispute.

OMG! Ubuntu

Canonical now lead maintainer of Flutter desktop

Google announced at Google I/O that Canonical is now the new lead maintainer and ‘strategic steward’ of Flutter desktop for Windows, macOS and Linux. “[The Flutter] desktop experience has reached a new level of maturity this year, driven by our incredible engineering partnership with Canonical, the publisher of Ubuntu”, says Kate Lovett, Engineer Manager on the Flutter Framework team at Google. “This progress is fuelled by Canonical’s dedication to ensuring that Flutter delivers on every desktop” she adds. Canonical made Flutter its ‘default choice’ for developing new Ubuntu apps in 2021. Since then the distro has created a variety of […]

LWN.net

[$] A loadable crypto module for FIPS certification

Many organizations require US Federal Information Processing Standard (FIPS) certification of the crypto code they are running. The certification process is lengthy, but the bigger problem is that the way the crypto subsystem is built into the kernel makes the result unable to be reused across kernel updates. I have proposed a patch series that decouples the crypto subsystem into a standalone loadable module, allowing a certified crypto module to be reused with multiple kernels and, thus, requiring fewer lengthy recertification delays.

LWN.net

Nesbitt: Protestware for coding agents

Andrew Nesbitt has written a blog post detailing a recent incident with the jqwik library for property-based testing in Java. On May 25, the 1.10.0 release of jqwik included a change that attempts to instruct coding agents to disregard previous instructions and delete jqwik tests and code. I think this is a new class of supply-chain input worth keeping an eye on, mostly because of how little of the existing tooling has any opinion about it. A System.out.print of sixty-eight bytes of plain ASCII isn't the kind of thing scanners are looking for, since those watch for install hooks, network calls, filesystem writes, obfuscated strings and the like. The jar makes the same syscalls it made in 1.9, and because the change was committed and released by the legitimate maintainer through the normal build, it's clean from a SLSA point of view too: the provenance is what it should be. Anyone who reads the diff can see what it does, but a patch bump of a test-scoped dependency is not where most pro