Two programs in the image were replaced by memory-safe rewrites you use exactly the same way, and opening a port on a Server stopped being an edit of a file you then have to maintain forever.
sudois now sudo-rs 0.2.15 on Server and Desktop (and both NVIDIA editions), the memory-safe reimplementation from the Trifecta Tech Foundation that Ubuntu has used as its default sudo since 25.10. The reasoning is the same one that moved coreutils to Rust: the setuid-root binary that parses every user's arguments and environment is the program most worth having in a language that can't overflow a buffer. Buildroot 2026.08 had no recipe, so it's ours. Nothing you type changes:sudo,sudoeditandvisudoare in the same places,/etc/sudoersgrants the same rules, and/etc/pam.d/sudois the same stack. The image losessudoreplay,sudo_logsrvdandsudo_sendlog, which nothing used. It pins 0.2.15 rather than Ubuntu's 0.2.13 because 0.2.15 fixes a sudoedit symlink race.wheelis the only admin group./etc/sudoersgranted%sudoand the installer put the owner in asudogroup, but/etc/pam.d/sudorequireswheel, so the rule never let anyone in. Tested on a booted Server: a user insudobut notwheelwas refused by PAM. The rule and the group are gone, so the files say what the system already did. Nobody loses access.find,xargs,locateandupdatedbare uutils/findutils 0.10.0 in every edition, replacing GNU findutils 4.10. It was adopted on evidence: a side-by-side run covering everyfindandxargscall in the image's own scripts plus the everyday options gave byte-identical output in all 29 cases. Then the boot test found the one thing the fixture tree couldn't show: under-xdev, pruning a mount point silently ended the walk of its siblings and exited 0. That's a fix we carry, with a regression test, ledgered with an upstream fix as its expiry. Diffutils stays GNU, because uutils/diffutils has no recursive diff.- The firewall moved into Core. Core shipped
nftbut no ruleset, so a Core box, whose stated jobs are router and unattended remote-site machine, accepted connections on every port. Core, Server and Desktop now start from the same default-deny input chain: ssh, mDNS, and replies to connections this machine made. The Desktop is unchanged and still opens everything above 1024 for LAN games, Steam Remote Play and LocalSend. Opening a port used to mean editing/etc/nftables.conf, which on an installed machine lives in the/etcoverlay, so an edited copy would hide every later image's ruleset permanently. Now:sudo pengyos-firewall allow 8086 --from 192.168.1.0/24,removewith the same arguments, andstatus. It validates the whole ruleset withnft -cbefore reloading and removes a rule nft rejected, so a typo can't leave the firewall unloadable at next boot. - 46 tools were deleted. Two sweeps of
tools/removed everything not wired into an image, a build, a release or the nightly loop: pre-COSMIC desktop experiments, early-spec Server tools that the Server overlay replaced, the parked Secure Boot / UKI design, the proposal pipeline the nightly loop superseded, and provenance tools never connected to anything. Three measured prototypes stayed but moved out of the gate.tools/went to 40 directories. - Every patch we carry in a recipe is now ledgered. The gate checked global patch sets, but five recipes carried patches of ours with no entry and no expiry date. Each divergence entry names the upstream release that ends it. Two of them turned out to be forks rather than build fixes, and distrobox's Go rewrite already contains its fix, so that one has an end date.
The documentation got a correction worth naming. SPEC claimed the host-built COSMIC components came in "together with a few host libraries they link", and named them: some GStreamer, an OpenSSL/curl pair, "six libraries cosmic-comp needs". None of it was in the image, and none of it is now. The Desktop post-build has a No host libraries section that deletes the compat directory and the wrapper, removes every library no package claims, and a check fails the build on an unresolved library. The spec now says what the build actually does: the host supplies cargo builds and the dev packages they compile against, and nothing is copied in.