Systemd 261 Release Sparks Fork Over Birth Date Field, Adds Software TPM

The systemd 261 release arrived on June 22, 2026, bringing a software TPM implementation, a new OS installer, and a cloud metadata subsystem. But the update also includes an optional birthDate field in JSON user records, a feature that has already prompted a fork called Liberated systemd.

The fork, published as v261 shortly after the official release, follows upstream systemd while reverting the birthDate field addition. Its author describes the field as "surveillance enablement" and recommends testing the fork in a virtual machine before production use.

What systemd 261 actually adds

Beyond the controversy, systemd 261 includes several technical improvements. The new software TPM (Trusted Platform Module) allows systems without dedicated TPM hardware to use TPM functionality in software, which is useful for virtual machines and cloud instances. The release also adds an IMDS (Instance Metadata Service) subsystem, with a daemon called systemd-imdsd that provides a local Varlink API for accessing cloud instance metadata.

• Software TPM for systems without dedicated TPM hardware, targeting VMs and cloud environments.
• IMDS subsystem with systemd-imdsd daemon for cloud instance metadata access via Varlink API.
• New OS installer integration for streamlined distribution deployment.
• Process state preservation across kexec reboots, improving uptime for critical services.
• Continued effort to load external libraries on demand, reducing memory footprint.

Birth date field backlash and the fork

The birthDate field is optional and stored in JSON user records. Its addition has drawn criticism from privacy advocates who argue it could be used for age verification or surveillance. The Liberated systemd fork explicitly removes this field while staying otherwise close to upstream. The fork's author warns that nightly builds may be unstable and recommends named releases for reliability.

This is not the first time systemd has faced controversy over feature creep. Critics have long argued that systemd, which started as an init system, has expanded into areas like logging, networking, and now user metadata. The fork represents a focused protest rather than a full alternative, as it tracks upstream closely except for the reverted change.

What comes next is uncertain. The birthDate field remains optional and unused by default, but its presence in the codebase could lead to future mandates by distributions or applications. The fork may gain traction among privacy-conscious users, but its long-term viability depends on maintaining compatibility with upstream systemd as new releases arrive.