Personally I tend to avoid running untrustworthy programs outside of a sandbox or VM.
what does that mean? are you not running any programs at all? you cannot know just by looking at the name if a program reads such sensitive info. and its not unlikely that some developer figured it would be a good idea to include it in automatic crash reports
yes, this is sensitive information. its like your fingerprint, you cannot change it. I think its quite obvious. web browsers firefox is fighting to hide more and more that even indirectly could lead to identification. websites can’t read this ID, this is just a comparison.
Are you a believer in the idea “They who have nothing to hide have nothing to fear”? Hint: You shouldn’t be.
And do you know for certain that your sandboxes and VMs don’t simply pass through the CPUID instruction? And if they don’t, do they rotate their fake CPUIDs? And how often does that happen?
Why not? Is that information considered sensitive? Personally I tend to avoid running untrustworthy programs outside of a sandbox or VM.
what does that mean? are you not running any programs at all? you cannot know just by looking at the name if a program reads such sensitive info. and its not unlikely that some developer figured it would be a good idea to include it in automatic crash reports
yes, this is sensitive information. its like your fingerprint, you cannot change it. I think its quite obvious.
web browsersfirefox is fighting to hide more and more that even indirectly could lead to identification. websites can’t read this ID, this is just a comparison.Are you a believer in the idea “They who have nothing to hide have nothing to fear”? Hint: You shouldn’t be.
And do you know for certain that your sandboxes and VMs don’t simply pass through the CPUID instruction? And if they don’t, do they rotate their fake CPUIDs? And how often does that happen?