Signed-off-by: hiro <hiro@torproject.org>
... | ... |
@@ -2453,8 +2453,8 @@ exit |
2453 | 2453 |
policies are propagated to Tor clients via the directory, so clients |
2454 | 2454 |
will automatically avoid picking exit relays that would refuse to |
2455 | 2455 |
exit to their intended destination. This way each relay can decide |
2456 |
- the services, hosts, and networks he wants to allow connections to, |
|
2457 |
- based on abuse potential and his own situation. Read the FAQ entry |
|
2456 |
+ the services, hosts, and networks it wants to allow connections to, |
|
2457 |
+ based on abuse potential and its own situation. Read the FAQ entry |
|
2458 | 2458 |
on |
2459 | 2459 |
<a href="<page docs/faq-abuse>#TypicalAbuses">issues you might |
2460 | 2460 |
encounter</a> |
... | ... |
@@ -2931,14 +2931,14 @@ Yes, you do get better anonymity against some attacks. |
2931 | 2931 |
</p> |
2932 | 2932 |
<p> |
2933 | 2933 |
The simplest example is an attacker who owns a small number of Tor relays. |
2934 |
-He will see a connection from you, but he won't be able to know whether |
|
2934 |
+They will see a connection from you, but they won't be able to know whether |
|
2935 | 2935 |
the connection originated at your computer or was relayed from somebody else. |
2936 | 2936 |
</p> |
2937 | 2937 |
<p> |
2938 | 2938 |
There are some cases where it doesn't seem to help: if an attacker can |
2939 |
-watch all of your incoming and outgoing traffic, then it's easy for him |
|
2939 |
+watch all of your incoming and outgoing traffic, then it's easy for them |
|
2940 | 2940 |
to learn which connections were relayed and which started at you. (In |
2941 |
-this case he still doesn't know your destinations unless he is watching |
|
2941 |
+this case they still don't know your destinations unless they are watching |
|
2942 | 2942 |
them too, but you're no better off than if you were an ordinary client.) |
2943 | 2943 |
</p> |
2944 | 2944 |
<p> |
... | ... |
@@ -2948,7 +2948,7 @@ signal to an attacker that you place a high value on your anonymity. |
2948 | 2948 |
Second, there are some more esoteric attacks that are not as |
2949 | 2949 |
well-understood or well-tested that involve making use of the knowledge |
2950 | 2950 |
that you're running a relay -- for example, an attacker may be able to |
2951 |
-"observe" whether you're sending traffic even if he can't actually watch |
|
2951 |
+"observe" whether you're sending traffic even if they can't actually watch |
|
2952 | 2952 |
your network, by relaying traffic through your Tor relay and noticing |
2953 | 2953 |
changes in traffic timing. |
2954 | 2954 |
</p> |
... | ... |
@@ -3475,7 +3475,7 @@ keys, |
3475 | 3475 |
locations, exit policies, and so on. So unless the adversary can |
3476 | 3476 |
control |
3477 | 3477 |
a majority of the directory authorities (as of 2012 there are 8 |
3478 |
- directory authorities), he can't trick the Tor client into using |
|
3478 |
+ directory authorities), they can't trick the Tor client into using |
|
3479 | 3479 |
other Tor relays. |
3480 | 3480 |
</p> |
3481 | 3481 |
|
... | ... |
@@ -4213,7 +4213,7 @@ only solution is to have no opinion. |
4213 | 4213 |
Like all anonymous communication networks that are fast enough for web |
4214 | 4214 |
browsing, Tor is vulnerable to statistical "traffic confirmation" |
4215 | 4215 |
attacks, where the adversary watches traffic at both ends of a circuit |
4216 |
- and confirms his guess that they're communicating. It would be really |
|
4216 |
+ and confirms their guess that those endpoints are communicating. It would be really |
|
4217 | 4217 |
nice if we could use cover traffic to confuse this attack. But there |
4218 | 4218 |
are three problems here: |
4219 | 4219 |
</p> |
... | ... |
@@ -148,6 +148,7 @@ country) |
148 | 148 |
<li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being |
149 | 149 |
used more?</a></li> |
150 | 150 |
<li><a href="#IDontHaveAStaticIP">Can I run a Tor relay using a dynamic IP address?</a></li> |
151 |
+ <li><a href="#IPv6Relay">Can I use IPv6 on my relay?</a></li> |
|
151 | 152 |
<li><a href="#PortscannedMore">Why do I get portscanned more often |
152 | 153 |
when I run a Tor relay?</a></li> |
153 | 154 |
<li><a href="#HighCapacityConnection">How can I get Tor to fully |
... | ... |
@@ -2163,6 +2164,18 @@ the program iptables (for *nix) useful. |
2163 | 2164 |
|
2164 | 2165 |
<hr> |
2165 | 2166 |
|
2167 |
+ <a id="IPv6Relay"></a> |
|
2168 |
+ <h3><a class="anchor" href="#IPv6Relay">Can I use IPv6 on my relay?</a></h3> |
|
2169 |
+ |
|
2170 |
+ <p> |
|
2171 |
+ Tor has <a href="<wiki>org/roadmaps/Tor/IPv6Features">partial</a> support for IPv6 and we |
|
2172 |
+ encourage every relay operator to <a href="<wiki>TorRelayGuide#IPv6">enable IPv6 functionality |
|
2173 |
+ </a> in their torrc configuration files when IPv6 connectivity is available. |
|
2174 |
+ For the time being Tor will require IPv4 addresses on relays, you can not run a Tor relay |
|
2175 |
+ on a host with IPv6 addresses only. |
|
2176 |
+ </p> |
|
2177 |
+ |
|
2178 |
+ <hr> |
|
2166 | 2179 |
<a id="PortscannedMore"></a> |
2167 | 2180 |
<h3><a class="anchor" href="#PortscannedMore">Why do I get portscanned |
2168 | 2181 |
more often when I run a Tor relay?</a></h3> |
... | ... |
@@ -2556,7 +2556,7 @@ relay or bridge relay?</a></h3> |
2556 | 2556 |
|
2557 | 2557 |
<p><a href="<page docs/bridges>">Bridge relays</a> (or "bridges" for |
2558 | 2558 |
short) |
2559 |
- are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't |
|
2559 |
+ are <a href="<wiki>TorRelayGuide">Tor relays</a> that aren't |
|
2560 | 2560 |
listed in the public Tor directory. |
2561 | 2561 |
That means that ISPs or governments trying to block access to the |
2562 | 2562 |
Tor network can't simply block all bridges. |
... | ... |
@@ -2586,9 +2586,10 @@ lots |
2586 | 2586 |
of bandwidth, you should definitely run a normal relay. |
2587 | 2587 |
If you're willing |
2588 | 2588 |
to <a href="#ExitPolicies">be an exit</a>, you should definitely |
2589 |
- run a normal relay, since we need more exits. If you can't be an |
|
2590 |
- exit and only have a little bit of bandwidth, be a bridge. Thanks |
|
2591 |
- for volunteering! |
|
2589 |
+ run an exit relay, since we need more exits. If you can't be an |
|
2590 |
+ exit and only have a little bit of bandwidth, setup an |
|
2591 |
+ <a href="<page docs/pluggable-transports>#operator">obfs4 bridge</a>. |
|
2592 |
+ Thanks for volunteering! |
|
2592 | 2593 |
</p> |
2593 | 2594 |
|
2594 | 2595 |
<hr> |
the following two questions have been moved from the relay
to the "Advanced Tor usage" section as they are more client related:
I want to run my Tor client on a different computer than my applications.
Can I install Tor on a central server, and have my clients connect to it?
... | ... |
@@ -132,6 +132,10 @@ country) |
132 | 132 |
worry?</a></li> |
133 | 133 |
<li><a href="#SocksAndDNS">How do I check if my application that uses |
134 | 134 |
SOCKS is leaking DNS requests?</a></li> |
135 |
+ <li><a href="#TorClientOnADifferentComputerThanMyApplications">I want to run my Tor client on a |
|
136 |
+ different computer than my applications.</a></li> |
|
137 |
+ <li><a href="#ServerClient">Can I install Tor on a central server, and |
|
138 |
+ have my clients connect to it?</a></li> |
|
135 | 139 |
</ul> |
136 | 140 |
|
137 | 141 |
<a id="relay"></a> |
... | ... |
@@ -167,10 +171,6 @@ be?</a></li> |
167 | 171 |
Why did that happen?</a></li> |
168 | 172 |
<li><a href="#MyRelayRecentlyGotTheGuardFlagAndTrafficDroppedByHalf">My |
169 | 173 |
relay recently got the Guard flag and traffic dropped by half.</a></li> |
170 |
- <li><a href="#TorClientOnADifferentComputerThanMyApplications">I want to run my Tor client on a |
|
171 |
- different computer than my applications.</a></li> |
|
172 |
- <li><a href="#ServerClient">Can I install Tor on a central server, and |
|
173 |
- have my clients connect to it?</a></li> |
|
174 | 174 |
<li><a href="#JoinTheNetwork">So I can just configure a nickname and |
175 | 175 |
ORPort and join the network?</a></li> |
176 | 176 |
<li><a href="#RelayOrBridge">Should I be a normal relay or bridge |
... | ... |
@@ -2027,6 +2027,80 @@ from the source code release tor-0.2.4.16-rc is: |
2027 | 2027 |
|
2028 | 2028 |
<hr> |
2029 | 2029 |
|
2030 |
+ <a id="TorClientOnADifferentComputerThanMyApplications"></a> |
|
2031 |
+ <h3><a class="anchor" href="#TorClientOnADifferentComputerThanMyApplications">I |
|
2032 |
+ want to run my Tor client on a different computer than my applications. |
|
2033 |
+ </a></h3> |
|
2034 |
+ <p> |
|
2035 |
+ By default, your Tor client only listens for applications that |
|
2036 |
+ connect from localhost. Connections from other computers are |
|
2037 |
+ refused. If you want to torify applications on different computers |
|
2038 |
+ than the Tor client, you should edit your torrc to define |
|
2039 |
+ SocksListenAddress 0.0.0.0 and then restart (or hup) Tor. If you |
|
2040 |
+ want to get more advanced, you can configure your Tor client on a |
|
2041 |
+ firewall to bind to your internal IP but not your external IP. |
|
2042 |
+ </p> |
|
2043 |
+ |
|
2044 |
+ <hr> |
|
2045 |
+ |
|
2046 |
+ <a id="ServerClient"></a> |
|
2047 |
+ <h3><a class="anchor" href="#ServerClient">Can I install Tor on a |
|
2048 |
+ central server, and have my clients connect to it?</a></h3> |
|
2049 |
+ <p> |
|
2050 |
+ Yes. Tor can be configured as a client or a relay on another |
|
2051 |
+ machine, and allow other machines to be able to connect to it |
|
2052 |
+ for anonymity. This is most useful in an environment where many |
|
2053 |
+ computers want a gateway of anonymity to the rest of the world. |
|
2054 |
+ However, be forwarned that with this configuration, anyone within |
|
2055 |
+ your private network (existing between you and the Tor |
|
2056 |
+ client/relay) can see what traffic you are sending in clear text. |
|
2057 |
+ The anonymity doesn't start until you get to the Tor relay. |
|
2058 |
+ Because of this, if you are the controller of your domain and you |
|
2059 |
+ know everything's locked down, you will be OK, but this configuration |
|
2060 |
+ may not be suitable for large private networks where security is |
|
2061 |
+ key all around. |
|
2062 |
+ </p> |
|
2063 |
+ <p> |
|
2064 |
+Configuration is simple, editing your torrc file's SocksListenAddress |
|
2065 |
+according to the following examples: |
|
2066 |
+ </p> |
|
2067 |
+ <pre> |
|
2068 |
+ |
|
2069 |
+ #This provides local interface access only, |
|
2070 |
+ #needs SocksPort to be greater than 0 |
|
2071 |
+ SocksListenAddress 127.0.0.1 |
|
2072 |
+ |
|
2073 |
+ #This provides access to Tor on a specified interface |
|
2074 |
+ SocksListenAddress 192.168.x.x:9100 |
|
2075 |
+ |
|
2076 |
+ #Accept from all interfaces |
|
2077 |
+ SocksListenAddress 0.0.0.0:9100 |
|
2078 |
+ </pre> |
|
2079 |
+ <p> |
|
2080 |
+You can state multiple listen addresses, in the case that you are |
|
2081 |
+part of several networks or subnets. |
|
2082 |
+ </p> |
|
2083 |
+ <pre> |
|
2084 |
+ SocksListenAddress 192.168.x.x:9100 #eth0 |
|
2085 |
+ SocksListenAddress 10.x.x.x:9100 #eth1 |
|
2086 |
+ </pre> |
|
2087 |
+ <p> |
|
2088 |
+After this, your clients on their respective networks/subnets would specify |
|
2089 |
+a socks proxy with the address and port you specified SocksListenAddress |
|
2090 |
+to be. |
|
2091 |
+ </p> |
|
2092 |
+ <p> |
|
2093 |
+Please note that the SocksPort configuration option gives the port ONLY for |
|
2094 |
+localhost (127.0.0.1). When setting up your SocksListenAddress(es), you need |
|
2095 |
+to give the port with the address, as shown above. |
|
2096 |
+ <p> |
|
2097 |
+If you are interested in forcing all outgoing data through the central Tor |
|
2098 |
+client/relay, instead of the server only being an optional proxy, you may find |
|
2099 |
+the program iptables (for *nix) useful. |
|
2100 |
+ </p> |
|
2101 |
+ |
|
2102 |
+ <hr> |
|
2103 |
+ |
|
2030 | 2104 |
<a id="RunningATorRelay"></a> |
2031 | 2105 |
<h2><a class="anchor" href="#RunningATorRelay">Running a Tor relay:</a></h2> |
2032 | 2106 |
|
... | ... |
@@ -2476,80 +2550,6 @@ users |
2476 | 2550 |
|
2477 | 2551 |
<hr> |
2478 | 2552 |
|
2479 |
- <a id="TorClientOnADifferentComputerThanMyApplications"></a> |
|
2480 |
- <h3><a class="anchor" href="#TorClientOnADifferentComputerThanMyApplications">I |
|
2481 |
- want to run my Tor client on a different computer than my applications. |
|
2482 |
- </a></h3> |
|
2483 |
- <p> |
|
2484 |
- By default, your Tor client only listens for applications that |
|
2485 |
- connect from localhost. Connections from other computers are |
|
2486 |
- refused. If you want to torify applications on different computers |
|
2487 |
- than the Tor client, you should edit your torrc to define |
|
2488 |
- SocksListenAddress 0.0.0.0 and then restart (or hup) Tor. If you |
|
2489 |
- want to get more advanced, you can configure your Tor client on a |
|
2490 |
- firewall to bind to your internal IP but not your external IP. |
|
2491 |
- </p> |
|
2492 |
- |
|
2493 |
- <hr> |
|
2494 |
- |
|
2495 |
- <a id="ServerClient"></a> |
|
2496 |
- <h3><a class="anchor" href="#ServerClient">Can I install Tor on a |
|
2497 |
- central server, and have my clients connect to it?</a></h3> |
|
2498 |
- <p> |
|
2499 |
- Yes. Tor can be configured as a client or a relay on another |
|
2500 |
- machine, and allow other machines to be able to connect to it |
|
2501 |
- for anonymity. This is most useful in an environment where many |
|
2502 |
- computers want a gateway of anonymity to the rest of the world. |
|
2503 |
- However, be forwarned that with this configuration, anyone within |
|
2504 |
- your private network (existing between you and the Tor |
|
2505 |
- client/relay) can see what traffic you are sending in clear text. |
|
2506 |
- The anonymity doesn't start until you get to the Tor relay. |
|
2507 |
- Because of this, if you are the controller of your domain and you |
|
2508 |
- know everything's locked down, you will be OK, but this configuration |
|
2509 |
- may not be suitable for large private networks where security is |
|
2510 |
- key all around. |
|
2511 |
- </p> |
|
2512 |
- <p> |
|
2513 |
-Configuration is simple, editing your torrc file's SocksListenAddress |
|
2514 |
-according to the following examples: |
|
2515 |
- </p> |
|
2516 |
- <pre> |
|
2517 |
- |
|
2518 |
- #This provides local interface access only, |
|
2519 |
- #needs SocksPort to be greater than 0 |
|
2520 |
- SocksListenAddress 127.0.0.1 |
|
2521 |
- |
|
2522 |
- #This provides access to Tor on a specified interface |
|
2523 |
- SocksListenAddress 192.168.x.x:9100 |
|
2524 |
- |
|
2525 |
- #Accept from all interfaces |
|
2526 |
- SocksListenAddress 0.0.0.0:9100 |
|
2527 |
- </pre> |
|
2528 |
- <p> |
|
2529 |
-You can state multiple listen addresses, in the case that you are |
|
2530 |
-part of several networks or subnets. |
|
2531 |
- </p> |
|
2532 |
- <pre> |
|
2533 |
- SocksListenAddress 192.168.x.x:9100 #eth0 |
|
2534 |
- SocksListenAddress 10.x.x.x:9100 #eth1 |
|
2535 |
- </pre> |
|
2536 |
- <p> |
|
2537 |
-After this, your clients on their respective networks/subnets would specify |
|
2538 |
-a socks proxy with the address and port you specified SocksListenAddress |
|
2539 |
-to be. |
|
2540 |
- </p> |
|
2541 |
- <p> |
|
2542 |
-Please note that the SocksPort configuration option gives the port ONLY for |
|
2543 |
-localhost (127.0.0.1). When setting up your SocksListenAddress(es), you need |
|
2544 |
-to give the port with the address, as shown above. |
|
2545 |
- <p> |
|
2546 |
-If you are interested in forcing all outgoing data through the central Tor |
|
2547 |
-client/relay, instead of the server only being an optional proxy, you may find |
|
2548 |
-the program iptables (for *nix) useful. |
|
2549 |
- </p> |
|
2550 |
- |
|
2551 |
- <hr> |
|
2552 |
- |
|
2553 | 2553 |
<a id="RelayOrBridge"></a> |
2554 | 2554 |
<h3><a class="anchor" href="#RelayOrBridge">Should I be a normal |
2555 | 2555 |
relay or bridge relay?</a></h3> |
... | ... |
@@ -2454,12 +2454,10 @@ users |
2454 | 2454 |
the BadExit flag why did that happen?</a></h3> |
2455 | 2455 |
|
2456 | 2456 |
<p>If you got this flag then we either discovered a problem or suspicious |
2457 |
- activity coming from your exit and weren't able to contact you. The reason |
|
2458 |
- for most flaggings are documented on the <a |
|
2459 |
- href="https://trac.torproject.org/projects/tor/wiki/doc/badRelays">bad |
|
2460 |
- relays wiki</a>. Please <a |
|
2461 |
- href="<page about/contact>">contact us</a> so |
|
2462 |
- we can sort out the issue.</p> |
|
2457 |
+ activity when routing traffic through your exit and weren't able to contact you. |
|
2458 |
+ Please reach out to the <a href="mailto:bad-relays@lists.torproject.org">bad-relays team</a> |
|
2459 |
+ so we can sort out the issue. |
|
2460 |
+ </p> |
|
2463 | 2461 |
|
2464 | 2462 |
<hr> |
2465 | 2463 |
|
... | ... |
@@ -143,7 +143,7 @@ country) |
143 | 143 |
<li><a href="#MostNeededRelayType">What type of relays are most needed?</a></li> |
144 | 144 |
<li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being |
145 | 145 |
used more?</a></li> |
146 |
- <li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li> |
|
146 |
+ <li><a href="#IDontHaveAStaticIP">Can I run a Tor relay using a dynamic IP address?</a></li> |
|
147 | 147 |
<li><a href="#PortscannedMore">Why do I get portscanned more often |
148 | 148 |
when I run a Tor relay?</a></li> |
149 | 149 |
<li><a href="#HighCapacityConnection">How can I get Tor to fully |
... | ... |
@@ -2079,8 +2079,8 @@ from the source code release tor-0.2.4.16-rc is: |
2079 | 2079 |
<hr> |
2080 | 2080 |
|
2081 | 2081 |
<a id="IDontHaveAStaticIP"></a> |
2082 |
- <h3><a class="anchor" href="#IDontHaveAStaticIP">I don't have a static |
|
2083 |
- IP.</a></h3> |
|
2082 |
+ <h3><a class="anchor" href="#IDontHaveAStaticIP">Can I run a Tor relay using a |
|
2083 |
+ dynamic IP address?</a></h3> |
|
2084 | 2084 |
|
2085 | 2085 |
<p> |
2086 | 2086 |
Tor can handle relays with dynamic IP addresses just fine. Just leave |
... | ... |
@@ -2149,12 +2149,6 @@ from |
2149 | 2149 |
your |
2150 | 2150 |
relay, you can set it up to only allow connections to other Tor |
2151 | 2151 |
relays. |
2152 |
- </li> |
|
2153 |
- <li>If your relay is behind a NAT and it doesn't know its public |
|
2154 |
- IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port |
|
2155 |
- forwarding. Forwarding TCP connections is system dependent but |
|
2156 |
- <a href="#BehindANAT">this FAQ entry</a> |
|
2157 |
- offers some examples on how to do this. |
|
2158 | 2152 |
</li> |
2159 | 2153 |
<li>Your relay will passively estimate and advertise its recent |
2160 | 2154 |
bandwidth capacity, so high-bandwidth relays will attract more users |
... | ... |
@@ -2141,16 +2141,6 @@ need to be?</a></h3> |
2141 | 2141 |
sure it's not too often, since connections using the relay when it |
2142 | 2142 |
disconnects will break. |
2143 | 2143 |
</li> |
2144 |
- <li>Tor has built-in support for <a |
|
2145 |
- href="#BandwidthShaping"> |
|
2146 |
- rate limiting</a>. Further, if you have a fast |
|
2147 |
- link but want to limit the number of bytes per |
|
2148 |
- day (or week or month) that you donate, check out the <a |
|
2149 |
- |
|
2150 |
-href="#LimitTotalBandwidth"> |
|
2151 |
-hibernation |
|
2152 |
- feature</a>. |
|
2153 |
- </li> |
|
2154 | 2144 |
<li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> |
2155 | 2145 |
that |
2156 | 2146 |
specifies what sort of outbound connections are allowed or refused |
... | ... |
@@ -2136,6 +2136,11 @@ need to be?</a></h3> |
2136 | 2136 |
</p> |
2137 | 2137 |
|
2138 | 2138 |
<ul> |
2139 |
+ <li>It's fine if the relay goes offline sometimes. The directories |
|
2140 |
+ notice this quickly and stop advertising the relay. Just try to make |
|
2141 |
+ sure it's not too often, since connections using the relay when it |
|
2142 |
+ disconnects will break. |
|
2143 |
+ </li> |
|
2139 | 2144 |
<li>Tor has built-in support for <a |
2140 | 2145 |
href="#BandwidthShaping"> |
2141 | 2146 |
rate limiting</a>. Further, if you have a fast |
... | ... |
@@ -2154,11 +2159,6 @@ from |
2154 | 2159 |
your |
2155 | 2160 |
relay, you can set it up to only allow connections to other Tor |
2156 | 2161 |
relays. |
2157 |
- </li> |
|
2158 |
- <li>It's fine if the relay goes offline sometimes. The directories |
|
2159 |
- notice this quickly and stop advertising the relay. Just try to make |
|
2160 |
- sure it's not too often, since connections using the relay when it |
|
2161 |
- disconnects will break. |
|
2162 | 2162 |
</li> |
2163 | 2163 |
<li>If your relay is behind a NAT and it doesn't know its public |
2164 | 2164 |
IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port |
... | ... |
@@ -2160,9 +2160,6 @@ relays. |
2160 | 2160 |
sure it's not too often, since connections using the relay when it |
2161 | 2161 |
disconnects will break. |
2162 | 2162 |
</li> |
2163 |
- <li>We can handle relays with dynamic IPs just fine — simply |
|
2164 |
- leave the Address config option blank, and Tor will try to guess. |
|
2165 |
- </li> |
|
2166 | 2163 |
<li>If your relay is behind a NAT and it doesn't know its public |
2167 | 2164 |
IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port |
2168 | 2165 |
forwarding. Forwarding TCP connections is system dependent but |
... | ... |
@@ -140,6 +140,7 @@ country) |
140 | 140 |
|
141 | 141 |
<li><a href="#HowDoIDecide">How do I decide if I should run a relay? |
142 | 142 |
</a></li> |
143 |
+ <li><a href="#MostNeededRelayType">What type of relays are most needed?</a></li> |
|
143 | 144 |
<li><a href="#WhyIsntMyRelayBeingUsedMore">Why isn't my relay being |
144 | 145 |
used more?</a></li> |
145 | 146 |
<li><a href="#IDontHaveAStaticIP">I don't have a static IP.</a></li> |
... | ... |
@@ -2043,6 +2044,19 @@ from the source code release tor-0.2.4.16-rc is: |
2043 | 2044 |
|
2044 | 2045 |
<hr> |
2045 | 2046 |
|
2047 |
+ <a id="MostNeededRelayType"></a> |
|
2048 |
+ <h3><a class="anchor" href="#MostNeededRelayType">What type of relays are most needed?</a></h3> |
|
2049 |
+ <p> |
|
2050 |
+ <ul> |
|
2051 |
+ <li>The exit relay is the most needed relay type but it also comes with the highest legal exposure and risk (and you |
|
2052 |
+ should NOT run them from your home).</li> |
|
2053 |
+ <li>If you are looking to run a relay with minimal effort, fast guard relays are also very useful</li> |
|
2054 |
+ <li>followed by bridges.</li> |
|
2055 |
+ </ul> |
|
2056 |
+ </p> |
|
2057 |
+ |
|
2058 |
+ <hr> |
|
2059 |
+ |
|
2046 | 2060 |
<a id="WhyIsntMyRelayBeingUsedMore"></a> |
2047 | 2061 |
<h3><a class="anchor" href="#WhyIsntMyRelayBeingUsedMore">Why isn't my |
2048 | 2062 |
relay being used more?</a></h3> |
... | ... |
@@ -2034,9 +2034,11 @@ from the source code release tor-0.2.4.16-rc is: |
2034 | 2034 |
run a relay?</a></h3> |
2035 | 2035 |
<p> |
2036 | 2036 |
We're looking for people with reasonably reliable Internet connections, |
2037 |
- that have at least 250 kilobytes/second each way. If that's you, please |
|
2038 |
- consider <a href="https://www.torproject.org/docs/tor-relay-debian">helping |
|
2039 |
- out</a>. |
|
2037 |
+ that have at least 1 MByte/second (that is 8 MBit/second) available bandwidth each way. If that's you, please |
|
2038 |
+ consider <a href="<wiki>TorRelayGuide">running a Tor relay</a>. |
|
2039 |
+ </p> |
|
2040 |
+ <p> |
|
2041 |
+ Even if you do not have at least 8 MBit/s of available bandwidth you can still help the Tor network by running a <a href="<page docs/pluggable-transports>#operator">Tor bridge with obfs4 support</a>. In that case you should have at least 1 MBit/s of available bandwidth. |
|
2040 | 2042 |
</p> |
2041 | 2043 |
|
2042 | 2044 |
<hr> |
... | ... |
@@ -1514,7 +1514,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed |
1514 | 1514 |
Tor Browser? How do I verify a build?</a></h3> |
1515 | 1515 |
|
1516 | 1516 |
<p> |
1517 |
- Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build</a>. |
|
1517 |
+ Tor Browser is built from the <a href="https://gitweb.torproject.org/builders/tor-browser-build.git/">tor-browser-build.git git repository</a>. You can have a look at the <a href="https://gitweb.torproject.org/builders/tor-browser-build.git/tree/README">README file</a> for the build instructions. There is also some informations in the <a href="https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking">Tor Browser Hacking Guide</a>. |
|
1518 | 1518 |
</p> |
1519 | 1519 |
|
1520 | 1520 |
|
... | ... |
@@ -287,7 +287,7 @@ things?</a></li> |
287 | 287 |
<hr> |
288 | 288 |
|
289 | 289 |
<a id="General"></a> |
290 |
- <h2><a class="anchor">General:</a></h2> |
|
290 |
+ <h2><a class="anchor" href="#General">General:</a></h2> |
|
291 | 291 |
|
292 | 292 |
<a id="WhatIsTor"></a> |
293 | 293 |
<h3><a class="anchor" href="#WhatIsTor">What is Tor?</a></h3> |
... | ... |
@@ -889,7 +889,7 @@ executive |
889 | 889 |
<hr> |
890 | 890 |
|
891 | 891 |
<a id="CompilationAndInstallation"></a> |
892 |
- <h2><a class="anchor">Compilation And Installation:</a></h2> |
|
892 |
+ <h2><a class="anchor" href="#CompilationAndInstallation">Compilation And Installation:</a></h2> |
|
893 | 893 |
|
894 | 894 |
<a id="HowUninstallTor"></a> |
895 | 895 |
<h3><a class="anchor" href="#HowUninstallTor">How do I uninstall |
... | ... |
@@ -1025,7 +1025,7 @@ bundle that includes Tor?</a></h3> |
1025 | 1025 |
<hr> |
1026 | 1026 |
|
1027 | 1027 |
<a id="TBBGeneral"></a> |
1028 |
-<h2><a class="anchor">Tor Browser (general):</a></h2> |
|
1028 |
+<h2><a class="anchor" href="#TBBGeneral">Tor Browser (general):</a></h2> |
|
1029 | 1029 |
|
1030 | 1030 |
<a id="TBBFlash"></a> |
1031 | 1031 |
<h3><a class="anchor" href="#TBBFlash">Why can't I view videos on |
... | ... |
@@ -1380,7 +1380,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed |
1380 | 1380 |
<hr> |
1381 | 1381 |
|
1382 | 1382 |
<a id="TBB3.x"></a> |
1383 |
-<h2><a class="anchor">Tor Browser (3.x and later):</a></h2> |
|
1383 |
+<h2><a class="anchor" href="#TBB3.x">Tor Browser (3.x and later):</a></h2> |
|
1384 | 1384 |
<a id="WhereDidVidaliaGo"></a> |
1385 | 1385 |
<h3><a class="anchor" href="#WhereDidVidaliaGo">Where did the world map |
1386 | 1386 |
(Vidalia) go?</a></h3> |
... | ... |
@@ -1510,7 +1510,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed |
1510 | 1510 |
<hr> |
1511 | 1511 |
|
1512 | 1512 |
<a id="AdvancedTorUsage"></a> |
1513 |
-<h2><a class="anchor">Advanced Tor usage:</a></h2> |
|
1513 |
+<h2><a class="anchor" href="#AdvancedTorUsage">Advanced Tor usage:</a></h2> |
|
1514 | 1514 |
|
1515 | 1515 |
<a id="torrc"></a> |
1516 | 1516 |
<h3><a class="anchor" href="#torrc">I'm supposed to "edit my torrc". |
... | ... |
@@ -2016,7 +2016,7 @@ from the source code release tor-0.2.4.16-rc is: |
2016 | 2016 |
<hr> |
2017 | 2017 |
|
2018 | 2018 |
<a id="RunningATorRelay"></a> |
2019 |
- <h2><a class="anchor">Running a Tor relay:</a></h2> |
|
2019 |
+ <h2><a class="anchor" href="#RunningATorRelay">Running a Tor relay:</a></h2> |
|
2020 | 2020 |
|
2021 | 2021 |
<a id="HowDoIDecide"></a> |
2022 | 2022 |
<h3><a class="anchor" href="#HowDoIDecide">How do I decide if I should |
... | ... |
@@ -3000,7 +3000,7 @@ diversity, |
3000 | 3000 |
|
3001 | 3001 |
# Leaving in old ids to accomodate incoming links. |
3002 | 3002 |
<a id="TorOnionServices"></a><a id="TorHiddenServices"></a> |
3003 |
-<h2><a class="anchor">Tor onion services:</a></h2> |
|
3003 |
+<h2><a class="anchor" href="#TorOnionServices">Tor onion services:</a></h2> |
|
3004 | 3004 |
|
3005 | 3005 |
<a id="AccessOnionServices"></a><a id="AccessHiddenServices"></a> |
3006 | 3006 |
<h3><a class="anchor" href="#AccessOnionServices">How do I access |
... | ... |
@@ -3066,7 +3066,7 @@ diversity, |
3066 | 3066 |
<hr> |
3067 | 3067 |
|
3068 | 3068 |
<a id="Development"></a> |
3069 |
- <h2><a class="anchor">Development:</a></h2> |
|
3069 |
+ <h2><a class="anchor" href="#Development">Development:</a></h2> |
|
3070 | 3070 |
|
3071 | 3071 |
<a id="VersionNumbers"></a> |
3072 | 3072 |
<h3><a class="anchor" href="#VersionNumbers">What do these weird |
... | ... |
@@ -3245,7 +3245,7 @@ diversity, |
3245 | 3245 |
<hr> |
3246 | 3246 |
|
3247 | 3247 |
<a id="AnonymityAndSecurity"></a> |
3248 |
- <h2><a class="anchor">Anonymity And Security:</a></h2> |
|
3248 |
+ <h2><a class="anchor" href="#AnonymityAndSecurity">Anonymity And Security:</a></h2> |
|
3249 | 3249 |
|
3250 | 3250 |
<a id="WhatProtectionsDoesTorProvide"></a> |
3251 | 3251 |
<h3><a class="anchor" href="#WhatProtectionsDoesTorProvide">What |
... | ... |
@@ -3777,7 +3777,7 @@ Perhaps even run separate Tor clients for these applications. |
3777 | 3777 |
<hr> |
3778 | 3778 |
|
3779 | 3779 |
<a id="AlternateDesigns"></a> |
3780 |
- <h2><a class="anchor">Alternate designs:</a></h2> |
|
3780 |
+ <h2><a class="anchor" href="#AlternateDesigns">Alternate designs:</a></h2> |
|
3781 | 3781 |
|
3782 | 3782 |
<a id="EverybodyARelay"></a> |
3783 | 3783 |
<h3><a class="anchor" href="#EverybodyARelay">You should make every |
... | ... |
@@ -4251,7 +4251,7 @@ only solution is to have no opinion. |
4251 | 4251 |
<hr> |
4252 | 4252 |
|
4253 | 4253 |
<a id="Abuse"></a> |
4254 |
- <h2><a class="anchor">Abuse:</a></h2> |
|
4254 |
+ <h2><a class="anchor" href="#Abuse">Abuse:</a></h2> |
|
4255 | 4255 |
|
4256 | 4256 |
<a id="Criminals"></a> |
4257 | 4257 |
<h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals |
Add anchors.
Change heading text from paragraphs to h4s, but keep previous vertcal spacing.
... | ... |
@@ -14,7 +14,8 @@ |
14 | 14 |
<h1>Tor FAQ</h1> |
15 | 15 |
<hr> |
16 | 16 |
|
17 |
- <p>General questions:</p> |
|
17 |
+ <a id="general"></a> |
|
18 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#general">General questions:</a></h4> |
|
18 | 19 |
<ul> |
19 | 20 |
<li><a href="#WhatIsTor">What is Tor?</a></li> |
20 | 21 |
<li><a href="#Torisdifferent">How is Tor different from other |
... | ... |
@@ -43,7 +44,8 @@ proxies?</a></li> |
43 | 44 |
exit nodes are there?</a></li> |
44 | 45 |
</ul> |
45 | 46 |
|
46 |
- <p>Compilation and Installation:</p> |
|
47 |
+ <a id="comp-install"></a> |
|
48 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#comp-install">Compilation and Installation:</a></h4> |
|
47 | 49 |
|
48 | 50 |
<ul> |
49 | 51 |
<li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li> |
... | ... |
@@ -58,7 +60,8 @@ proxies?</a></li> |
58 | 60 |
includes Tor?</a></li> |
59 | 61 |
</ul> |
60 | 62 |
|
61 |
- <p>Tor Browser (general):</p> |
|
63 |
+ <a id="tbb"></a> |
|
64 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#tbb">Tor Browser (general):</a></h4> |
|
62 | 65 |
<ul> |
63 | 66 |
|
64 | 67 |
<li><a href="#TBBFlash">Why can't I view videos on YouTube and other |
... | ... |
@@ -90,7 +93,8 @@ unsafe?</a></li> |
90 | 93 |
with my application?</a></li> |
91 | 94 |
</ul> |
92 | 95 |
|
93 |
- <p>Tor Browser (3.x and later):</p> |
|
96 |
+ <a id="tbb-3plus"></a> |
|
97 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#tbb-3plus">Tor Browser (3.x and later):</a></h4> |
|
94 | 98 |
|
95 | 99 |
<ul> |
96 | 100 |
<li><a href="#DisableJS">How do I disable JavaScript?</a></li> |
... | ... |
@@ -105,7 +109,8 @@ unsafe?</a></li> |
105 | 109 |
How do I verify a build?</a></li> |
106 | 110 |
</ul> |
107 | 111 |
|
108 |
- <p>Advanced Tor usage:</p> |
|
112 |
+ <a id="advanced"></a> |
|
113 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#advanced">Advanced Tor usage:</a></h4> |
|
109 | 114 |
|
110 | 115 |
<ul> |
111 | 116 |
<li><a href="#torrc">I'm supposed to "edit my torrc". What does |
... | ... |
@@ -129,7 +134,8 @@ country) |
129 | 134 |
SOCKS is leaking DNS requests?</a></li> |
130 | 135 |
</ul> |
131 | 136 |
|
132 |
- <p>Running a Tor relay:</p> |
|
137 |
+ <a id="relay"></a> |
|
138 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#relay">Running a Tor relay:</a></h4> |
|
133 | 139 |
<ul> |
134 | 140 |
|
135 | 141 |
<li><a href="#HowDoIDecide">How do I decide if I should run a relay? |
... | ... |
@@ -191,14 +197,16 @@ relay.</a></li> |
191 | 197 |
run my own?</a></li> |
192 | 198 |
</ul> |
193 | 199 |
|
194 |
- <p>Tor onion services:</p> |
|
200 |
+ <a id="onion-services"></a> |
|
201 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#onion-services">Tor onion services:</a></h4> |
|
195 | 202 |
|
196 | 203 |
<ul> |
197 | 204 |
<li><a href="#AccessOnionServices">How do I access onion services?</a></li> |
198 | 205 |
<li><a href="#ProvideAnOnionService">How do I provide an onion service?</a></li> |
199 | 206 |
</ul> |
200 | 207 |
|
201 |
- <p>Development:</p> |
|
208 |
+ <a id="dev"></a> |
|
209 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#dev">Development:</a></h4> |
|
202 | 210 |
|
203 | 211 |
<ul> |
204 | 212 |
<li><a href="#VersionNumbers">What do these weird version numbers |
... | ... |
@@ -212,7 +220,8 @@ relay.</a></li> |
212 | 220 |
into Tor?</a></li> |
213 | 221 |
</ul> |
214 | 222 |
|
215 |
- <p>Anonymity and Security:</p> |
|
223 |
+ <a id="anonsec"></a> |
|
224 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#anonsec">Anonymity and Security:</a></h4> |
|
216 | 225 |
<ul> |
217 | 226 |
<li><a href="#WhatProtectionsDoesTorProvide">What protections does Tor |
218 | 227 |
provide?</a></li> |
... | ... |
@@ -240,7 +249,8 @@ uses.</a></li> |
240 | 249 |
<li><a href="#LearnMoreAboutAnonymity">Where can I learn more about anonymity?</a></li> |
241 | 250 |
</ul> |
242 | 251 |
|
243 |
- <p>Alternate designs that we don't do (yet):</p> |
|
252 |
+ <a id="altdesigns"></a> |
|
253 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#altdesigns">Alternate designs that we don't do (yet):</a></h4> |
|
244 | 254 |
|
245 | 255 |
<ul> |
246 | 256 |
<li><a href="#EverybodyARelay">You should make every Tor user be a |
... | ... |
@@ -270,7 +280,8 @@ packets, |
270 | 280 |
traffic.</a></li> |
271 | 281 |
</ul> |
272 | 282 |
|
273 |
- <p>Abuse:</p> |
|
283 |
+ <a id="abuse"></a> |
|
284 |
+ <h4 style="margin-bottom: 18px"><a class="anchor" href="#abuse">Abuse:</a></h4> |
|
274 | 285 |
<ul> |
275 | 286 |
<li><a href="#Criminals">Doesn't Tor enable criminals to do bad |
276 | 287 |
things?</a></li> |
Renamed files, made new files with old names for redirects, updated
links to use new URLs.
... | ... |
@@ -3062,7 +3062,7 @@ diversity, |
3062 | 3062 |
onion service?</a></h3> |
3063 | 3063 |
|
3064 | 3064 |
<p> |
3065 |
- See the <a href="<page docs/tor-hidden-service>"> |
|
3065 |
+ See the <a href="<page docs/tor-onion-service>"> |
|
3066 | 3066 |
official onion service configuration instructions</a>. |
3067 | 3067 |
</p> |
3068 | 3068 |
|
... | ... |
@@ -191,11 +191,11 @@ relay.</a></li> |
191 | 191 |
run my own?</a></li> |
192 | 192 |
</ul> |
193 | 193 |
|
194 |
- <p>Tor hidden services:</p> |
|
194 |
+ <p>Tor onion services:</p> |
|
195 | 195 |
|
196 | 196 |
<ul> |
197 |
- <li><a href="#AccessHiddenServices">How do I access hidden services?</a></li> |
|
198 |
- <li><a href="#ProvideAHiddenService">How do I provide a hidden service?</a></li> |
|
197 |
+ <li><a href="#AccessOnionServices">How do I access onion services?</a></li> |
|
198 |
+ <li><a href="#ProvideAnOnionService">How do I provide an onion service?</a></li> |
|
199 | 199 |
</ul> |
200 | 200 |
|
201 | 201 |
<p>Development:</p> |
... | ... |
@@ -1817,7 +1817,7 @@ versions. |
1817 | 1817 |
<p> |
1818 | 1818 |
Note also that not every circuit is used to deliver traffic outside of |
1819 | 1819 |
the Tor network. It is normal to see non-exit circuits (such as those |
1820 |
- used to connect to hidden services, those that do directory fetches, |
|
1820 |
+ used to connect to onion services, those that do directory fetches, |
|
1821 | 1821 |
those used for relay reachability self-tests, and so on) that end at |
1822 | 1822 |
a non-exit node. To keep a node from being used entirely, see |
1823 | 1823 |
<tt>ExcludeNodes</tt> and <tt>StrictNodes</tt> in the |
... | ... |
@@ -3001,15 +3001,16 @@ diversity, |
3001 | 3001 |
|
3002 | 3002 |
<hr> |
3003 | 3003 |
|
3004 |
-<a id="TorHiddenServices"></a> |
|
3005 |
-<h2><a class="anchor">Tor hidden services:</a></h2> |
|
3004 |
+# Leaving in old ids to accomodate incoming links. |
|
3005 |
+<a id="TorOnionServices"></a><a id="TorHiddenServices"></a> |
|
3006 |
+<h2><a class="anchor">Tor onion services:</a></h2> |
|
3006 | 3007 |
|
3007 |
- <a id="AccessHiddenServices"></a> |
|
3008 |
- <h3><a class="anchor" href="#AccessHiddenServices">How do I access |
|
3009 |
- hidden services?</a></h3> |
|
3008 |
+ <a id="AccessOnionServices"></a><a id="AccessHiddenServices"></a> |
|
3009 |
+ <h3><a class="anchor" href="#AccessOnionServices">How do I access |
|
3010 |
+ onion services?</a></h3> |
|
3010 | 3011 |
|
3011 | 3012 |
<p> |
3012 |
- Tor hidden services are named with a special top-level domain (TLD) |
|
3013 |
+ Tor onion services are named with a special top-level domain (TLD) |
|
3013 | 3014 |
name in DNS: .onion. Since the .onion TLD is not recognized by the |
3014 | 3015 |
official root DNS servers on the Internet, your application will not |
3015 | 3016 |
get the response it needs to locate the service. Currently, the Tor |
... | ... |
@@ -3020,7 +3021,7 @@ diversity, |
3020 | 3021 |
<p> |
3021 | 3022 |
Therefore, your application <b>needs</b> to pass the .onion hostname to |
3022 | 3023 |
Tor directly. You can't try to resolve it to an IP address, since there |
3023 |
- <i>is</i> no corresponding IP address: the server is hidden, after all! |
|
3024 |
+ <i>is</i> no corresponding IP address. |
|
3024 | 3025 |
</p> |
3025 | 3026 |
|
3026 | 3027 |
<p> |
... | ... |
@@ -3044,10 +3045,10 @@ diversity, |
3044 | 3045 |
<p> |
3045 | 3046 |
For applications that do not support HTTP proxy, and so cannot use |
3046 | 3047 |
Polipo, <a href="http://www.freecap.ru/eng/">FreeCap</a> is an |
3047 |
- alternative. When using FreeCap set proxy protocol to SOCKS 5 and under |
|
3048 |
+ alternative. When using FreeCap set proxy protocol to SOCKS 5 and under |
|
3048 | 3049 |
settings set DNS name resolving to remote. This |
3049 | 3050 |
will allow you to use almost any program with Tor without leaking DNS |
3050 |
- lookups and allow those same programs to access hidden services. |
|
3051 |
+ lookups and allow those same programs to access onion services. |
|
3051 | 3052 |
</p> |
3052 | 3053 |
|
3053 | 3054 |
<p> |
... | ... |
@@ -3056,13 +3057,13 @@ diversity, |
3056 | 3057 |
|
3057 | 3058 |
<hr> |
3058 | 3059 |
|
3059 |
- <a id="ProvideAHiddenService"></a> |
|
3060 |
- <h3><a class="anchor" href="#ProvideAHiddenService">How do I provide a |
|
3061 |
- hidden service?</a></h3> |
|
3060 |
+ <a id="ProvideAnOnionService"></a><a id="ProvideAHiddenService"></a> |
|
3061 |
+ <h3><a class="anchor" href="#ProvideAnOnionService">How do I provide an |
|
3062 |
+ onion service?</a></h3> |
|
3062 | 3063 |
|
3063 | 3064 |
<p> |
3064 | 3065 |
See the <a href="<page docs/tor-hidden-service>"> |
3065 |
- official hidden service configuration instructions</a>. |
|
3066 |
+ official onion service configuration instructions</a>. |
|
3066 | 3067 |
</p> |
3067 | 3068 |
|
3068 | 3069 |
<hr> |
... | ... |
@@ -3951,7 +3952,7 @@ and clients need to predict all the packets they will want to send in |
3951 | 3952 |
a session before picking their exit node! |
3952 | 3953 |
</li> |
3953 | 3954 |
<li>The Tor-internal name spaces would need to be redesigned. We support |
3954 |
-hidden service ".onion" addresses by intercepting the addresses when |
|
3955 |
+onion service ".onion" addresses by intercepting the addresses when |
|
3955 | 3956 |
they are passed to the Tor client. Doing so at the IP level will require |
3956 | 3957 |
a more complex interface between Tor and the local DNS resolver. |
3957 | 3958 |
</li> |
... | ... |
@@ -4002,7 +4003,7 @@ their path length.</a></h3> |
4002 | 4003 |
<p> |
4003 | 4004 |
Right now the path length is hard-coded at 3 plus the number of nodes in |
4004 | 4005 |
your path that are sensitive. That is, in normal cases it's 3, but for |
4005 |
- example if you're accessing a hidden service or a ".exit" address it could be 4. |
|
4006 |
+ example if you're accessing an onion service or a ".exit" address it could be 4. |
|
4006 | 4007 |
</p> |
4007 | 4008 |
<p> |
4008 | 4009 |
We don't want to encourage people to use paths longer than this — it |
... | ... |
@@ -682,7 +682,7 @@ with more funding?</a></h3> |
682 | 682 |
|
683 | 683 |
<p> |
684 | 684 |
The Tor network's <a |
685 |
-href="https://metrics.torproject.org/networksize.html">serveral thousand</a> |
|
685 |
+href="https://metrics.torproject.org/networksize.html">several thousand</a> |
|
686 | 686 |
relays push <a |
687 | 687 |
href="https://metrics.torproject.org/bandwidth.html">around 100 Gbps on |
688 | 688 |
average</a>. We have <a |
... | ... |
@@ -682,15 +682,12 @@ with more funding?</a></h3> |
682 | 682 |
|
683 | 683 |
<p> |
684 | 684 |
The Tor network's <a |
685 |
- |
|
686 |
-href="https://metrics.torproject.org/network.html#networksize">several |
|
687 |
- thousand</a> relays push <a |
|
688 |
- href="https://metrics.torproject.org/network.html#bandwidth">over |
|
689 |
- 7.5GB per second on average</a>. We have <a |
|
690 |
- |
|
691 |
-href="https://metrics.torproject.org/users.html#direct-users">millions of |
|
692 |
- daily users</a>. But the Tor network is not yet |
|
693 |
- self-sustaining. |
|
685 |
+href="https://metrics.torproject.org/networksize.html">serveral thousand</a> |
|
686 |
+ relays push <a |
|
687 |
+href="https://metrics.torproject.org/bandwidth.html">around 100 Gbps on |
|
688 |
+average</a>. We have <a |
|
689 |
+href="https://metrics.torproject.org/userstats-relay-country.html">millions of |
|
690 |
+ daily users</a>. But the Tor network is not yet self-sustaining. |
|
694 | 691 |
</p> |
695 | 692 |
|
696 | 693 |
<p> |
fix comes mostly from pastly (thanks!)
... | ... |
@@ -1525,15 +1525,19 @@ instructions for how your Tor program should behave. The default |
1525 | 1525 |
configuration should work fine for most Tor users. |
1526 | 1526 |
</p> |
1527 | 1527 |
<p> |
1528 |
-If you installed Tor Browser, look for |
|
1528 |
+If you installed Tor Browser on Windows or Linux, look for |
|
1529 | 1529 |
<code>Browser/TorBrowser/Data/Tor/torrc</code> inside your Tor Browser |
1530 | 1530 |
directory. |
1531 |
-On OS X, you must right-click or command-click on the Tor Browser icon, |
|
1532 |
-and select "Show Package Contents" before the Tor Browser directories become |
|
1533 |
-visible. |
|
1531 |
+If you're on macOS, the torrc is in <code>~/Library/Application Support/TorBrowser-Data/Tor</code> . |
|
1532 |
+To get to it, press cmd-shift-g while in Finder and copy/paste that directory |
|
1533 |
+into the box that appears. |
|
1534 | 1534 |
</p> |
1535 | 1535 |
<p> |
1536 |
-Tor looks for the torrc file in <code>/usr/local/etc/tor/torrc</code> if you compiled tor from source, and <code>/etc/tor/torrc</code> or <code>/etc/torrc</code> if you installed a pre-built package.</p> |
|
1536 |
+Otherwise, if you are using Tor without Tor Browser, it looks for the |
|
1537 |
+torrc file in <code>/usr/local/etc/tor/torrc</code> if you compiled tor |
|
1538 |
+from source, and <code>/etc/tor/torrc</code> or <code>/etc/torrc</code> |
|
1539 |
+if you installed a pre-built package. |
|
1540 |
+</p> |
|
1537 | 1541 |
|
1538 | 1542 |
<p> |
1539 | 1543 |
Once you've created or changed your torrc file, you will need to restart |
... | ... |
@@ -1389,10 +1389,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed |
1389 | 1389 |
(Vidalia) go?</a></h3> |
1390 | 1390 |
|
1391 | 1391 |
<p>Vidalia has been replaced with Tor Launcher, which is a Firefox |
1392 |
- extension that provides similar functionality. Unfortunately, circuit |
|
1393 |
- status reporting is still missing, but we are <a |
|
1394 |
- href="https://trac.torproject.org/projects/tor/ticket/8641">working |
|
1395 |
- on providing it</a>. </p> |
|
1392 |
+ extension that provides similar functionality.</p> |
|
1396 | 1393 |
|
1397 | 1394 |
<hr> |
1398 | 1395 |
|
... | ... |
@@ -2192,7 +2192,7 @@ too. |
2192 | 2192 |
second). For example, you might want to choose "BandwidthRate 10 MBytes" |
2193 | 2193 |
for 10 megabytes per second (a fast connection), or "BandwidthRate 500 |
2194 | 2194 |
KBytes" for 500 kilobytes per second (a decent cable connection). |
2195 |
- The minimum BandwidthRate setting is 20 kilobytes per second. |
|
2195 |
+ The minimum BandwidthRate setting is 75 kilobytes per second. |
|
2196 | 2196 |
</li> |
2197 | 2197 |
<li> |
2198 | 2198 |
BandwidthBurst is a pool of bytes used to fulfill requests during |
... | ... |
@@ -873,8 +873,8 @@ executive |
873 | 873 |
|
874 | 874 |
<p>No, it doesn't. You need to use a separate program that understands |
875 | 875 |
your application and protocol and knows how to clean or "scrub" the data |
876 |
- it sends. The Tor Browser tries to keep application-level data, |
|
877 |
- like the user-agent string, uniform for all users. The Tor Browser can't |
|
876 |
+ it sends. Tor Browser tries to keep application-level data, |
|
877 |
+ like the user-agent string, uniform for all users. Tor Browser can't |
|
878 | 878 |
do anything about text that you type into forms, though. <a |
879 | 879 |
href="<page download/download-easy>#warning">Be |
880 | 880 |
careful and be smart.</a> |
... | ... |
@@ -1060,7 +1060,7 @@ from the graphical interface. Open "Files" (Unity's explorer), open |
1060 | 1060 |
Preferences-> Behavior Tab -> Set "Run executable text files when they are |
1061 | 1061 |
opened" to "Ask every time", then OK. |
1062 | 1062 |
</p> |
1063 |
-<p>You can also start the Tor Browser from the command line by running </p> |
|
1063 |
+<p>You can also start Tor Browser from the command line by running </p> |
|
1064 | 1064 |
<pre>./start-tor-browser</pre> |
1065 | 1065 |
<p> |
1066 | 1066 |
from inside the Tor Browser directory. |
... | ... |
@@ -1104,7 +1104,7 @@ issue. |
1104 | 1104 |
Firefox extensions?</a></h3> |
1105 | 1105 |
|
1106 | 1106 |
<p> |
1107 |
-The Tor Browser is free software, so there is nothing preventing you from |
|
1107 |
+Tor Browser is free software, so there is nothing preventing you from |
|
1108 | 1108 |
modifying it any way you like. However, we do not recommend installing any |
1109 | 1109 |
additional Firefox add-ons with Tor Browser. Add-ons can break |
1110 | 1110 |
your anonymity in a number of ways, including browser fingerprinting and |
... | ... |
@@ -1112,7 +1112,7 @@ bypassing proxy settings. |
1112 | 1112 |
</p> |
1113 | 1113 |
<p> |
1114 | 1114 |
Some people have suggested we include ad-blocking software or |
1115 |
-anti-tracking software with the Tor Browser. Right now, we do not |
|
1115 |
+anti-tracking software with Tor Browser. Right now, we do not |
|
1116 | 1116 |
think that's such a good idea. Tor Browser aims to provide |
1117 | 1117 |
sufficient privacy that additional add-ons to stop ads and trackers are |
1118 |