It though I had Skype, Spotify and Slack installed. I only have Slack installed.
Windows can sometimes say you have Skype, because it comes bundled even if you didn't install it yourself.
Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
41–50 of 213 posts
Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#42Worked perfectly on Firefox 88.0.1 on Windows. Great to know despite my efforts to balance privacy and anonymity, there is another metric that I'm unique in. Fingerprinting is just insidious.
When you need privacy, always browse in a VM or a Tails boot.
Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#43Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#44Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#45Does this actually work correctly for anyone? Got wrong results for Firefox and Chrome on Linux (it warns that Chrome probably won't work). I glanced through the source[0] and my about:config and I noticed I have the dom.block_external_protocol_in_iframes setting enabled. Looks like this could be the mechanism they use? I don't remember enabling it manually. Otherwise, it could be my tiling window manager messing wit…
Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#46I wish we could find a way to deal with this risk that's not simply disabling all kinds of functionality. Browser APIs seem to be suffering more and more by limitations to prevent finger printing.
Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#47Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#48Re: Vulnerability allows cross-browser tracking in Chrome, Firefox, Safari, and Tor
#49Does this actually work correctly for anyone? Got wrong results for Firefox and Chrome on Linux (it warns that Chrome probably won't work). I glanced through the source[0] and my about:config and I noticed I have the dom.block_external_protocol_in_iframes setting enabled. Looks like this could be the mechanism they use? I don't remember enabling it manually. Otherwise, it could be my tiling window manager messing wit…