[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [tor-browser-spec/master] minor fixes



commit de9508298e0513287d63c6e0e1955a3ee51ae5e7
Author: Georg Koppen <gk@xxxxxxxxxxxxxx>
Date:   Wed May 6 20:11:27 2015 +0000

    minor fixes
---
 design-doc/design.xml |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/design-doc/design.xml b/design-doc/design.xml
index 58935cb..a59e610 100644
--- a/design-doc/design.xml
+++ b/design-doc/design.xml
@@ -1570,7 +1570,7 @@ is only possible to minimize the differences among different installations of
 the same browser vendor and version. We make no effort to mimic any other
 major browser vendor, and in fact most of our fingerprinting defenses serve to
 differentiate Tor Browser users from normal Firefox users. Because of this,
-any study that lumps browser vendor and version differences in to its analysis
+any study that lumps browser vendor and version differences into its analysis
 of the fingerprintability of a population is largely useless for evaluating
 either attacks or defenses. Unfortunately, this includes popular large-scale
 studies such as <ulink
@@ -1589,8 +1589,8 @@ To date, the Tor Browser team has concerned itself only with developing
 defenses for APIs that have already been standardized and deployed. Once an
 API or feature has been standardized and widely deployed, defenses to the
 associated fingerprinting issues tend to have only a few options available to
-compensate for the lack up-front privacy design. In our experience, these
-options tend to be limited to value spoofing, subsystem reimplementation,
+compensate for the lack of up-front privacy design. In our experience, these
+options are usually limited to value spoofing, subsystem reimplementation,
 virtualization, site permissions, and feature removal. We will now describe
 these options and the fingerprinting sources they tend to work best with.
 



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits