- 25 Apr, 2022 2 commits
- 08 Apr, 2022 1 commit
-
- 06 Apr, 2022 1 commit
-
-
Richard Pospesel authored
-
- 31 Mar, 2022 2 commits
-
-
In our Firefox patch set we have a test that assures that preferences are kept in memory, instead of saving them to the disk or other storage. However, usually we check this kind of functionality here, not on the Firefox/tor-browser code. Other tests in that tor-browser commit should already be covered.
-
Added a test to check that fingerprinting can only detect the fonts we bundle with Tor Browser. The code is readapted from TorZilla Print: https://arkenfox.github.io/TZP/tests/fontlists.html The list should be updated to match the bundled fonts. Also, we ship different fonts in different platforms, so the test is enabled only for Linux. Added also a test to detect which glyph the browser can render and their size. The code was originally developed by David Fifield and Serge Egelman: https://www.bamsoftware.com/talks/fc15-fontfp/fontfp.html#demo The expected result of the test comes directly from a run on Tor Browser, and we want it to be persistent, rather than having some deisred metrics to match.
-
- 10 Mar, 2022 1 commit
-
-
Georg Koppen authored
We remove anything related to gk while doing so. It should not be needed anymore. Closes: #40039.
-
- 17 Jan, 2022 1 commit
-
-
Pier Angelo Vendrame authored
-
- 10 Jan, 2022 1 commit
-
-
Pier Angelo Vendrame authored
The bridge test was not ending, because the bridge specified in the configuration was down. With this new bridge, the test passed as expected.
-
- 07 Jan, 2022 1 commit
-
-
Piero V authored
Canged fp_navigator and fp_useragent to test with the correct version. The screen dimensions test was failing because letterboxing is disabled on about:pages (I checked with Richard, and this is the indended behavior). Therefore, the test is now run on a TPO page, and it passes. Updated the settings test, to check for new settings (see tor-browser!215), and not to check anymore for deprecated and removed settings (see tor-browser#40177). As a result of these settings changes, some DOM objects are now exposed: * pointer events * gamepads * applicationCache * visualViewport However, Tor Browser already contains mitigatins against their use for fingerprinting (e.g., gamepads do not work, Mozilla added some protections to pointer events for Bugzilla#1363508, letterboxing should prevent fingerprinting on visualViewport, cache storage is 0 bytes, etc...). Some other DOM objects are just new (e.g., clientInformation). Finally, HTTPS everywhere test failed because no...
-
- 13 Aug, 2021 3 commits
-
-
Matthew Finkel authored
-
Matthew Finkel authored
-
Matthew Finkel authored
-
- 17 May, 2021 1 commit
-
-
boklm authored
-
- 19 Feb, 2021 3 commits
- 16 Feb, 2021 1 commit
-
-
boklm authored
-
- 26 Jan, 2021 1 commit
-
-
Alex Catarineu authored
-
- 21 Jan, 2021 1 commit
-
-
Georg Koppen authored
-
- 20 Jan, 2021 1 commit
-
-
Alex Catarineu authored
This should be closer to how it's done by tor-launcher and should help us catch issues like tor-browser#40282.
-
- 11 Dec, 2020 1 commit
-
-
Alex Catarineu authored
-
- 03 Dec, 2020 1 commit
-
-
Alex Catarineu authored
window.content is disabled in early betas since 77.
-
- 25 Nov, 2020 1 commit
-
-
Alex Catarineu authored
-
- 23 Oct, 2020 2 commits
-
-
Alex Catarineu authored
-
Alex Catarineu authored
-
- 15 Oct, 2020 14 commits
-
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-
Alex Catarineu authored
-