An audit on 28 October found every mainline kernel memory-safety option switched off in all five
editions. PengyOS builds its kernel from x86_64_defconfig plus three fragments, so anything
nobody added simply wasn't there. Core's fragment now turns on SLAB_FREELIST_HARDENED,
SLAB_FREELIST_RANDOM, LIST_HARDENED, FORTIFY_SOURCE, HARDENED_USERCOPY,
INIT_ON_ALLOC_DEFAULT_ON and ZERO_CALL_USED_REGS. What that means in practice: each one turns a
class of kernel memory corruption into a crash instead of root, for code already running as you.
The cost is near zero for most, and 1-3% on allocation-heavy workloads for zeroing fresh
allocations. Ubuntu, Fedora and Arch ship that one. INIT_ON_FREE, MODULE_SIG and the lockdown
LSM stay off, deliberately, with the reasoning written in the fragment. A post-build check fails the
build if a symbol drops out of Kconfig, and a gate test fails if someone removes one from the
fragment. It went to testing first so the cost could be measured on hardware, because QEMU says
nothing about it.
xdg-desktop-portal-cosmic, the thing behind screenshots, screen casting, the file chooser and
the permission settings Flatpak apps read, was a separate recipe stuck at epoch-1.8.0 building
against its own libcosmic while the rest of COSMIC was on 1.9.0. It's a row of the component table
now, built by the same package, on the same pin, with --locked against a committed lock, and the
nightly watches its releases like every other component.
And a reminder that a release is a pipeline, not a commit. 26.10.47, the first build with COSMIC as
a Buildroot package, stopped at the SBOM step: an apostrophe in a license string broke Buildroot's
legal-info, which quotes that field in single quotes. The quote is escaped, and there's a test for
it.