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.
Or a random GDID on each read?
No GDID sounds like it sticks out a lot more.
It would make more sense just not use windows to begin with.
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.
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