Replying to @Whostosay@sh.itjust.works
I didn’t saw it was dangerous only that it was similar to MS GDID, and it is.

Replying to @Whostosay@sh.itjust.works
I didn’t saw it was dangerous only that it was similar to MS GDID, and it is.
Replying to @Whostosay@sh.itjust.works
I’m not technically inclined enough to harden against that, nor do ai really have the inclination. But here is a thread on that topic where I even heard about it.
lemmy.mlHarness launches Gitness, an open-source GitHub competitor - LemmyCredit to @marsara9@lemmy.world [/u/marsara9@lemmy.world] (:Replying to @Luffy879@lemmy.ml
See discussion below. I’m making it up obviously
Replying to @Whostosay@sh.itjust.works
That’s fair. I didn’t mean MS was the threat actor, just the seed from which this grew. I definitely take that back after reading up more on where machine-id grew out of.
However, I don’t concede that machine-id is theoretical for user fingerprinting. Any software installed can read it, especially a browser. That’s the vector for tracking across the web. Do I have instances of this occurring, no. Seems plausible and the more we can sandbox things, especially “web browsers” (untrusted app runners more like it) the better.
Replying to @Whostosay@sh.itjust.works
Absolutely zero reason a init system needs admin date of birth. Yes separate issue entirely, but it’s showing a trend and the direction things are headed.
Replying to @very_well_lost@lemmy.world
Cost of doing business
Replying to @bender223@lemmy.today
www.freedesktop.orgmachine-idReplying to @kescusay@lemmy.world
If any of your Linux machines use SystemD, then Microsoft has done that then there’s something to be aware of with those machines. SystemD has a global system ID that can be used like the Windows GDID apparently.
Edit: not MS