Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:40:45Zhttps://gitlab.torproject.org/legacy/trac/-/issues/18569Run Pluggable Transport tests only once2020-06-13T17:40:45ZboklmRun Pluggable Transport tests only onceWhen running the tests on Tor Browser, we run all the tests on the bundles in all the languages, which takes a lot of time.
Given that the Pluggable Transports are exactly the same for all the languages, we could run those tests only fo...When running the tests on Tor Browser, we run all the tests on the bundles in all the languages, which takes a lot of time.
Given that the Pluggable Transports are exactly the same for all the languages, we could run those tests only for one of the languages.boklmboklmhttps://gitlab.torproject.org/legacy/trac/-/issues/18557Exempt Graphite preference from Security Slider2020-06-15T23:33:57ZGeorg KoppenExempt Graphite preference from Security SliderMozilla is disabling Graphite on the releases channel for the time being. We should exempt the pref from the security slider and follow Mozilla here.Mozilla is disabling Graphite on the releases channel for the time being. We should exempt the pref from the security slider and follow Mozilla here.https://gitlab.torproject.org/legacy/trac/-/issues/18406Update Tor Browser release documentation to check for properly signed MAR files2020-06-15T23:33:43ZGeorg KoppenUpdate Tor Browser release documentation to check for properly signed MAR filesWe should update our release documentation to make sure our MAR files are signed properly before generating the update response files.We should update our release documentation to make sure our MAR files are signed properly before generating the update response files.Georg KoppenGeorg Koppenhttps://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/16686Migrate all font fingerprinting patches to tor-browser.git2020-06-15T23:27:55ZArthur EdelsteinMigrate all font fingerprinting patches to tor-browser.gitRight now, our font fingerprinting patches are divided between tor-browser.git and tor-browser-bundle.git. We'd like to move all patches to tor-browser.git.
From our discussion at ticket:13313#comment:25:
arthuredelstein:
> [We could]...Right now, our font fingerprinting patches are divided between tor-browser.git and tor-browser-bundle.git. We'd like to move all patches to tor-browser.git.
From our discussion at ticket:13313#comment:25:
arthuredelstein:
> [We could] add the Noto fonts directly to the tor-browser.git repo, and add something in the Mozilla build scripts to install them in the directory where fonts are bundled. That would avoid modifying tor-browser-bundle.git altogether.
gk:
> I think this makes sense. Another thing that bothers me with the currently proposed solution is that it makes bisecting quite error-prone. Although this is not documented yet the fastest approach is to just take an existing Tor Browser bundle and just bisect the tor-browser parts copying the result over the respective bundle parts with each iteration. This is not working anymore with having so many parts in tor-browser-bundle.git. Having everything in tor-browser could help us debug issues due to font updates easier as well.
One issue is whether we want to use hinted or unhinted Noto fonts. If some OSs are incapable of making use of hinting, then we may decide to turn off hinting on all platforms. In that case we could bundle just unhinted fonts. OTOH, hinting maybe looks nicer, and it may be difficult to prevent fingerprinting Windows vs Linux vs Mac, so it's worth thinking about the tradeoff.Arthur EdelsteinArthur Edelsteinhttps://gitlab.torproject.org/legacy/trac/-/issues/16672Text rendering allows font fingerprinting2020-06-16T00:42:42ZArthur EdelsteinText rendering allows font fingerprintingUsing dcf's font fingerprinting demo,
https://www.bamsoftware.com/talks/fc15-fontfp/fontfp.html#demo
gk [ticket:13313#comment:24 observed] that different operating systems render glyphs in the *same* font differently:
> I just tested...Using dcf's font fingerprinting demo,
https://www.bamsoftware.com/talks/fc15-fontfp/fontfp.html#demo
gk [ticket:13313#comment:24 observed] that different operating systems render glyphs in the *same* font differently:
> I just tested that on two 32bit Linux systems (one Ubuntu 12.04 and one Debian testing) and even there are differeces visible with bundled fonts (the diff is attached). I guess this means shipping the alpha with it is fine (it can't get worse wrt to the status quo :) ) but we might want to have an estimation about what the current solution really helps us for the stable series before we ship it there.
So I wonder whether it's possible to force Firefox/Tor Browser to use a cross-platform method for rendering fonts.Arthur EdelsteinArthur Edelsteinhttps://gitlab.torproject.org/legacy/trac/-/issues/16665Circuit visualizer needs a cue about guards2020-06-15T23:27:49ZLunarCircuit visualizer needs a cue about guardsOne user came to me really confused about the fact that everytime they used “New identitiy” or “New circuit for this site”, the first Tor node in the circuit was always the same. We probably should add an explanation about guards somewhe...One user came to me really confused about the fact that everytime they used “New identitiy” or “New circuit for this site”, the first Tor node in the circuit was always the same. We probably should add an explanation about guards somewhere close to the circuit visualizer.