Virtual Machine Detection in the Browser (2019)

Re:Virtual Machine Detection in the Browser (2019) by _trampeltier on Saturday December 19, 2020 @05:01AM (#25476419)

I didn't know WebGL leaks so much information about my machine. I already open a browser just in ingokigno/private mode 90% of the time. Maybe is time to start just each time a different VM for browsing.

[ Parent | on HN ]

Re:Virtual Machine Detection in the Browser (2019) by gruez on Saturday December 19, 2020 @09:14AM (#25477500)

It's not limited to just webgl, there's a whole suite of browser features that can be used to "fingerprint" your browser. see: https://news.ycombinator.com/item?id=25166703

[ Parent | on HN ]

Re:Virtual Machine Detection in the Browser (2019) by jmnicolas on Saturday December 19, 2020 @05:05AM (#25476432)

I tried it, it's highly inconvenient. Maybe QubesOS would help, not sure.

[ Parent | on HN ]

Re:Virtual Machine Detection in the Browser (2019) by gruez on Saturday December 19, 2020 @09:16AM (#25477507)

That wouldn't really help. The containers/VMs might be separated from each other, but they're running on the same hardware/software stack, so they'll behave the same should you decide to fingerprint it.

[ Parent | on HN ]

Re:Virtual Machine Detection in the Browser (2019) by jmnicolas on Saturday December 19, 2020 @10:00AM (#25477768)

I meant for convenience since launching VM is part of the OS.

Wouldn't every Qubes VM (whatever the underlying physical machine) return the same fingerprint? Something like VM Fedora version XXX running on Xen hypervisor.

[ Parent | on HN ]

Re:Virtual Machine Detection in the Browser (2019) by gruez on Saturday December 19, 2020 @02:59PM (#25480646)

Depends how they do 3d rendering. If it's passed through to the host gpu, then it's fingerprintable. If it's using some sort of software renderer that might be fine, but the performance is going to be garbage.

[ Parent | on HN ]