Cleaned up some existing FAQ entries
Matt Pagan

Matt Pagan commited on 2013-12-04 11:57:57
Zeige 1 geänderte Dateien mit 28 Einfügungen und 46 Löschungen.

... ...
@@ -608,10 +608,10 @@ money to the
608 608
     <hr>
609 609
 
610 610
     <a id="FileSharing"></a>
611
-    <h3><a class="anchor" href="#FileSharing">How can I share files anonymously through Tor?"</a></h3>
611
+    <h3><a class="anchor" href="#FileSharing">How can I share files anonymously through Tor?</a></h3>
612 612
 
613 613
     <p>
614
-    File sharing (peer-to-peer/P2P) is widely unwanted in the Tor network and exit nodes are configured to block file sharing traffic by default. Tor is not really designed for it and file sharing through Tor excessively wastes everyone's bandwidth (slows down browsing). Also, Bittorrent over Tor <a href="https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea">is not anonymous</a>!
614
+    File sharing (peer-to-peer/P2P) is widely unwanted in the Tor network, and exit nodes are configured to block file sharing traffic by default. Tor is not really designed for it, and file sharing through Tor slows down everyone's browsing. Also, Bittorrent over Tor <a href="https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea">is not anonymous</a>!
615 615
     </p>
616 616
 
617 617
     <hr>
... ...
@@ -758,7 +758,7 @@ So as a client, you could probably get away with opening only those four ports.
758 758
 If you really need to connect to only a small set of ports, see the FAQ entry on firewalled ports.
759 759
     </p>
760 760
     <p>
761
-Note that if you're running as a Tor relay, you must allow outgoing connections to every other relay, and to anywhere your exit policy advertises that you allow. The cleanest way to do that is to simply allow all outgoing connections at your firewall. If you don't, clients will try to use these connections and things won't work. 
761
+Note that if you're running Tor as a relay, you must allow outgoing connections to every other relay and to anywhere your exit policy advertises that you allow. The cleanest way to do that is simply to allow all outgoing connections at your firewall. If you don't, clients will try to use these connections and things won't work. 
762 762
     </p>
763 763
     
764 764
     <hr>
... ...
@@ -770,7 +770,7 @@ Note that if you're running as a Tor relay, you must allow outgoing connections
770 770
     There are sites you can visit that will tell you if you appear to be coming through the Tor network. Try the <a href="https://check.torproject.org">Tor Check</a> site and see whether it thinks you are using Tor or not.
771 771
     </p>
772 772
     <p>
773
-If that site is down, you can still test, but it will involve more effort: <a>http://ipid.shat.net</a> and <a>http://www.showmyip.com/</a> will tell you what your IP address appears to be, but you'll need to know your current IP address so you can compare and decide whether you're using Tor correctly.
773
+If that site is down, you can still test, but it will involve more effort. Sites like <a href="http://ipid.shat.net">http://ipid.shat.net</a> and <a href="http://www.showmyip.com/">http://www.showmyip.com/</a> will tell you what your IP address appears to be, but you'll need to know your current IP address so you can compare and decide whether you're using Tor correctly.
774 774
     </p>
775 775
     <p>
776 776
 To learn your IP address on OS X, Linux, BSD, etc, run "ifconfig". On Windows, go to the Start menu, click Run and enter "cmd". At the command prompt, enter "ipconfig /a".
... ...
@@ -831,33 +831,7 @@ Browser" and it is removed from your system.
831 831
 entirely on how you installed it and which operating system you
832 832
     have. If you installed a package, then hopefully your package has a
833 833
 way to
834
-    uninstall itself. The Windows packages include uninstallers. The
835
-proper way to
836
-    completely remove Tor, Vidalia, and Torbutton for Firefox on any
837
-version of Windows is as follows:
838
-    </p>
839
-
840
-    <ol>
841
-    <li>In your taskbar, right click on Vidalia (the green onion or the
842
-black head)
843
-    and choose exit.</li>
844
-    <li>Right click on the taskbar to bring up TaskManager. Look for
845
-tor.exe in the
846
-    Process List. If it's running, right click and choose End
847
-Process.</li>
848
-    <li>Click the Start button, go to Programs, go to Vidalia, choose
849
-Uninstall.
850
-    This will remove the Vidalia bundle, which includes Tor.</li>
851
-    <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select
852
-Torbutton.
853
-    Click the Uninstall button.</li>
854
-    </ol>
855
-
856
-    <p>
857
-    If you do not follow these steps (for example by trying to uninstall
858
-    Vidalia and Tor while they are still running), you will need to
859
-    reboot and manually remove the directory "Program Files\Vidalia
860
-Bundle".
834
+    uninstall itself. The Windows packages include uninstallers. 
861 835
     </p>
862 836
 
863 837
     <p>
... ...
@@ -1220,15 +1194,15 @@ Why does Google show up in foreign languages?</a></h3>
1220 1194
  Google uses "geolocation" to determine where in the world you are, so it can give you a personalized experience. This includes using the language it thinks you prefer, and it also includes giving you different results on your queries.
1221 1195
 </p>
1222 1196
 <p>
1223
-If you really want to see Google in English you can click the link that provides that. But we consider this a feature with Tor, not a bug --- the Internet is not flat, and it in fact does look different depending on where you are. This feature reminds people of this fact. The easy way to avoid this "feature" is to use <a>http://google.com/ncr</a>.
1197
+If you really want to see Google in English you can click the link that provides that. But we consider this a feature with Tor, not a bug --- the Internet is not flat, and it in fact does look different depending on where you are. This feature reminds people of this fact. The easy way to avoid this "feature" is to use <a href="http://google.com/ncr">http://google.com/ncr</a>.
1224 1198
 </p>
