- Nov 27, 2024
- Aug 24, 2024
-
-
morgan authored
- removed richard - added bea, clairehurst, jwilde, and morgan
-
- Jul 10, 2024
-
-
Richard Pospesel authored
Bug 40078: Update tools/tb-build-06-start-nightly-build to archive binaries after tor-browser-build#40829
-
- Dec 08, 2023
-
-
boklm authored
-
- Dec 07, 2023
-
-
We enabled base browser builds before Mullvad Browser was completely created. But now Mullvad Browser has some code paths that are not tested in Base Browser, therefore it makes more sense to build MB instead of BB.
-
- Jul 05, 2023
- Jun 28, 2023
-
-
boklm authored
-
- Mar 20, 2023
-
-
boklm authored
-
- Feb 08, 2023
-
- Feb 01, 2023
-
-
boklm authored
With tor-browser-build#40737 the nightly/ directory is now prefixed with the $projectname, and with tor-browser-build#40742 the makefile rule to generate the incrementals is now $projectname-incrementals-nightly.
-
- Jan 13, 2023
-
-
boklm authored
-
- Nov 17, 2022
-
-
boklm authored
Following tor-browser-build#40439 and tor-browser-build#40067, the rbm target to build for macos was changed. At the same time we also change the name and directory of the macos builds, using `macos` instead of `osx-x86_64`.
-
- Nov 10, 2022
-
-
boklm authored
Since we now have multi-locale builds, keeping old builds uses less space. We are also not currently doing builds every day since building takes more than one day. So I think we can increase the number of days of builds we keep (previously only one).
-
boklm authored
Archive the `ALL` bundles instead of `en-US`, since we now do multi-locale bundles. We also archive base-browser builds.
-
boklm authored
With tor-browser-build#40501, the name of the targets changed. We also add the base-browser builds there.
- Oct 06, 2022
-
-
boklm authored
-
- Aug 24, 2022
-
-
boklm authored
-
- Jul 15, 2022
- Jul 14, 2022
-
-
boklm authored
-
- Apr 25, 2022
- Apr 08, 2022
-
- Apr 06, 2022
-
-
Richard Pospesel authored
-
- Mar 31, 2022
-
-
Pier Angelo Vendrame authored
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.
-
Pier Angelo Vendrame authored
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.
-
- Mar 10, 2022
-
-
Georg Koppen authored
We remove anything related to gk while doing so. It should not be needed anymore. Closes: #40039.
-
- Jan 17, 2022
-
-
Pier Angelo Vendrame authored
-
- Jan 10, 2022
-
-
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.
-
- Jan 07, 2022
-
-
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 now Firefox redirects to HTTPS if available, even when HTTPS-Only Mode is not enabled. To detect if HTTPS everywhere is actually the responsible of the redirect, we need to run it with dom.security.https_first_pbm set to false.
-
- Aug 13, 2021
-
-
Matthew Finkel authored
-
Matthew Finkel authored
-
Matthew Finkel authored
-
- May 17, 2021
-
-
boklm authored
-
- Feb 19, 2021