[tor-commits] [tor-browser-spec/master] Update with most of the fingerprinting changes.
mikeperry at torproject.org
mikeperry at torproject.org
Tue Oct 28 01:51:02 UTC 2014
Author: Mike Perry <mikeperry-git at torproject.org>
Date: Mon Oct 27 18:50:34 2014 -0700
Update with most of the fingerprinting changes.
More work still remains.
design-doc/design.xml | 220 ++++++++++++++++++++++++++++++++++++-------------
1 file changed, 164 insertions(+), 56 deletions(-)
diff --git a/design-doc/design.xml b/design-doc/design.xml
index 8f12ae4..b469f2a 100644
@@ -1044,7 +1044,7 @@ features if they so desire.
We achieve this goal through several mechanisms. First, we set the Firefox
Private Browsing preference
@@ -1052,15 +1052,18 @@ Private Browsing preference
Private Browsing Mode is enabled. We need to
-the permissions manager from recording HTTPS STS state</ulink>,
-intermediate SSL certificates from being recorded</ulink>,
+the permissions manager from recording HTTPS STS state</ulink>, <ulink
+intermediate SSL certificates from being recorded</ulink>, <ulink
+the clipboard cache from being written to disk for large pastes</ulink>, and
-the content preferences service from recording site zoom</ulink>.
+the content preferences service from recording site zoom</ulink>. We also had
+to disable the media cache with the pref <command>media.cache_size</command>,
+to prevent HTML5 videos from being written to the OS temporary directory,
+which happened regardless of the private browsing mode setting.
@@ -1117,7 +1120,6 @@ $HOME environment variable to be the TBB extraction directory.
<title>Cross-Origin Identifier Unlinkability</title>
- <!-- FIXME: Mention web-send?? -->
The Tor Browser MUST prevent a user's activity on one site from being linked
@@ -1445,11 +1447,14 @@ determine how many bits of identifying information each attribute provided.
-Many browser features have been added since the EFF first ran their experiment
-and collected their data. To avoid an infinite sinkhole, we reduce the efforts
-for fingerprinting resistance by only concerning ourselves with reducing the
-fingerprintable differences <emphasis>among</emphasis> Tor Browser users. We
-do not believe it is possible to solve cross-browser fingerprinting issues.
+Because fingerprinting is problem that potentially touches every aspect of the
+browser, we reduce the efforts for fingerprinting resistance by only
+concerning ourselves with reducing the fingerprintable differences
+<emphasis>among</emphasis> Tor Browser users. We do not believe it is possible
+to solve cross-browser fingerprinting issues. Similarly, we prioritize issues
+that differentiate only MacOS, Windows, and Linux lower than those that
+differentiate aspects of the hardware, third party installed software, and
+configuration differences in those operating systems.
@@ -1470,7 +1475,6 @@ Panopticlick to allow us to run our own version for this reason.
<title>Fingerprinting defenses in the Tor Browser</title>
@@ -1488,7 +1492,9 @@ barrier. Additionally, version information should be reduced or obfuscated
until the plugin object is loaded. For flash, we wish to <ulink
settings.sol file</ulink> to disable Flash cookies, and to restrict P2P
-features that are likely to bypass proxy settings.
+features that are likely to bypass proxy settings. We'd also like to restrict
+access to fonts and other system information (such as IP address and MAC
+address) in such a sandbox.
@@ -1526,13 +1532,54 @@ image can be used almost identically to a tracking cookie by the web server.
To reduce the threat from this vector, we have patched Firefox to <ulink
-before returning valid image data</ulink> to the Canvas APIs. If the user
-hasn't previously allowed the site in the URL bar to access Canvas image data,
+before returning valid image data</ulink> to the Canvas APIs, and for <ulink
+to isPointInPath and related functions</ulink>. If the user hasn't previously
+allowed the site in the URL bar to access Canvas image data, pure white image
+ <listitem>Open Local Port Fingerprinting
+In Firefox, by using either WebSockets or XHR, it is possible for remote
+content to <ulink url="http://www.andlabs.org/tools/jsrecon.html">enumerate
+the list of TCP ports open on 127.0.0.1</ulink>. In other browsers, this can
+be accomplished by DOM events on image tags. This open vs filtered vs closed
+port list can provide a very unique fingerprint of a machine.
+ <para><command>Implementation Status:</command> We prevent access to
+127.0.0.1/localhost by ensuring that even these requests are still sent by
+Firefox to our SOCKS proxy (ie we set
+<command>network.proxy.no_proxies_on</command> to the empty string). The local
+Tor client then rejects them, since it is configured to proxy for internal IP
+addresses by default.
+ <listitem>USB Device ID enumeration
+The GamePad API <ulink
+web pages with the USB device id, product id, and driver name</ulink> of all
+connected game controllers, as well as detailed information about their
+capabilities. This API should be behind a site permission in Private Browsing
+Modes. We simply disable it via the pref
+ <listitem>Invasive Authentication Mechanisms (NTLM and SPNEGO)
+Both NTLM and SPNEGO authentication mechansisms can leak the hostname, and in
+some cases the machine username. These authentication mechanisms should either
+be disabled, or placed behind a site permission before their use. We simply
@@ -1575,24 +1622,25 @@ font for every language, typeface, and style in use in the world, and to only
use those fonts at the exclusion of system fonts. However, this set may be
impractically large. It is possible that a smaller <ulink
-subset</ulink> may be found that provides total coverage. However, we believe
-that with strong url bar origin identifier isolation, a simpler approach can reduce the
-number of bits available to the adversary while avoiding the rendering and
-language issues of supporting a global font set.
+subset</ulink> may be found that provides total coverage. Right now, it
+appears that the major languages on Wikipedia can be supported for about 3MB
+of additional distribution size, using the DejaVu font set.
-We disable plugins, which prevents font enumeration. Additionally, we limit
-both the number of font queries from CSS, as well as the total number of
-fonts that can be used in a document <ulink
+In the meantime while we investigate shipping our own fonts, we disable
+plugins, which prevents font enumeration. Additionally, we limit both the
+number of font queries from CSS, as well as the total number of fonts that can
+be used in a document <ulink
a Firefox patch</ulink>. We create two prefs,
<command>browser.display.max_font_count</command> for this purpose. Once these
limits are reached, the browser behaves as if
-<command>browser.display.use_document_fonts</command> was set. We are
-still working to determine optimal values for these prefs.
+<command>browser.display.use_document_fonts</command> was set. We are still
+working to determine optimal values for these prefs.
@@ -1604,52 +1652,81 @@ font (in any order), we use that font instead of any of the named local fonts.
- <listitem>Desktop resolution, CSS Media Queries, and System Colors
+ <listitem>Monitor and Desktop resolution
resolution, usable desktop size, OS widget size, toolbar size, title bar size,
-system theme colors, and other desktop features that are not at all relevant
+screen orientation, and other desktop features that are not at all relevant
to rendering and serve only to provide information for fingerprinting.
Our design goal here is to reduce the resolution information down to the bare
-minimum required for properly rendering inside a content window. We intend to
+minimum required for properly rendering inside a content window. We intend to
report all rendering information correctly with respect to the size and
properties of the content window, but report an effective size of 0 for all
-border material, and also report that the desktop is only as big as the
-inner content window. Additionally, new browser windows are sized such that
-their content windows are one of a few fixed sizes based on the user's
+border material, and also report that the desktop is only as big as the inner
+content window. Additionally, new browser windows are sized such that their
+content windows are one of a few fixed sizes based on the user's desktop
+resolution. The user should also be informed that maximizing their windows can
+lead to fingerprintability under this scheme. To further reduce
+resolution-based fingerprinting, we are <ulink
+zoom/viewport-based mechanisms</ulink> that might allow us to always report
+the same desktop resolution regardless of the actual size of the content
+window, and simply scale to make up the difference.
We have implemented the above strategy using a window observer to <ulink
new windows based on desktop resolution</ulink>. Additionally, we patch
Firefox to use the client content window size <ulink
-window.screen</ulink> and <ulink
-CSS Media Queries</ulink>. Similarly, we <ulink
-DOM events to return content window relative points</ulink>. We also patch
-Firefox to <ulink
-a fixed set of system colors to content window CSS</ulink>.
+window.screen</ulink>. Similarly, we <ulink
+DOM events to return content window relative points</ulink>. We also force
+popups to open in new tabs (via
+<command>browser.link.open_newwindow.restriction</command>), to avoid
+full-screen popups inferring information about the browser resolution. In
+addition, we prevent auto-maximizing on browser start, and are investigating a
+user-friendly way of informing users that maximized windows are deterimental
+to privacy in this mode.
+ <listitem>CSS Media Queries
-To further reduce resolution-based fingerprinting, we are <ulink
-zoom/viewport-based mechanisms</ulink> that might allow us to always report
-the same desktop resolution regardless of the actual size of the content
-window, and simply scale to make up the difference. However, the complexity
-and rendering impact of such a change is not yet known.
+resolution, usable desktop size, OS widget size, toolbar size, title bar size,
+system theme colors, and other desktop features that are not at all relevant
+to rendering and serve only to provide information for fingerprinting.
+ <para><command>Design Goal:</command>
+<!-- XXX: Link to CSS spec for this stuff -->
+In Private Browsing Mode, CSS should not be able infer anything that the user
+has configured about their computer. Additionally, it should not be able to
+infer machine-specific details such as screen orientation or type.
+ <para><command>Implementation Status:</command>
+Firefox to <ulink
+a fixed set of system colors to content window CSS</ulink>, and <ulink
+detection of font smoothing on OSX</ulink>. We also always
+landscape-primary</ulink> for the screen orientation.
@@ -1674,6 +1751,11 @@ url="http://pseudo-flaw.net/tor/torbutton/fingerprint-firefox.html">can be
used</ulink> to fingerprint OS, platform, and Firefox minor version. </para>
+ <listitem>Locale Fingerprinting
+XXX: 2. bug 10703: force the default charset to avoid locale fingerprinting
<listitem>Timezone and clock offset
@@ -1696,6 +1778,29 @@ use.
+ <listitem>Timezone and Clock skew fingerprinting
+While the latency in Tor connections varies anywhere from milliseconds to
+several seconds, it is still possible for the remote site to detect large
+differences between the user's clock and an official reference timesource.
+ <para><command>Design Goal:</command> Ideally, the browser would be
+able to correct the source of this clock drift using an external time source,
+either through something like tlsdate, or directly through the Tor protocol.
+Additionally, the timezone should be set to UTC.
+ <para><command>Implementation Status:</command>
+Right now, we currently set the timezone to UTC via the
+<command>TZ</command> environment variable, and randomize the TLS Hello
+timestamp. However, we have not yet integrated tlsdate or an external
@@ -1724,6 +1829,8 @@ optimum trade-off between quantization+jitter and amortization time.
+<!-- XXX: Disabled network performance timers too -->
Currently, the only mitigation against performance fingerprinting is to
disable <ulink url="http://www.w3.org/TR/navigation-timing/">Navigation
Timing</ulink> through the Firefox preference
@@ -1790,7 +1897,7 @@ All linkable identifiers and browser state MUST be cleared by this feature.
@@ -1814,8 +1921,9 @@ url="https://developer.mozilla.org/en-US/docs/Supporting_private_browsing_mode#P
state), and then manually clear the following state: searchbox and findbox
text, HTTP auth, SSL state, OCSP state, site-specific content preferences
(including HSTS state), content and image cache, offline cache, Cookies, DOM
-storage, DOM local storage, the safe browsing key, and the Google wifi geolocation
-token (if it exists).
+storage, crypto tokens, DOM local storage, the safe browsing key, and the
+Google wifi geolocation token (if it exists). We also clear NoScript's site
+and temporary permissions.
More information about the tor-commits