Add an option in about:config to disable unicode range
Categories
(Core :: Layout: Text and Fonts, enhancement, P3)
Tracking
()
People
(Reporter: Tom25519, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
I try to disable unicode range.
Actual results:
Here're no option in about:config to disable it.
Expected results:
Add an option in about:config to disable unicode range.
|
||
Comment 1•3 years ago
|
||
Why do you want that?
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1)
Why do you want that?
I try to make my browser fingerprint the same as Tor Browser's, but font fingerprinting and web browser features detection are still different (Unicode Range should be "false"), I search on internet, it says that set layout.css.unicode-range.enabled = false, but it totally dosn't work.
|
|
||
Comment 3•3 years ago
|
||
I don't think we want to add flags to disable this unless it really prevents fingerprinting in any measurable way. Do you know why Tor might disable this?
|
|
||
Updated•3 years ago
|
|
||
Comment 4•3 years ago
|
||
(In reply to Tom25519 from comment #2)
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1)
Why do you want that?
I try to make my browser fingerprint the same as Tor Browser's, but font fingerprinting and web browser features detection are still different (Unicode Range should be "false"), I search on internet, it says that set layout.css.unicode-range.enabled = false, but it totally dosn't work.
Tor Browser does not set that preference. The preferences it sets are in these files: https://gitlab.torproject.org/tpo/applications/tor-browser/-/tree/tor-browser-102.11.0esr-12.5-1/browser/app/profile
Tor Browser does ship specific fonts with it, and restrict the fonts available to those, which is my best guess for why you would get different unicode ranges between Firefox and Tor Browser.
You're not going to get Firefox to look identical to Tor Browser, it's just not feasible, and by customizing Firefox more you're going to look more unique - not less. If you want to limit your fingerprint and match as many people as possible (ignoring the problem of IP addresses), I would either use Tor Browser; use Mullvad Browser which is basically TB without tor; or use Firefox and set the (unsupported) privacy.resistFingerprinting preference (and the letterboxing preference) - but not customize them further.
(In reply to Tom Ritter [:tjr] from comment #4)
(In reply to Tom25519 from comment #2)
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1)
Why do you want that?
I try to make my browser fingerprint the same as Tor Browser's, but font fingerprinting and web browser features detection are still different (Unicode Range should be "false"), I search on internet, it says that set layout.css.unicode-range.enabled = false, but it totally dosn't work.
Tor Browser does not set that preference. The preferences it sets are in these files: https://gitlab.torproject.org/tpo/applications/tor-browser/-/tree/tor-browser-102.11.0esr-12.5-1/browser/app/profile
Tor Browser does ship specific fonts with it, and restrict the fonts available to those, which is my best guess for why you would get different unicode ranges between Firefox and Tor Browser.
You're not going to get Firefox to look identical to Tor Browser, it's just not feasible, and by customizing Firefox more you're going to look more unique - not less. If you want to limit your fingerprint and match as many people as possible (ignoring the problem of IP addresses), I would either use Tor Browser; use Mullvad Browser which is basically TB without tor; or use Firefox and set the (unsupported) privacy.resistFingerprinting preference (and the letterboxing preference) - but not customize them further.
In fact, I did it. First, I open Tor Browser directory\Browser, then I open onmi.ja with WinRAR, next, I open omni.ja\defaults\preferences, export 000-tor-browser.js, unneeded items, such as proxy settings. Last but not least, copy font files from Tor Browser directory\fonts to the same path of firefox. When I directly import 000-tor-browser.js, and only cancel using proxy, I get the result in browserleaks.com that only Font Fingerprinting should be 2301 fonts and 91 unique metrics found, Web Browser Features Detection Features Hash should be dcecd89c46914829759fc195ecbb3eb3 (because Unicode Range = true, not false), everything else is the same!
Oops, I make a typo: "export 000-tor-browser.js, unneeded items," should be "export 000-tor-browser.js, delete unneeded items". I couldn't edit submitted comment.
|
|
||
Comment 7•3 years ago
|
||
So... that level of browser hacking is really unsupported, and I'm not even sure how to reason about it, when xul isn't going to match what you're copying around for omni. I'm also not sure what is going on with browserleaks because it reports Unicode Range support as false for 113, 114, and Tor Browser.
(In reply to Tom Ritter [:tjr] from comment #7)
So... that level of browser hacking is really unsupported, and I'm not even sure how to reason about it, when xul isn't going to match what you're copying around for omni. I'm also not sure what is going on with browserleaks because it reports Unicode Range support as false for 113, 114, and Tor Browser.
Really? I test 113.0.1, browserleaks reports Unicode Range support is true.
|
|
||
Comment 9•3 years ago
|
||
(In reply to Tom25519 from comment #8)
(In reply to Tom Ritter [:tjr] from comment #7)
So... that level of browser hacking is really unsupported, and I'm not even sure how to reason about it, when xul isn't going to match what you're copying around for omni. I'm also not sure what is going on with browserleaks because it reports Unicode Range support as false for 113, 114, and Tor Browser.
Really? I test 113.0.1, browserleaks reports Unicode Range support is true.
Apparently it's OS dependent - Windows reports true, Linux reports false.
Description
•