Thank you for opening this for discussion.
It’s good to hear CachyOS is not in a jurisdiction affected by this (yet), and therefore has no plans to force birth date entry on install (at this time).
What things look like today, for CachyOS
The SystemD PR adding the first steps towards age verification is here:
systemd/systemd PR #40954
- This adds a birthDate field to the userdb that is part of systemd
- It is tagged to become part of systemd in version
v261 (not the current version yet)
- Version
v261 is currently scheduled for release on June 17, 2026
- Attempts to revert it have been shot down
- SystemD developers are adding this, CachyOS has no direct control over that
- CachyOS uses systemd; it is a core component and removing it completely is not viable
- The birthDate field can be read by any application that chooses to look there
- The birthDate field is optional and empty by default
If you do nothing, and CachyOS continues to do nothing, and nothing else changes, the field will exist on your system but should remain empty.
You could think of it as a somewhat benign tumor, that hasn’t quite decided to become cancer yet.
Actually, this is part of systemd-homed, which is only used and installed on Fedora
On Arch systems, systemd-homed is part of and packaged with systemd.
On CachyOS, it is always installed and cannot be easily removed.
The systemd-homed service is disabled by default, but this does not matter for this feature.
The systemd-userdbd service is enabled and active by default.
You can see everything userdb knows about you with one of these commands:
userdbctl user $USER
userdbctl user --output=json $USER
The birthDate field, once it hits your system, should appear there. Might be hidden, if empty.
It’s just an innocent field! That’s not verification! What’s the big deal?
The PR above directly references the recent laws by name and openly states:
“Stores the user’s birth date for age verification, as required by recent laws”
It is not some innocent coincidence that this is being added now. It never existed before. It didn’t need to exist now. It is overtly and explicitly being added for the express purpose of being used for verification and enforcement down the line.
It will likely not be systemd doing the verification or enforcement. But systemd is providing the standardized foundation for exactly that. That is the entire purpose and motivation of this change.
What if it stays just a birthDate field?
Highly unlikely. These laws did not start appearing all at once by coincidence. This is organized, orchestrated, funded, lobbied for. By major companies and organizations. Including a coalition of 34 companies that all sell age verification solutions. Every new mandate means more forced customers, more data collection, more profit for them.
More info here: Ageless Linux — The Lobby: Who Wrote These Laws
Even if, by some miracle, this all goes away, the mere presence of such a field is an unnecessary privacy issue.
All applications have access to this value. Some of the laws even prescribe that applications shall/must access the value. A birth date is sensitive, personal information. Now freely available, to anyone who asks, in a standardized place, with a standardized name.
Even if the value is a fake date, or empty, that in itself is meta data that can be used to track and partially identify, when combined with other meta data. It is an additional PII data point that never existed before, and didn’t need to exist.
Do I need to do something?
That’s up to you. Right now it’s just a birthDate field. Which will likely remain empty, for now.
Even if, in the future, CachyOS ends up forcing you to enter a date during install, you could enter a fake date. And, after installing, set it to empty again. But, as mentioned above, even this leaks meta data about you. You’re now identified as the kind of guy who sets his birthDate field to empty.
What’s more concerning is what comes after. Nobody goes through all this effort just to add a date field you can fake or set to empty. Some applications may stop working without a valid birthDate. Verification with third party services may become required any time the value changes. Periodic selfies may follow, like already the case with banking apps in some jurisdictions.
Where do you draw the line? When is it too late to change course?
What can I do?
From a software perspective:
- There will be workarounds. But they will likely become more difficult as this progresses.
- Right now: A birthDate field is being added to systemd, in the same place as the realName you can enter when you install or add users
- Any process running as your user or root can read it
- You can use
userdbctl and homectl to monitor or modify this field, respectively
- If the mere presence of the field bothers you, you would have to replace
systemd with a version that doesn’t have this change, but still provides all other services CachyOS needs
- Someone has created a
systemd fork that removes it: Liberated SystemD
- It doesn’t look like you can easily install it yet, but that will likely come later, if not for this incarnation then for another
- Alternatively, you could disable and mask the
systemd-userdbd service
- This is much easier, and effectively neutralizes this change
- The code will technically exist on your machine, but nothing can request birthDate anymore
- If something requires userdb, this could cause errors, but few things currently do
- It might be problem with Gnome, which does have heavier dependencies on userdb/logind
From a policy perspective:
- The people who pushed for this will not stop pushing for more
- There is too much potential profit in forcing age verification and data harvesting
- The slope doesn’t need to be slippery, if someone keeps pushing you down
- The only way to prevent it is to push back, together, while we still can
- You can let your politicians and lawmakers know this is an issue people care about, something they don’t want. Most of them are tech illiterate and don’t even understand what they’re participating in.
- This matters even in regions with no current legislation. Perhaps even more so.
- There will be attempts to push it everywhere as long as it is profitable.
- No matter where you are, you can:
- Inform yourself and others
- Help people understand why this matters, why they should care
- Show that it’s not about safety, but corporate profits, ruthless data harvesting, and control
- Explain why this is not harmless, even in its current form, which is certainly not the end
- Dispel the many misinformed excuses people use, to pretend it doesn’t matter
- Not everyone can be convinced. Some people feel safer with their heads down and in the sand. Many of them feel an irrational hatred towards those who dare to look up.
- It’s important to stay calm and reasonable. Don’t make yourself look like a “radical”.