Revert "userdb: add birthDate field to JSON user records"
The systemd project has officially reverted a commit that would have added a birthDate field to user records, citing significant privacy risks and a mismatch with open-source values.
Conversation
It's an optional field in the userdb JSON object. It's not a policy engine, not an API for apps. We just define the field, so that it's standardized Hence, please move your discussion elsewhere, you are misunderstanding what systemd does here. It enforces And sorry, I am really not interested in these discussions here. it's not the right place for this, and please don't bring it here. Thank you.
This reverts commit acb6624, reversing changes made to ba1caf0. Revert "userdb: add birthDate field to JSON user records (#40954)"
After extensive community discussion, legal review and consideration of privacy implications, we have decided not to implement OS-level age attestation / age bracket signaling as initially prototyped.
Reasons for revert:
- Privacy & freedom concerns: A new class of sensitive user data in the OS that didn't exist before, and could be extended to far more invasive controls in the future.
- Open Source philosophy mismatch: Neither the structure nor the desire to act as identity / age authorities. It conflicts with the "permissionless/un-required" experience that many users value in Linux.
- Practical & enforcement issues: Risk of de-facto requirements if sites decide to distrust non-signaling OSes.
- Legal / jurisdictional overreach: Laws drafted for volunteer / decentralized projects are often complex; precedent exists to simply not comply rather than build half-measures.
- No upstream consensus: Lack of agreement on concrete changes.
We may revisit if there is a zero-knowledge / privacy-preserving way to signal age with no birth date storage. For now: keep the system free of age-related metadata and APIs.
Source: Hacker News
