[tor-reports] October 2014 Report for the Tor Browser Team
mikeperry at torproject.org
Tue Nov 4 07:53:47 UTC 2014
In October, the Tor Browser team made two releases: 4.0, and 4.0.1[1,2].
The 4.0 release marked the stabilization of our 4.0-alpha series, as
well as the transition to Firefox 31ESR. The new UI is quite a bit more
streamlined than the old Tor Browser, owing to Firefox's new Australis
layout, as well as our improved ability to customize this layout. The
release also featured fingerprinting fixes and
improvements[4,5,6,7,8,9], defense-in-depth checks for proxy safety,
and disabled SSLv3 to prevent the POODLE attack. We were also able
to enable WebGL on Windows in this release (though it is still
click-to-play via NoScript). The full set of tickets that went into this
Firefox 31 rebase can be found using the ff31-esr tag in our bug
tracker. Full changelogs for the 4.0 series are also on the blog
However, this transition was a little bumpier than we would have liked.
In particular, a Windows crash bug due to our Windows cross-compiler
caused us to have to release 4.0.1 shortly afterwords.
We also updated the Tor Browser design document to cover the 4.0
series, describe our build reproducibility enhancements, and update
the list of fingerprinting attacks and defenses. We've also
discussed private browsing mode standardization with some members of
the W3C, and will be sending interested W3C people the updated design
The remainder of the month was spent preparing 4.5-alpha-1, which
unfortunately only just barely didn't make it out in October. For this
release, we deployed SOCKS username and password support to isolate all
requests for a url bar domain on the same Tor circuit, implemented a
browser UI for displaying the current circuit and exit IP address,
implemented the Security Slider, backported HTTPS certificate pinning
support, switched to 64 bit builds for Mac OS X, integrated the
new obs4proxy pluggable transport, added (reproducible) incremental
update support to reduce update download size (from ~40M down to
2M), fixed an updater issue with our extension compatibility
checks, and fixed a locale fingerprinting issue.
We also performed an experiment to test Mozilla Persona, to
determine if we could easily adapt it to serve as a mechanism to
anonymously prove that users had completed a captcha or some other
proof-of-scarcity. Unfortunately, it seems as though Mozilla has left
the system in a rather unusable state for us. In an attempt to drive
adoption, they made two implementations: A "legacy" version using
version using code in Firefox. Unfortunately, the so-called legacy
non-Firefox implementation appears to be incompatible with the native
implementation, at least to the point where all sites that currently use
Persona would have to upgrade to new code written by us, as well as new
user-facing behavior. In short, if we were to try to make use of
Persona, we'd have to choose either compatibility or privacy, and could
not have both. This (coupled with the recent "community support" status
of Persona) has led us to conclude that we would be better off
pursuing other options.
The full list of tickets closed by the Tor Browser team in October can
be seen using the TorBrowserTeam201410 tag on our bug tracker.
In November, we will focus on stabilizing 4.5-alpha, work on supporting
per-file signatures on our updates, work on fixing remaining bugs
with our updater[32,33,34], and will continue updating all of our
patches and adding unit tests in the Mozilla bug tracker. We also
hope to set up an auto-rebased branch for use with the official Mozilla
testing infrastructure, to help ensure our patches continue to pass unit
tests and to avoid surprise conflicts and regressions.
The full list of tickets that the Tor Browser team plans to work on in
November can be seen using the TorBrowserTeam201411 tag on our
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: Digital signature
More information about the tor-reports