Roger Dingledine commited on 2010-09-22 03:47:56
Zeige 1 geänderte Dateien mit 54 Einfügungen und 3 Löschungen.
... | ... |
@@ -43,9 +43,14 @@ have a virus or spyware?</a></li> |
43 | 43 |
|
44 | 44 |
<p>Running a Tor client:</p> |
45 | 45 |
<ul> |
46 |
-<li><a href="#DoesntWork">I installed Tor and Polipo but it's not working.</a></li> |
|
47 |
-<li><a href="#VidaliaPassword">Tor/Vidalia prompts for a password at start.</a></li> |
|
48 |
-<li><a href="#ChooseEntryExit">Can I control which nodes (or country) are used for entry/exit?</a></li> |
|
46 |
+<li><a href="#DoesntWork">I installed Tor and Polipo but it's not |
|
47 |
+working.</a></li> |
|
48 |
+<li><a href="#VidaliaPassword">Tor/Vidalia prompts for a password at |
|
49 |
+start.</a></li> |
|
50 |
+<li><a href="#ChooseEntryExit">Can I control which nodes (or country) |
|
51 |
+are used for entry/exit?</a></li> |
|
52 |
+<li><a href="#GoogleCaptcha">Google makes me solve a Captcha or tells |
|
53 |
+me I have spyware installed.</a></li> |
|
49 | 54 |
</ul> |
50 | 55 |
|
51 | 56 |
<p>Running a Tor relay:</p> |
... | ... |
@@ -908,6 +913,52 @@ See the manual page for details. |
908 | 913 |
|
909 | 914 |
<hr /> |
910 | 915 |
|
916 |
+<a id="GoogleCaptcha"></a> |
|
917 |
+<h3><a class="anchor" href="#GoogleCaptcha">Google makes me solve a |
|
918 |
+Captcha or tells me I have spyware installed.</a></h3> |
|
919 |
+ |
|
920 |
+<p> |
|
921 |
+This is a known and intermittent problem; it does not mean that Google |
|
922 |
+considers Tor to be spyware. Instead, Google tries to detect certain |
|
923 |
+kinds of spyware or viruses that send distinctive queries to Google |
|
924 |
+Search. It then notes the IP addresses from which those queries are |
|
925 |
+received, and tries to warn the users of those IP addresses that it |
|
926 |
+received queries indicating an infection. |
|
927 |
+</p> |
|
928 |
+ |
|
929 |
+<p> |
|
930 |
+When you use Tor, you are sending queries through exit nodes that are also |
|
931 |
+shared by thousands of other users. If some of those users are infected |
|
932 |
+with software that Google detects, Google may mistakenly conclude that |
|
933 |
+the exit nodes themselves are infected (because the requests appeared |
|
934 |
+to originate from the exit nodes) and, for a limited period of time, |
|
935 |
+will try (incorrectly) to warn all Google users who share an exit node |
|
936 |
+with an infected machine that they are themselves infected. |
|
937 |
+</p> |
|
938 |
+ |
|
939 |
+<p> |
|
940 |
+You may also get this sort of message when lots of Tor users are querying |
|
941 |
+Google in a short period of time. Google interprets the high volume of |
|
942 |
+traffic as somebody trying to "crawl" their website, so it slows down |
|
943 |
+traffic from that IP address for a short time. |
|
944 |
+</p> |
|
945 |
+ |
|
946 |
+<p> |
|
947 |
+To our knowledge, Google is not doing anything intentionally specifically |
|
948 |
+to deter or block Tor use. The error message about an infected machine |
|
949 |
+should clear up again after a short time. |
|
950 |
+</p> |
|
951 |
+ |
|
952 |
+<p> |
|
953 |
+If we think of a measure that would prevent users from seeing this sort of |
|
954 |
+spurious warning message, we will certainly suggest it to Google and to |
|
955 |
+other web site developers. There may also be technical workarounds for |
|
956 |
+Tor end-users affected by this problem; if you find a useful workaround |
|
957 |
+and write up a description of it, please let us know. |
|
958 |
+</p> |
|
959 |
+ |
|
960 |
+<hr /> |
|
961 |
+ |
|
911 | 962 |
<a id="RelayFlexible"></a> |
912 | 963 |
<h3><a class="anchor" href="#RelayFlexible">How stable does my relay |
913 | 964 |
need to be?</a></h3> |
914 | 965 |