Date: Tue, 10 Mar 2026 14:33:28 +0200 From: Volodymyr Kostyrko <arcade@b1t.name> To: "freebsd-hackers@FreeBSD.org" <freebsd-hackers@freebsd.org>, freebsd-pkg@freebsd.org Subject: Re: Practical suggestions for resolving the Age Verification problem Message-ID: <aedadee6-8840-4a98-b719-eb0820c8912d@b1t.name> In-Reply-To: <17977bb140d10505168a9af142dc09c8@bsdforge.com> References: <08dc619e-955a-438d-86ba-751b1fa63bce@vincentbentley.co.uk> <qurrwbveytgowgynhnxl@gnvo> <jlqpgyurrtctmgglpwgh@msbt> <CANCZdfpTcV36wOUh4ivQt0GfH5cPfzh7MiQKAgAXXbOxwDEYUw@mail.gmail.com> <tldnfperrvgxbipskaof@hbbd> <e29bbfc4f76aa2d5bdf8bd452460b7eb@bsdforge.com> <CADqw_gLdF2QSnSqsEBBu0aLg14gHmcLJC6qu-X-5L8HiUt80Vg@mail.gmail.com> <17977bb140d10505168a9af142dc09c8@bsdforge.com>
index | next in thread | previous in thread | raw e-mail
10.03.26 11:39, Chris: > On 2026-03-10 00:44, Michael Schuster wrote: >> On Mon, Mar 9, 2026 at 11:13 PM Chris <bsd-lists@bsdforge.com> wrote: >> >>> On 2026-03-09 10:39, vermaden wrote: >>> > Lucas Holt from MidnightBSD just created aged(8) here: >>> > - https://github.com/MidnightBSD/src/tree/master/usr.sbin/aged >>> >>> While I think the initiative as written is untenable (unenforceable) >>> Wouldn't it be enough to write an additional field to adduser(8) >>> say; born / over 13? Then allow ports to use it as they so choose? >>> It's a dead simple approach w/ near zero work/overhead. >>> >> >> Speaking as a "naive" user and developer: >> Where would you want to store that information? the GECOS field is known >> nearly universally, you can't just change it, it'd break ... lots ot >> stuff. >> >> Besides: storing people's age in a publicly visible place probably >> wouldn't >> fly with many people, esp in the EU. > I was thinking more on the lines of permissions of different users in > the same > way their regulated already. Adding another category and applying > appropriate > perms to match. It basically changes nothing in the way a system regulates > user categories now. I was simply suggesting adding another (age based) > category. > Perms can be set accordingly. > Seemed like an painless possibility. Maybe I'm over/under thinking it? There's a really bad example on storing sensitive (PII) information. During World War ][ there was many more victims amongst jews in Netherlands then in all France, and one of the reasons for that was better government records. What is currently is being discussed is PII - Personally Identifiable Information, that can be used to select and target less protected citizens, easy pray. Storing this information in files in clear form makes this information accessible to anyone who can access host (including remote access). Storing this information in encrypted form to be available only under select user is also prone to be queried by any malicious software, including remote exploits resulting in targeting kids online. So I humbly ask all developers here to think twice before querying, storing and making available any sensitive information that is not required for system to function so none of us would later be liable for disclosure. -- Sphinx of black quartz judge my vow.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aedadee6-8840-4a98-b719-eb0820c8912d>