[tor-reports] January 2014 Report for the Tor Browser Team
mikeperry at torproject.org
Sat Feb 1 20:52:58 UTC 2014
In January, we released TBB 3.5.1, which enabled screen readers for the
blind, added Arabic bundles to the 3.x series, and provided updated
versions for several components of the bundle.
Several additional fixes are also ready for inclusion in the next
release of the bundle after 3.5.1, though Mozilla has also recently
tagged a new Firefox 24ESR release (out of phase with their normal 6
week schedule, due to the holidays), so we may delay merging non-serious
issues until the release after that.
The fixes that are ready for review and merge include improvements in
browser fingerprinting defenses via screen resolution[1,2], default
character sets, site permissions, and local service
enumeration. A few security fixes are also ready, including disabling
addon update requests for addons that should not update, a potential
fix for a disk leak in the browser's video cache, a fix for two
localization issues with Tor Launcher[8,9], and a potential fix to
prevent the Flash plugin from being loaded into the browser at all until
the user actually requests to use it (rather than loading the plugin,
but setting it disabled).
Partial progress has also been made on a number of fronts, most notable
is the work on unifying the pluggable transport bundles with the
official bundles, so that both censored and uncensored users can use
the same bundles. UI support for configuring pluggable transports has
also progressed. The progress is sufficient that we are very likely
to be able to deploy a 3.6-beta1 release in February to test these
unified bundles. Soon after that, if all goes well, we will declare the
3.6 series the new stable, so that all users will be using the same
Progress has also been made on code hardening on Windows (ASLR and DEP
support). Discussions and initial patches for improvements to the
usability of the "New Identity" button are also underway.
On the organizational side, we have reviewed resumes and began
contacting candidates who applied to the browser developer positions
that we posted in December. We're also working on streamlining our
release process, and documenting it to the point where release duties
can be rotated through the team.
We have also continued the merge process with Mozilla, and have worked
to ensure that every patch of ours is on their radar (through a shared
Google spreadsheet with the Privacy Tech Lead). Two patches, one for an
API we require to manage the Tor subprocess, and another to give us
a filter to remove potentially dangerous drag-and-drop events to the
desktop have already been merged. Next steps will include filing
more bugs, continual contact with their development team, and touching
up patches as needed.
In February, we will make at least one, but possibly two or even three
releases of the TBB: 3.5.2, 3.6-beta1, and possibly also 3.5.3. We hope
to use these releases to dial in the process for rotating release
Respectively, these three releases will contain the Mozilla Firefox
security update; unified pluggable transports; and the fixes mentioned
above that have been developed in January.
Along with our existing semi-weekly meetings with Mozilla, we will also
be holding weekly meetings with the HTTPS-Everywhere developers at the
EFF. Specifically, we will be investigating and designing improvements
to the HTTPS-Everywhere SSL Observatory, to work towards the ability to
turn the SSL Observatory on in TBB, and to improve the user notification
if SSL tampering is detected.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: Digital signature
More information about the tor-reports