systemd devs successfully rage baited you and a bunch of others. It’s time to let it go.
But if you don’t want to, let me ask, how do you think a data field with no connection to any access control subsystem, is going to prevent anyone from logging in?
No. A database doesn’t have these specific fields by default.
Neither does systemd. They are optional.
LDAP has had a birth date field for like 20 years now. Is it “complicit” as well?
Fields are optional, but developers of systemd consciously preimplemented those fields.
And in a DB that’s not the case.
This field appeared in LDAP for different reasons, than age control.
systemd devs successfully rage baited you and a bunch of others. It’s time to let it go.
But if you don’t want to, let me ask, how do you think a data field with no connection to any access control subsystem, is going to prevent anyone from logging in?
Should that be their goal?
It isn’t. I’m pretty sure the dev working on that userdb field didn’t plan on getting death threats on github and said as much afterwards.