← Back to context

Comment by hypfer

7 days ago

Wouldn't it make more sense to instead use the same GDID on thousands of hosts?

Or a random GDID on each read?

No GDID sounds like it sticks out a lot more.

10 comments

hypfer

Reply
happosai  7 days ago

Trying to make windows work differently than what Microsoft wants is a losing proposition.

It would make more sense just not use windows to begin with.

  • userbinator  7 days ago

    Vibe-coding a sufficiently compatible replacement seems increasingly possible. ReactOS and WINE can either get on board, or if they still try their IP pearl-clutching, I suspect they'll be replaced by something else. Bonus points for using Copilot to do it.

jmclnx  7 days ago

Or recreate it on every boot :)

For example, it you are paranoid about Linux's /var/lib/dbus/machine-id file you can easily use dbus-uuidgen(1) to re-create it on shutdown.

Melatonic  7 days ago

Or just have the option of any of these

Same GDID would pollute the data for Microsoft if enough people did it. Which would also incentivise a fix or another way to differentiate.

Random GDID would likely be the most "security through obscurity" approach but still allow tracking per "session" or whatever time period it changed in.

No GDID could stick out more and if enough people did it also incentivise a fix.

Hard to say which is best but I also like another persons suggestion of random GDID assigned at boot. Or maybe no GDID by default with the option to spoof a random GDID manually