 Re: firefox portable fingerprinting default blocking
A lot of folks here are not in agreement as regards whether eBay fingerprinting leads to suspensions or if eBay does fingerprint us at all. Let's just presume for a minute that they do.
This is a guess but, I don't think eBay would appreciate blocking all fingerprints during account creation.
However, we've successfully blocked WebGL and WebRTC for aged, active accounts - with no consequence so far.
If you choose to block these because you think it will personally make a difference to your accounts, it'd be helpful to know the different methods and any associated risks. This should help you decide how to block, should you choose to go on with it.
Option 1. Use the new feature in Firefox:- I think the usefulness of this feature does not apply for stealth purposes.
Firefox does not block all incoming requests to fingerprint you. They just block the ones that they think are engaging in cross-site tracking and fingerprinting at the same time. They determine these after rigorous evaluation.
This allows enough time for any domain to collect all the information they need. This is no different from closing the barn door when all your horses have fled.
In my opinion, this will not be suitable for stealth.
Firefox will have my confidence when they decide to pull APIs that allow fingerprinting or at least permanently implement scripts that block it.
It will be the death of them if they do so now, but I know they're heading there eventually.
Option 2. Addons -: These will serve you well, but addons do break with incompatible updates. Conversely, a browser update can break the addon. Any of these will divulge your secrets to any monitoring websites if something goes wrong.
Option 3. Blocking directly from browser UI -: Opera and Firefox offer to block directly from the user interface, but these are all over the pace, especially Firefox. They do work however until someone at Firefox decides to remove the feature during a major update. In this case, you wouldn't even know it's gone unless you're testing daily before getting on eBay. What a PITA!
Option 4. Browser Command Line Switches:- in my opinion, this is the most reliable way to enforce anything on a browser.
While this method works great, chrome makes it a point to deprecate select commands that enhance privacy.
For example, the chrome switch "--disable-webgl" is supposed to disable ALL versions of WebGL but it does not. It just disables WebGL2.0 while letting 1.0 run amok.
If I wanted to block WebGL and WebRTC on various browsers, my strategy would be something like this:
Chrome: Avoid
Firefox: WebRTC: about:config "media.peerconnection.enabled"
FireFox: WebGL: about:config find “webgl.disabled” change value to "true"
Opera: WebRTC: opera:config -> Advanced -->scroll down. Block WebRTC by selecting "Disable non-proxied UDP"
Opera: WebGL: Right-click on Opera icon on your desktop, click on properties the Shortcut tab should open up automatically. It displays the load path of the browser in the target field. At the end of the field, after the closing ", add a space, and then paste his command: --disable-webgl
Apply, OK, and you're all set.
I'll go in and remove both browser's ability to update anything. I prefer to delete the update files.
If you choose to allow updates, be assured someday something will break and unless you're checking daily, you'd be caught unaware.
Last edited by Pandoras_box; 04-13-2020 at 03:04 PM.
| 
