Hi all!
In June the Tor Browser team made 3 releases, Tor Browser 7.0[1], Tor Browser 7.0.1[2], and Tor Browser 7.5a1[3], switching Tor Browser users to an up-to-date Firefox 52 ESR version.
Major new features coming with the switch to Firefox 52 ESR are Firefox's multiprocess mode and in-browser sandboxing. Unfortunately, the long awaited content sandboxing did not make it into the ESR 52 series due to stability issues but we are trying to backport the necessary patches for Tor Browser 7. We'll start with Tor Browser for Linux[4] but hope to do the same for macOS as well if there are different patches needed. For Windows users work on basic sandboxing support was and is ongoing, too.[5]
The alpha release is almost identical to Tor Browser 7.0.1 with the notable exception of testing a fix for a vulnerability found in Firefox on Windows systems.[6] It got already upstreamed and all Tor Browser users on Windows will get it with the next Firefox update.[7]
Non-release related work involved fixing our test suite for the ESR 52 transition[8] and preparing the launch of our own FP Central instance + using its results for our Q&A.[9]
The full list of tickets closed by the Tor Browser team in June is accessible using the `TorBrowserTeam201706` keyword in our bug tracker.[10]
In June we already started with addressing regressions coming with our switch to Firefox ESR 52 and plan to continue with that work in July. Interested parties can track the progress in our bug tracker following tickets with the `tbb-7.0-issues, tbb-regression` keywords.[11] Furthermore, we hope to work on some of the remaining `tbb-7.0-must` issues.[12] Finally, rbm nightly builds and making use of our own Panopticlick (a.k.a FP Central) instance is on our agenda for July as well.
All tickets on our radar for this month can be seen with the `TorBrowserTeam201707` keyword in our bug tracker.[13]
Georg
[1] https://blog.torproject.org/blog/tor-browser-70-released [2] https://blog.torproject.org/blog/tor-browser-701-released [3] https://blog.torproject.org/blog/tor-browser-75a1-released [4] https://trac.torproject.org/projects/tor/ticket/22692 [5] https://trac.torproject.org/projects/tor/ticket/16010 [6] https://trac.torproject.org/projects/tor/ticket/21617 [7] https://hg.mozilla.org/releases/mozilla-esr52/rev/012e4429ccd9 [8] https://trac.torproject.org/projects/tor/ticket/21982 [9] https://trac.torproject.org/projects/tor/ticket/22587 [10] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~T... [11] https://trac.torproject.org/projects/tor/query?status=accepted&status=as... [12] https://trac.torproject.org/projects/tor/query?status=accepted&status=as... [13] https://trac.torproject.org/projects/tor/query?keywords=~TorBrowserTeam20170...
Georg Koppen:
[snip]
All tickets on our radar for this month can be seen with the `TorBrowserTeam201707` keyword in our bug tracker.[13]
FWIW, the correct footnote for that one is
[13] https://trac.torproject.org/projects/tor/query?keywords=~TorBrowserTeam20170...
Georg
[snip]
tor-project@lists.torproject.org