1225 1199
 <p>
1226
-Note that Google search URLs take name/value pairs as arguments and one of those names is "hl". If you set "hl" to "en" then Google will return search results in English regardless of what Google server you have been sent to. On a query this looks like: http://google.com/search?q=...&amp;hl=en&amp;..g
1227
-</p>
1200
+Note that Google search URLs take name/value pairs as arguments and one of those names is "hl". If you set "hl" to "en" then Google will return search results in English regardless of what Google server you have been sent to. On a query this looks like: </p><pre>https://encrypted.google.com/search?q=online%20anonymity&hl=en
1201
+</pre>
1228 1202
 <p>
1229
-Another method is to simply use your  country code for accessing Google. This can be google.be, google.de, google.us and so on. You can also set your language by first selecting it in the Language Tools section, search for something simple. Then extract the language from the URL. In this example, we'll choose Hebrew:  <a>http://www.google.com/search?lr=lang_g'''iw</a>. Next, use that string in the url:  <a>http://google.com/intl/iw/</a>. This can obviously be set as your homepage or bookmarked if necessary. 
1230
-</pb>
1231
-
1203
+Another method is to simply use your country code for accessing Google. This can be google.be, google.de, google.us and so on. 
1204
+</p>
1205
+<hr />
1232 1206
 <a id="GmailWarning"></a>
1233 1207
 <h3><a class="anchor" href="#GmailWarning">Gmail warns me that my
1234 1208
 account
... ...
@@ -1794,9 +1768,16 @@ users
1794 1768
 Configuration is simple, editing your torrc file's SocksListenAddress according to the following examples:
1795 1769
     </p>
1796 1770
     <pre>
1797
-  SocksListenAddress 127.0.0.1 #This provides local interface access only, needs SocksPort to be greater than 0
1798
-  SocksListenAddress 192.168.x.x:9100 #This provides access to Tor on a specified interface
1799
-  SocksListenAddress 0.0.0.0:9100 #Accept from all interfaces
1771
+
1772
+  #This provides local interface access only, 
1773
+  #needs SocksPort to be greater than 0
1774
+  SocksListenAddress 127.0.0.1 
1775
+
1776
+  #This provides access to Tor on a specified interface
1777
+  SocksListenAddress 192.168.x.x:9100 
1778
+
1779
+  #Accept from all interfaces
1780
+  SocksListenAddress 0.0.0.0:9100
1800 1781
    </pre>
1801 1782
     <p>
1802 1783
 You can state multiple listen addresses, in the case that you are part of several networks or subnets.
... ...
@@ -1832,7 +1813,7 @@ If you are interested in forcing all outgoing data through the central Tor clien
1832 1813
 Nickname ididnteditheconfig
1833 1814
     </pre>
1834 1815
     <ul><li>
1835
-    Configure !ORPort: 
1816
+    Configure ORPort: 
1836 1817
     </li></ul>
1837 1818
     <pre>
1838 1819
 ORPort 9001
... ...
@@ -1845,11 +1826,10 @@ ORPort 9001
1845 1826
 ContactInfo human@…
1846 1827
     </pre>
1847 1828
     <ul><li>
1848
-    Start Tor. Watch the log file for a log entry that states: 
1829
+    Start Tor. Watch the log file for a log entry that states: "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor."
1849 1830
     </li></ul>
1850
-    <pre>
1851
-[notice] router_orport_found_reachable(): Self-testing indicates your !ORPort is reachable from the outside. Excellent. Publishing server descriptor.
1852
-    </pre>
1831
+
1832
+    <hr />
1853 1833
 
1854 1834
     <a id="RelayOrBridge"></a>
1855 1835
     <h3><a class="anchor" href="#RelayOrBridge">Should I be a normal
... ...
@@ -1960,7 +1940,7 @@ If you are running Tor as a service and you want to uninstall Tor entirely, be s
1960 1940
 <p>
1961 1941
 Some ISPs are selling "vserver" accounts that provide what they call a virtual server -- you can't actually interact with the hardware, and they can artificially limit certain resources such as the number of file descriptors you can open at once. Competent vserver admins are able to configure your server to not hit these limits. For example, in SWSoft's Virtuozzo, investigate /proc/user_beancounters. Look for "failcnt" in tcpsndbuf, tcprecvbuf, numothersock, and othersockbuf. Ask for these to be increased accordingly. Some users have seen settings work well as follows: 
1962 1942
 <p>
1963
-<table border>
1943
+<table border="1">
1964 1944
 <tr>
1965 1945
 <td>
1966 1946
 <i>resource</i>
... ...
@@ -2075,6 +2055,8 @@ Unfortunately, since Tor currently requires you to be able to connect to all the
2075 2055
 We hope to fix this in the future, once we know how to build a Tor network with restricted topologies -- that is, where each node connects to only a few other nodes. But this is still a long way off.
2076 2056
 </p>
2077 2057
 
2058
+<hr>
2059
+
2078 2060
 <a id="MultipleRelays"></a>
2079 2061
 <h3><a class="anchor" href="#MultipleRelays">I want to run more than one
2080 2062
 relay.</a></h3>
2081 2063