MAC address randomization?

[hunixtalk]

Does randomizing MAC address further defend de-anonymizing? Suppose there’s a Firefox bug that allows JavaScript to read MAC address (and further, router MAC like in ip n), all your web browsing is then linked.
Maybe it’s not practical to do this on the hypervisor level, how about VM MAC spoofing? Is it a good idea to change Gateway and Workstation MAC address at times?

[Patrick]

MAC address is mentioned here:

Protocol Leak and Fingerprinting Protection ‎

MAC randomization might make sense on the host. See:

MAC Address

@hunixtalk

Suppose there’s a Firefox bug that allows JavaScript to read MAC address (and further, router MAC like in ip n), all your web browsing is then linked.

As for MAC address inside VMs…

Using Multiple Whonix-Workstation ™ is generally recommended.

If such a bug allows to read the MAC address of the VM, what other things should be presumed readable from remote (such as Firefox when having a bug)? I am asking, because then the following would apply:

VM Fingerprinting

See also:

MAC address anonymization

I would like to raise community awareness on MAC address anonymization. Tails project actually documents various threats at https://tails.boum.org/contribute/design/MAC_address Most concerning to me actually is “Active probe fingerprinting” documented at https://tails.boum.org/contribute/design/MAC_address/#index7h1 While using Wifi is generally recommended against, I guess people use it and from my perspective we should closely follow what Tails is going to release here (currently in testing)…