IrateAnteater comments on Inside the Systemd Age Verification Debate: Developer Responds to Criticism

Inside the Systemd Age Verification Debate: Developer Responds to Criticism (itsfoss.com)

submitted 7 months ago by cm0002@europe.pub to c/linux@programming.dev

63 comments fedilink hide all child comments

Dylan M. Taylor is not a household name in the Linux world. At least, he wasn’t until recently.

The software engineer and longtime open source contributor has quietly built a respectable track record over the years: writing Python code for the Arch Linux installer, maintaining packages for NixOS, and contributing CI/CD pipelines to various FOSS projects.

But a recent change he made to systemd has pushed him into the spotlight, along with a wave of intense debate.

At the center of the controversy is a seemingly simple addition Dylan made: an optional birthDate field in systemd’s user database.

[–] IrateAnteater@sh.itjust.works 14 points 7 months ago (7 children)

You can't really "block" fingerprinting. You can obfuscate it a bit, but the fingerprinting process happens server side, not on your device. So whether or not your system sends whatever age verification signal becomes a part of its fingerprint.

permalink

fedilink

source

parent

hideshow 7 child comments

[–] fruitcantfly@programming.dev 1 point 7 months ago (2 children)

It's not just server-side: A lot of fingerprinting happens client-side, for example using a canvas to check what features your graphics card supports. You can see this in action via services like https://coveryourtracks.eff.org/ or https://amiunique.org/

permalink

fedilink

source

parent

hideshow 2 child comments

[–] IrateAnteater@sh.itjust.works 5 points 7 months ago (1 child)

That's not the fingerprinting happening client side, that's just information supply. Fingerprinting is about what the server does with that information.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Zink@programming.dev 0 points 7 months ago

Yeah, but the countermeasures are client-side because that's what you can control. And some kind FOSS devs out there make it easy to start somewhere decent.

Sent from my LibreWolf

permalink

fedilink

source

parent

[–] quick_snail@feddit.nl -3 points 7 months ago* (last edited 7 months ago) (3 children)

Of course you can block fingerprinting. See Tor Browser. Everyone looks the same.

Or you can change your fingerprint every 30 seconds with a plugin like chameleon.

You know it works when evil sites all ban you because they can't fingerprint you and track you between sessions anymore

permalink

fedilink

source

parent

hideshow 3 child comments

[–] IrateAnteater@sh.itjust.works 7 points 7 months ago (1 child)

That's not blocking the fingerprinting, that obfuscating the data. The fact that you are doing that itself becomes part of the fingerprint being built. Services like Tor or Chameleon don't stop the fingerprinting process running, they just make it more difficult (but not impossible) to tie the fingerprint to your actual identity.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] quick_snail@feddit.nl 0 points 7 months ago

It's making the fingerprinting efforts useless. Sure, they can do it, but many of us are blocking them from being able to uniquely fingerprint and track us across the internet

permalink

fedilink

source

parent

[–] Aatube@lemmy.dbzer0.com 1 point 7 months ago

Here’s the sentence right after the quote:

Privacy-wise, it’d be wise to “blend in” and always report the most common value. Tor browser thinks this way to make users less fingerprintable.

permalink

fedilink

source

parent