Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T01:07:55Zhttps://gitlab.torproject.org/legacy/trac/-/issues/31917Investigate shipping bundled fonts on Android2020-06-16T01:07:55ZMatthew FinkelInvestigate shipping bundled fonts on AndroidIn #31881 we found the correct method for shipping bundled fonts in Tor Browser on Android.
1. Do we need to ship bundled fonts?
1. Which fonts should be ship?
1. How do these impact apk size?
1. How does this impact language support?In #31881 we found the correct method for shipping bundled fonts in Tor Browser on Android.
1. Do we need to ship bundled fonts?
1. Which fonts should be ship?
1. How do these impact apk size?
1. How does this impact language support?https://gitlab.torproject.org/legacy/trac/-/issues/31141font.system.whitelist value typo?2020-06-16T01:07:21ZThorinfont.system.whitelist value typo?On windows (haven't checked Mac or Linux yet) the `font.system.whitelist` contains
```
..., Microsoft JhengHei, Microsoft JengHei UI, ...
```
In looking at some font lists used for enumeration, I don't see the second font spelt this w...On windows (haven't checked Mac or Linux yet) the `font.system.whitelist` contains
```
..., Microsoft JhengHei, Microsoft JengHei UI, ...
```
In looking at some font lists used for enumeration, I don't see the second font spelt this way - e.g Arthur's ordered list at https://github.com/arthuredelstein/tordemos/blob/gh-pages/fontList.txt#L477 . Even a google search for the one used in the whitelist corrects itself to `Showing results for Microsoft JhengHei UI`
Just checking in with the font experts to see if this is a typo
- JengHei UI <- used in whitelist
- J`h`engHei UI <- used everywhere else I looked so farhttps://gitlab.torproject.org/legacy/trac/-/issues/30589Tor Browser on Windows does not support Hindi or Tamil.2020-06-16T01:04:16ZAadi BajpaiTor Browser on Windows does not support Hindi or Tamil.Works on the Android app.
Hindi and Tamil fonts fail to render as seen on Wikipedia, might be other common languages may not be supported as well but I haven't looked further into it.
![https://i.imgur.com/KhpCUyp.png](https://i.imgur...Works on the Android app.
Hindi and Tamil fonts fail to render as seen on Wikipedia, might be other common languages may not be supported as well but I haven't looked further into it.
![https://i.imgur.com/KhpCUyp.png](https://i.imgur.com/KhpCUyp.png)https://gitlab.torproject.org/legacy/trac/-/issues/30532font FP reveals different Windows releases2020-06-16T01:03:53ZThorinfont FP reveals different Windows releasesbased on Arthur's work [1], I have been looking at the enumerate fonts FP for TB 8 and 8.5a and various platforms.
[1] https://ghacksuserjs.github.io/TorZillaPrint/TorZillaPrint.html#fonts
^^ just click run tests, and the only test I h...based on Arthur's work [1], I have been looking at the enumerate fonts FP for TB 8 and 8.5a and various platforms.
[1] https://ghacksuserjs.github.io/TorZillaPrint/TorZillaPrint.html#fonts
^^ just click run tests, and the only test I have actually added is the one we're concerned about
- Linux distros all seem to be the same - I will test more
- I do not have a Mac, but I do have one result, should anyone like to contribute, and I don't think Macs would vary
- But I found Windows (so far in three out 3 cases) is revealing the major version and maybe the architecture. I believe this might be fixed by looking at the font whitelist, but Windows 10 is a rather drastic change (at least from Win7).
- I will try and get Win10-32bit, Win8.1 32+64bit results to build a complete picture of Windows font entropy. **If you can provide it instead of me trying to find isos and setting up more VMs, then please do**
So here are some results (8.0.9, 8.5a12)
- Win 7 32bit: `9e5d39b4542cd5e2a19f73b8fa566e679fa561e5` (62 fonts)
- Win 7 64bit: `ad4ccd607603041d3e89aa8e03e2e203fc184653` (61 fonts)
- Win8.1 32bit: please help
- Win8.1 64bit: please help
- Win 10 32bit: please help
- win 10 64bit: `1389aaf4c97027b8157c5fb9ef5ed6f141a6b8a1` (36 fonts)
also, FYI
- mint (32/64bit), ubuntu, debian: `09a4ee037c9082b9b8f0b7ae981c656d517faffa`
- mac 10.14: `4094aedc000205c711385fad32827e60462976dc`
Note that the 1 font difference between Win7 32 and 64 bit is just the count, there are actually three changes. I will post the font lists for the three windows results in the next posthttps://gitlab.torproject.org/legacy/trac/-/issues/27880Sinhala Unicode error on Windows 102020-06-16T00:51:34ZTracSinhala Unicode error on Windows 10Sinhala Unicode not shown correctly.
**Trac**:
**Username**: roosjrSinhala Unicode not shown correctly.
**Trac**:
**Username**: roosjrhttps://gitlab.torproject.org/legacy/trac/-/issues/26080torbrowser 7.5.4 update seems to generate file with unique uuid in it2020-06-16T00:46:12Zcypherpunkstorbrowser 7.5.4 update seems to generate file with unique uuid in itupdating from 7.5.3 to 7.5.4 on linux seems to include a file named '.uuid' in the fonts dir that appears to be unique (comparing two different updated torbrowsers)updating from 7.5.3 to 7.5.4 on linux seems to include a file named '.uuid' in the fonts dir that appears to be unique (comparing two different updated torbrowsers)https://gitlab.torproject.org/legacy/trac/-/issues/22952Tor Browser Arabic Fonts Issue !2020-06-15T23:45:39ZTracTor Browser Arabic Fonts Issue !Hi. can you help me kindly to resolve fonts issue with this site:
https://sites.google.com/site/arcommunistslibrary
This site in Arabic language. Please look to it in normal firefox browser (on Windows or Linux), then compare it with i...Hi. can you help me kindly to resolve fonts issue with this site:
https://sites.google.com/site/arcommunistslibrary
This site in Arabic language. Please look to it in normal firefox browser (on Windows or Linux), then compare it with it's appearance in Tor (regullar Tor or Tor of Tails are same error).
On Tor, size of fonts are big (look for right sidebar navigation for example). Fonts of Arabic contents are not the original fonts !
How to solve this error ? I tried the following (but failed):
"preferences", then "contents", then from "fonts & colors" selected "advanced" & set the following:
- fonts for: Arabic
- proportional: sans sarif
- sarif: sans sarif
- sans sarif: sansarif
- monospace: monospace
then I tried (but also failed):
- fonts for: Arabic
- proportional: sans
- sarif: sans
- sans sarif: sans
- monospace: monospace
then I tried (& also failed):
- fonts for: Arabic
- proportional: sans sarif
- sarif: sans
- sans sarif: san sarif
- monospace: monospace
In all above cases, I had 2 subtrials: 1st with uncheck "allow pages to choose their owen fonts" box, & 2nd with check this box (after failure when uncheck it).
In all above trails, after set parameters, I restart Tor browser. All my effort failed !!
I contact their owners on their e-mail that existing on their site. They inform me that they use "Arial" as the default fonts for their site, & most content on their site are in "Arial".
Please, is their any fix for this issue ?
Best
**Trac**:
**Username**: sigma4111https://gitlab.torproject.org/legacy/trac/-/issues/22787Fontconfig warning: remove 'blank' configuration2020-06-15T23:45:21ZcypherpunksFontconfig warning: remove 'blank' configurationIn the log:
> Fontconfig warning: line 145: blank doesn't take any effect anymore. please remove it from your fonts.conf
Quickly skimming fontconfig's changelog one finds:
> commit 46b2c62faa64250eec3981ee816e91a9a3dee857
> Author: Ak...In the log:
> Fontconfig warning: line 145: blank doesn't take any effect anymore. please remove it from your fonts.conf
Quickly skimming fontconfig's changelog one finds:
> commit 46b2c62faa64250eec3981ee816e91a9a3dee857
> Author: Akira TAGOH <akira@tagoh.org>
> Date: Wed Jun 17 16:29:08 2015 +0900
>
> Add a warning for blank in fonts.conf
>
> and remove the unnecessary code for parsing blanks
>
> src/fcxml.c | 7 +++++++
> 1 file changed, 7 insertions(+)https://gitlab.torproject.org/legacy/trac/-/issues/22070Check whether we need to update our font whitelist for ESR682020-06-15T23:43:13ZGeorg KoppenCheck whether we need to update our font whitelist for ESR68While looking over the diff of `all.js` between esr45 and esr52 I noted that the font settings changed quite a bit between those two ESR versions. We should check whether we need to update our font whitelist. In particular now, that we a...While looking over the diff of `all.js` between esr45 and esr52 I noted that the font settings changed quite a bit between those two ESR versions. We should check whether we need to update our font whitelist. In particular now, that we are about to switch to ESR60.https://gitlab.torproject.org/legacy/trac/-/issues/21973Fonts settings changed badly in 7.0a3 on Win 72020-06-15T23:43:01ZcypherpunksFonts settings changed badly in 7.0a3 on Win 7Fonts look blurry in Browser Console, something is wrong or is this a new feature?
Security Settings text becomes scrollable when set to High.Fonts look blurry in Browser Console, something is wrong or is this a new feature?
Security Settings text becomes scrollable when set to High.https://gitlab.torproject.org/legacy/trac/-/issues/21385Ensure fonts are always loaded in the same order2020-06-15T23:40:55ZArthur EdelsteinEnsure fonts are always loaded in the same orderWe bundle fonts with Linux Tor Browser, but I recall noticing that the bundled fonts are used with different priorities on different Linux flavors, such that a given code point is displayed with Font 1 on Linux flavor A and Font 2 on Lin...We bundle fonts with Linux Tor Browser, but I recall noticing that the bundled fonts are used with different priorities on different Linux flavors, such that a given code point is displayed with Font 1 on Linux flavor A and Font 2 on Linux flavor B. This probably has to do with the order of font loading being different.
Currently we use a workaround in 000-tor-browser.js, where we enforce priorities useing the font.name* prefs. But we should investigate the underlying reason for this problem and come up with a better patch that ensures our whitelisted fonts are always applied in the same order. That way a given code point will always use the same font.https://gitlab.torproject.org/legacy/trac/-/issues/20842Proposal: Improve Tor Browser font whitelist / bundled fonts2022-07-22T21:41:20ZArthur EdelsteinProposal: Improve Tor Browser font whitelist / bundled fonts**Background:**
In #13313 we introduced a new font whitelisting mechanism. Tor Browser only allows certain fonts to be used in the browser, in order to prevent bad people from trying to identify you by detecting what fonts are installed...**Background:**
In #13313 we introduced a new font whitelisting mechanism. Tor Browser only allows certain fonts to be used in the browser, in order to prevent bad people from trying to identify you by detecting what fonts are installed on your computer. Font whitelisting is also available in Firefox, off by default. (The whitelisting is controlled by a pref, "font.system.whitelist", which contains a comma-separated list of allowed font names. You can edit this pref by opening a tab and browsing to `about:config`.)
On Window and Mac, we mostly whitelist certain system fonts that are bundled with the operating system by default. We bundle a few [Google Noto fonts](https://www.google.com/get/noto/) as well for languages that don't have a built-in platform font.
On Linux, we bundle a large number of Google Noto fonts, plus Arimo, Cousine, and Tinos. We don't expose any system fonts, because these aren't consistent across Linux flavors.
My strategy for choosing fonts for the whitelist was to try to cover all possible languages with at least one font, and get the work done as efficiently as possible. I whitelisted Mac and Windows fonts that have been available for a long time and should be on essentially all systems. Bundling fonts from the Noto collection was a quick and dirty method for covering any missing fonts for different languages.
But there are probably more appealing fonts for some languages that we could use, especially on Linux. For example, in #20820 we are considering switching Linux from Noto Japanese to mona.ttf because the latter looks better (according to Yawning) and because mona.ttf can be used in the ancient Japanese art of ascii calligraphy. I also heard from someone who knows that the Tamil font on Windows is not too beautiful.
**Proposed project:**
So it would be a useful project to go through each of the fonts on each platform and see if there are better fonts that could be used instead. Important considerations would include:
* Aesthetics
* Character coverage
* Printability
* Font licensing
* Font file size
This would require asking the opinions of native speakers of various languages.
Ideally, we could come up with a new font whitelist and bundling list for Mac, Windows and Linux, where the fonts are beautiful and users are happy.https://gitlab.torproject.org/legacy/trac/-/issues/20820Add font support for Shift-JIS2020-06-15T23:39:46ZcypherpunksAdd font support for Shift-JISBack with Tor Browser 5, I was able to install monafont on my computer and it would allow Shift-JIS fonts to render properly. Because Tor Browser now uses its own built-in fonts to make fingerprinting of system fonts harder, and because ...Back with Tor Browser 5, I was able to install monafont on my computer and it would allow Shift-JIS fonts to render properly. Because Tor Browser now uses its own built-in fonts to make fingerprinting of system fonts harder, and because there are no SJIS fonts, I can't correctly view any of it. SJIS is extremely sensitive to spacing, so an alternative font which renders the characters but does not render the spacing correctly does not work at all.
SJIS is used extensively on Japanese websites.
Look at https://ja.wikipedia.org/wiki/モナー (or https://ja.wikipedia.org/wiki/%E3%83%A2%E3%83%8A%E3%83%BC if the browser isn't displaying Japanese. Many Japanese characters do not display at all) and see if the examples it displays in SJIS are anything like the image which it displays on the right.
I have not tested on Windows, only Linux.https://gitlab.torproject.org/legacy/trac/-/issues/18297Tor browser uses Chinese-style glyphs to display Japanese2020-06-15T23:33:17ZcypherpunksTor browser uses Chinese-style glyphs to display JapaneseIn Tor browser 5.5.1 version (en_US), if I visit https://en.wikipedia.org/wiki/Han_unification#Examples_of_language-dependent_glyphs the browser correctly shows Japanese-style glyph variants in the ja column.
However, on most actual Jap...In Tor browser 5.5.1 version (en_US), if I visit https://en.wikipedia.org/wiki/Han_unification#Examples_of_language-dependent_glyphs the browser correctly shows Japanese-style glyph variants in the ja column.
However, on most actual Japanese web pages, Chinese-style glyphs end up being used. This happens even if I select "Japanese" in the View->Character Encoding menu (I know that character encoding and glyph variant are two separate things, but a Japan-specific character encoding should be taken as an indicator that Japanese glyph variants should be used).
For example example, if I search for the characters from the Wikipedia table on this page - http://www.aozora.gr.jp/cards/001779/files/56648_58207.html - in every instance the simplified Chinese variant is used instead of the Japanese glyph.https://gitlab.torproject.org/legacy/trac/-/issues/18234Font fingerprinting defenses broken on Windows2020-06-15T23:33:03ZcypherpunksFont fingerprinting defenses broken on WindowsAny adjustment to Cleartype settings changes the TBB font rendering. This applies to both enabling/disabling Cleartype as well as Cleartype tuning.
(Tested on Win 7.)Any adjustment to Cleartype settings changes the TBB font rendering. This applies to both enabling/disabling Cleartype as well as Cleartype tuning.
(Tested on Win 7.)https://gitlab.torproject.org/legacy/trac/-/issues/18205Restrict font whitelist patch to apply only to non-chrome contexts?2020-06-15T23:32:58ZArthur EdelsteinRestrict font whitelist patch to apply only to non-chrome contexts?We have run into a number of difficulties where Tor-Browser's whitelist is preventing the browser's non-content UI (aka chrome) from rendering properly. It would be better if we could only apply the whitelist to content.We have run into a number of difficulties where Tor-Browser's whitelist is preventing the browser's non-content UI (aka chrome) from rendering properly. It would be better if we could only apply the whitelist to content.https://gitlab.torproject.org/legacy/trac/-/issues/18172Emoji support is broken in Tor Browser 5.52020-06-16T01:07:21ZGeorg KoppenEmoji support is broken in Tor Browser 5.5It seems our font fingerprinting defense breaks emoji support: https://blog.torproject.org/blog/tor-browser-55-released#comment-153807. See comment:10:ticket:17270 for one example.It seems our font fingerprinting defense breaks emoji support: https://blog.torproject.org/blog/tor-browser-55-released#comment-153807. See comment:10:ticket:17270 for one example.https://gitlab.torproject.org/legacy/trac/-/issues/18169Tor Browser 5.5 misses whitelisted zh-CN UI font2020-06-15T23:32:45ZGeorg KoppenTor Browser 5.5 misses whitelisted zh-CN UI fontIt seems we missed a default UI font for Chinese users. See https://blog.torproject.org/blog/tor-browser-55-released#comment-153757It seems we missed a default UI font for Chinese users. See https://blog.torproject.org/blog/tor-browser-55-released#comment-153757Arthur EdelsteinArthur Edelsteinhttps://gitlab.torproject.org/legacy/trac/-/issues/17999Changed default GUI font might help fingerprinting JA Windows users2020-06-16T00:42:42ZGeorg KoppenChanged default GUI font might help fingerprinting JA Windows usersAs yawning noted in #17550 the default GUI font changed across Windows versions:
* Windows XP -> `MS UI Gothic` (Not sure if this needs to be localized, don't have a box with this)
* Windows Vista/7 -> `メイリオ`
* Windows 8/8.1 -> `Meir...As yawning noted in #17550 the default GUI font changed across Windows versions:
* Windows XP -> `MS UI Gothic` (Not sure if this needs to be localized, don't have a box with this)
* Windows Vista/7 -> `メイリオ`
* Windows 8/8.1 -> `Meiryo UI`
* Windows 10 -> `Yu Gothic UI`
This might aid in fingerprinting JA users which are on Windows.https://gitlab.torproject.org/legacy/trac/-/issues/17785Unit tests for font whitelisting patch2020-06-15T23:31:44ZArthur EdelsteinUnit tests for font whitelisting patchWe need unit tests for the font whitelisting patch (#13313).We need unit tests for the font whitelisting patch (#13313).