I was ambivalent about systemd up until now. If this gets merged I’m moving to a non-systemd distro. I do not live in California or even the USA. I do not want age verification garbage in my OS.

@skyline2@lemmy.dbzer0.com @linux@lemmy.ml

Brazilian here. I’m neither a lawyer nor a specialist, just someone who has read the Portuguese text from the Brazilian flavor of the ongoing worldwide age check set of laws.

I must note that the Brazilian age check law (Lei 15.211/2025) specifies “vedada a autodeclaração” (English: “self-declaring is forbidden”). This means that this kind of implementation, where age or birthday is an user input, wouldn’t be compliant to Lei 15.211/2025, because it requires the age information to be assessed independently from the user whose age is being assessed. This means face biometrics, government-issued ID (in our case, CPF, CNH, Passaporte and similar) or “behaviorial analysis”… Anything but a “yes I’m 18” or “I was born in day month year”, for those are self-declared and the Law says it’s “not enough”.

Someone should warn the systemd maintainers of this “Brazilian jabuticaba”.

(Cross posting this reply of mine because the post was cross posted to two different Lemmy instances)

what a fucking bootlicker

In my opinion, storing a date is pretty much irrelevant unless there’s a process that validates the supplied date, otherwise every Linux user was born on 1/1/1, if not, an administrator can “fix” that

Furthermore, that systemd thinks that it’s the place to store such information is in my opinion beyond absurd.

Who appointed that project the source of age truth in the Linux ecosystem? What discussion was there, who was consulted and where was the vote?

The answer to the PII issues is hence not restrictions in userdb, the answer is proper app sandboxing. And that even already exists in flatpak! It restricts access to $HOME already, and to userdb too! And that’s the way to do it!

I don’t use flatpak. I don’t like it. Linux is about choice and I choose not to use that.

Hence, just embrace app sandboxing! And if you come to me and say “hey, I run all my apps without sandboxing, but i want the birthday hidden anyway” then I can only say, your model is really really broken. Fix your security model first, then come back.

In the words of the great Linus Torvalds, go fuck yourself.

What is the most effective way to gather all of my personal stuff within Linux and it be as plug and play with every distro as possible?

Like if I wanted to infinitely distro hop to avoid this fucking Trainwreck right here, how would I easily and effectively ensure I can?

Can I take a set of folders?

Is there a backup format of some kind?

Is there a way to do this with installed programs in a way that can be dropped in?

Unless it is fought, this corporate-driven rot will burrow all the way down to the sub-processor TEE/TPM and all the way up to the web browser/app.

echo "18+" > ~/.age_rc

Am I compliant with California’s law now? Apps can use the POSIX API to access my age.

That’s it! >:-( I’m going back to init. /s

It is possible that California law will be changed. But similar ideas are popping up in other contexts and it’s unlikely that they’ll all go away. This implementation is fairly generic and useful for other things besides age verification, so we shouldn’t decide whether to merge it or not based on a single law in any jurisdiction.

https://github.com/systemd/systemd/pull/40954#issuecomment-4032355482

deleted by creator

deleted by creator