Roger Dingledine commited on 2010-10-10 01:35:02
Zeige 7 geänderte Dateien mit 34 Einfügungen und 35 Löschungen.
... | ... |
@@ -38,7 +38,7 @@ |
38 | 38 |
reasons. The latest version of <a href="<page projects/torbrowser>">The |
39 | 39 |
Tor Browser Bundle</a> on Windows tries to give you better hints about |
40 | 40 |
why Tor is having problems connecting. You should also read <a |
41 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.">the |
|
41 |
+ href="<wikifaq>#IinstalledTorandPolipobutitsnotworking.">the |
|
42 | 42 |
FAQ about problems with running Tor properly</a> when you have issues. |
43 | 43 |
If you feel that the issue is clearly blocking, or you'd simply like to try |
44 | 44 |
because you're unsure or feeling adventurous, please read on. Ensure |
... | ... |
@@ -154,7 +154,7 @@ |
154 | 154 |
run a bridge relay. You can configure it either way: |
155 | 155 |
<ul> |
156 | 156 |
<li> manually <a |
157 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit |
|
157 |
+ href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit |
|
158 | 158 |
your torrc file</a> to be just these four lines:<br /> |
159 | 159 |
<pre><code> |
160 | 160 |
SocksPort 0 |
... | ... |
@@ -170,7 +170,7 @@ |
170 | 170 |
|
171 | 171 |
<p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors |
172 | 172 |
on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a |
173 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some |
|
173 |
+ href="<wikifaq>#Myfirewallonlyallowsafewoutgoingports.">some |
|
174 | 174 |
complex port forwarding</a>. |
175 | 175 |
</p> |
176 | 176 |
|
... | ... |
@@ -46,7 +46,7 @@ |
46 | 46 |
|
47 | 47 |
<li> |
48 | 48 |
Our <a |
49 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a> |
|
49 |
+ href="<wikifaq>">FAQ</a> |
|
50 | 50 |
covers all sorts of topics, including questions about setting up a client |
51 | 51 |
or relay, concerns about anonymity attacks, why we didn't build Tor in |
52 | 52 |
other ways, etc. |
... | ... |
@@ -59,7 +59,7 @@ |
59 | 59 |
|
60 | 60 |
<li>The <a href="<page docs/tor-manual>">manual</a> |
61 | 61 |
lists all the possible entries you can put in your <a |
62 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc |
|
62 |
+ href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc |
|
63 | 63 |
file</a>. We also provide a <a href="<page docs/tor-manual-dev>">manual for |
64 | 64 |
the development version of Tor</a>.</li> |
65 | 65 |
|
... | ... |
@@ -67,7 +67,7 @@ |
67 | 67 |
operators, and developers) |
68 | 68 |
at <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>. If |
69 | 69 |
you have a bug, especially a crash bug, read <a |
70 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how |
|
70 |
+ href="<wikifaq>#MyTorkeepscrashing.">how |
|
71 | 71 |
to report a Tor bug</a> first and then tell us as much information |
72 | 72 |
about it as you can in |
73 | 73 |
<a href="https://bugs.torproject.org/tor">our bugtracker</a>. |
... | ... |
@@ -240,11 +240,11 @@ |
240 | 240 |
<a id="NeatLinks"></a> |
241 | 241 |
<h1><a class="anchor" href="#NeatLinks">Neat Links</a></h1> |
242 | 242 |
<ul> |
243 |
- <li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor |
|
243 |
+ <li>The <a href="<wiki>">Tor |
|
244 | 244 |
wiki</a> provides a plethora of helpful contributions from Tor |
245 | 245 |
users. Check it out!</li> |
246 | 246 |
<li><a |
247 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A |
|
247 |
+ href="<wiki>TheOnionRouter/SupportPrograms">A |
|
248 | 248 |
list of supporting programs you might want to use in association with |
249 | 249 |
Tor</a>.</li> |
250 | 250 |
<li><a href="https://check.torproject.org/">The |
... | ... |
@@ -114,7 +114,7 @@ |
114 | 114 |
<h3><a class="anchor" href="#ExitPolicies">How do Tor exit policies work?</a></h3> |
115 | 115 |
|
116 | 116 |
<p> |
117 |
- <a href="<wiki>TorFAQ#ExitPolicies">See the FAQ</a> |
|
117 |
+ <a href="<wikifaq>#ExitPolicies">See the FAQ</a> |
|
118 | 118 |
</p> |
119 | 119 |
|
120 | 120 |
<a id="HowMuchAbuse"></a> |
... | ... |
@@ -234,7 +234,7 @@ |
234 | 234 |
|
235 | 235 |
<p>Finally, if you become aware of an IRC network that seems to be |
236 | 236 |
blocking Tor, or a single Tor exit node, please put that information on <a |
237 |
- href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc">The Tor |
|
237 |
+ href="<wiki>TheOnionRouter/BlockingIrc">The Tor |
|
238 | 238 |
IRC block tracker</a> |
239 | 239 |
so that others can share. At least one IRC network consults that page |
240 | 240 |
to unblock exit nodes that have been blocked inadvertently. </p> |
... | ... |
@@ -295,7 +295,7 @@ |
295 | 295 |
not so different from AOL in this respect.</p> |
296 | 296 |
|
297 | 297 |
<p>Lastly, please remember that Tor relays have <a |
298 |
- href="<wiki>#ExitPolicies">individual exit policies</a>. Many Tor relays do |
|
298 |
+ href="<wikifaq>#ExitPolicies">individual exit policies</a>. Many Tor relays do |
|
299 | 299 |
not allow exiting connections at all. Many of those that do allow some |
300 | 300 |
exit connections might already disallow connections to |
301 | 301 |
your service. When you go about banning nodes, you should parse the |
... | ... |
@@ -81,8 +81,7 @@ |
81 | 81 |
</ul> |
82 | 82 |
|
83 | 83 |
<p>For other questions not yet on this version of the FAQ, see the <a |
84 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki |
|
85 |
- FAQ</a> for now.</p> |
|
84 |
+ href="<wikifaq>">wiki FAQ</a> for now.</p> |
|
86 | 85 |
|
87 | 86 |
<hr /> |
88 | 87 |
|
... | ... |
@@ -164,9 +163,9 @@ |
164 | 163 |
but we haven't researched the application-level anonymity |
165 | 164 |
issues on them well enough to be able to recommend a safe |
166 | 165 |
configuration. Our wiki has a list of instructions for <a |
167 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying |
|
166 |
+ href="<wiki>TheOnionRouter/TorifyHOWTO">Torifying |
|
168 | 167 |
specific applications</a>. There's also a <a |
169 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list |
|
168 |
+ href="<wiki>TheOnionRouter/SupportPrograms">list |
|
170 | 169 |
of applications that help you direct your traffic through Tor</a>. |
171 | 170 |
Please add to these lists and help us keep them accurate! |
172 | 171 |
</p> |
... | ... |
@@ -394,7 +393,7 @@ |
394 | 393 |
<li> |
395 | 394 |
There are some steps that individuals |
396 | 395 |
can take to improve their Tor performance. <a |
397 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You |
|
396 |
+ href="<wiki>TheOnionRouter/FireFoxTorPerf">You |
|
398 | 397 |
can configure your Firefox to handle Tor better</a>, <a |
399 | 398 |
href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use |
400 | 399 |
Polipo with Tor</a>, or you can try <a href="<page download/download>">upgrading |
... | ... |
@@ -698,7 +697,7 @@ |
698 | 697 |
Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent |
699 | 698 |
non-Tor traffic from accidentally leaving your computer. More information at |
700 | 699 |
<a |
701 |
- href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine">https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li> |
|
700 |
+ href="<wiki>VirtualPrivacyMachine"><wiki>VirtualPrivacyMachine</a>.</li> |
|
702 | 701 |
<li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather |
703 | 702 |
than Linux for maximum security. It was designed to be anonymous and secure |
704 | 703 |
from the ground up, and thus has some features and limitations not found in |
... | ... |
@@ -783,11 +782,11 @@ |
783 | 782 |
|
784 | 783 |
<ul> |
785 | 784 |
<li>Tor has built-in support for <a |
786 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth"> |
|
785 |
+ href="<wikifaq>#LimitBandwidth"> |
|
787 | 786 |
rate limiting</a>. Further, if you have a fast |
788 | 787 |
link but want to limit the number of bytes per |
789 | 788 |
day (or week or month) that you donate, check out the <a |
790 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation |
|
789 |
+ href="<wikifaq>#Hibernation">hibernation |
|
791 | 790 |
feature</a>. |
792 | 791 |
</li> |
793 | 792 |
<li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that |
... | ... |
@@ -806,7 +805,7 @@ |
806 | 805 |
<li>If your relay is behind a NAT and it doesn't know its public |
807 | 806 |
IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port |
808 | 807 |
forwarding. Forwarding TCP connections is system dependent but |
809 |
- <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> |
|
808 |
+ <a href="<wikifaq>#ServerForFirewalledClients">this FAQ entry</a> |
|
810 | 809 |
offers some examples on how to do this. |
811 | 810 |
</li> |
812 | 811 |
<li>Your relay will passively estimate and advertise its recent |
... | ... |
@@ -842,12 +841,12 @@ |
842 | 841 |
|
843 | 842 |
<p> |
844 | 843 |
The default exit policy allows access to many popular services (e.g. web browsing), but |
845 |
- <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a> |
|
844 |
+ <a href="<wikifaq>#DefaultPorts">restricts</a> |
|
846 | 845 |
some due to abuse potential (e.g. mail) and some since |
847 | 846 |
the Tor network can't handle the load (e.g. default |
848 | 847 |
file-sharing ports). You can change your exit policy |
849 | 848 |
using Vidalia's "Sharing" tab, or by manually editing your |
850 |
- <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a> |
|
849 |
+ <a href="<wikifaq>#torrc">torrc</a> |
|
851 | 850 |
file. If you want to avoid most if not all abuse potential, set it to |
852 | 851 |
"reject *:*" (or un-check all the boxes in Vidalia). This setting means |
853 | 852 |
that your relay will be used for relaying traffic inside the Tor network, |
... | ... |
@@ -927,7 +926,7 @@ |
927 | 926 |
<li>If you're running on Solaris, OpenBSD, NetBSD, or |
928 | 927 |
old FreeBSD, Tor is probably forking separate processes |
929 | 928 |
rather than using threads. Consider switching to a <a |
930 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better |
|
929 |
+ href="<wikifaq>#RelayOS">better |
|
931 | 930 |
operating system</a>.</li> |
932 | 931 |
|
933 | 932 |
<li>If you still can't handle the memory load, consider reducing the |
... | ... |
@@ -1037,7 +1036,7 @@ |
1037 | 1036 |
|
1038 | 1037 |
<p> |
1039 | 1038 |
Requiring every Tor user to be a relay would help with scaling the |
1040 |
- network to handle all our users, and <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor |
|
1039 |
+ network to handle all our users, and <a href="<wikifaq>#RelayAnonymity">running a Tor |
|
1041 | 1040 |
relay may help your anonymity</a>. However, many Tor users cannot be good |
1042 | 1041 |
relays — for example, some Tor clients operate from behind restrictive |
1043 | 1042 |
firewalls, connect via modem, or otherwise aren't in a position where they |
... | ... |
@@ -1074,7 +1073,7 @@ |
1074 | 1073 |
<a href="<page getinvolved/volunteer>#Research">research section of the |
1075 | 1074 |
volunteer page</a>: "Tor doesn't work very well when relays |
1076 | 1075 |
have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a |
1077 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching |
|
1076 |
+ href="<wikifaq>#TransportIPnotTCP">switching |
|
1078 | 1077 |
to UDP transport</a> is the simplest answer here — which alas is |
1079 | 1078 |
not a very simple answer at all. |
1080 | 1079 |
</p> |
... | ... |
@@ -1135,7 +1134,7 @@ |
1135 | 1134 |
|
1136 | 1135 |
<p> |
1137 | 1136 |
A collection of templates for successfully responding to ISPs is <a |
1138 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected |
|
1137 |
+ href="<wiki>TheOnionRouter/TorAbuseTemplates">collected |
|
1139 | 1138 |
here</a>. |
1140 | 1139 |
</p> |
1141 | 1140 |
|
... | ... |
@@ -110,7 +110,7 @@ |
110 | 110 |
<p> |
111 | 111 |
At this point it is of special importance that the hidden service sticks to |
112 | 112 |
the same set of <a |
113 |
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Whatsthisaboutentryguardformerlyknownashelpernodes">entry |
|
113 |
+ href="<wikifaq>#Whatsthisaboutentryguardformerlyknownashelpernodes">entry |
|
114 | 114 |
guards</a> when creating new circuits. Otherwise an attacker |
115 | 115 |
could run his own relay and force a hidden service to create an arbitrary |
116 | 116 |
number of circuits in the hope that the corrupt relay is picked as entry |
... | ... |
@@ -32,12 +32,12 @@ |
32 | 32 |
people who run relays, the faster the Tor network will be. If you have |
33 | 33 |
at least 20 kilobytes/s each way, please help out Tor by configuring your |
34 | 34 |
Tor to be a relay too. We have many features that make Tor relays easy |
35 |
- and convenient, including <a href="<wiki>TorFAQ#RelayFlexible">rate limiting |
|
35 |
+ and convenient, including <a href="<wikifaq>#RelayFlexible">rate limiting |
|
36 | 36 |
for bandwidth, exit policies so you can limit your exposure to abuse |
37 | 37 |
complaints, and support for dynamic IP addresses</a>. |
38 | 38 |
</p> |
39 | 39 |
|
40 |
- <p>You can run a Tor relay on <a href="<wiki>/TorFAQ#RelayOS">pretty |
|
40 |
+ <p>You can run a Tor relay on <a href="<wikifaq>#RelayOS">pretty |
|
41 | 41 |
much any</a> operating system. Tor relays work best on Linux, OS X Tiger |
42 | 42 |
or later, FreeBSD 5.x+, NetBSD 5.x+, and Windows Server 2003 or later. |
43 | 43 |
</p> |
... | ... |
@@ -83,7 +83,7 @@ |
83 | 83 |
<dt>Choose <tt>Relay Traffic for the Tor network</tt> if you |
84 | 84 |
want to be a public relay (recommended), or choose <tt>Help |
85 | 85 |
censored users reach the Tor network</tt> if you want to be a <a |
86 |
-href="<wiki>TorFAQ#RelayOrBridge">bridge</a> for users in countries that censor their Internet.</dt> |
|
86 |
+href="<wikifaq>#RelayOrBridge">bridge</a> for users in countries that censor their Internet.</dt> |
|
87 | 87 |
<dd><img alt="vidalia basic settings" src="../img/screenshot-win32-configure-relay-1.png"></dd> |
88 | 88 |
</li> |
89 | 89 |
|
... | ... |
@@ -100,7 +100,7 @@ href="<wiki>TorFAQ#RelayOrBridge">bridge</a> for users in countries that censor |
100 | 100 |
|
101 | 101 |
<li><dt>Choose the <tt>Exit Policies</tt> tab. If you want to allow others |
102 | 102 |
to use your relay for these services, don't change anything. Un-check |
103 |
- the services you don't want to allow people to <a href="<wiki>TorFAQ#ExitPolicies">reach from your relay</a>. If you want to be a non-exit relay, un-check all services.</dt> |
|
103 |
+ the services you don't want to allow people to <a href="<wikifaq>#ExitPolicies">reach from your relay</a>. If you want to be a non-exit relay, un-check all services.</dt> |
|
104 | 104 |
<dd><img alt="vidalia exit policies" src="../img/screenshot-win32-configure-relay-3.png"></dd> |
105 | 105 |
</li> |
106 | 106 |
|
... | ... |
@@ -111,9 +111,9 @@ href="<wiki>TorFAQ#RelayOrBridge">bridge</a> for users in countries that censor |
111 | 111 |
<br /> |
112 | 112 |
<strong>Manual Configuration</strong>: |
113 | 113 |
<ul> |
114 |
- <li>Edit the bottom part of <a href="<wiki>/TorFAQ#torrc">your torrc file</a>. If you want to be a public relay (recommended), |
|
115 |
- make sure to define ORPort and <a href="<wiki>TorFAQ#ExitPolicies">look at ExitPolicy</a>; otherwise |
|
116 |
- if you want to be a <a href="<wiki>TorFAQ#RelayOrBridge">bridge</a> |
|
114 |
+ <li>Edit the bottom part of <a href="<wikifaq>#torrc">your torrc file</a>. If you want to be a public relay (recommended), |
|
115 |
+ make sure to define ORPort and <a href="<wikifaq>#ExitPolicies">look at ExitPolicy</a>; otherwise |
|
116 |
+ if you want to be a <a href="<wikifaq>#RelayOrBridge">bridge</a> |
|
117 | 117 |
for users in countries that censor their Internet, |
118 | 118 |
just use <a href="<page docs/bridges>#RunningABridge">these lines</a>. |
119 | 119 |
</li> |
... | ... |
@@ -44,7 +44,7 @@ |
44 | 44 |
You should fill in "localhost" |
45 | 45 |
and "8118" to point the top four protocols to Polipo, as shown here. (Even |
46 | 46 |
though Polipo doesn't support FTP and Gopher, <a |
47 |
- href="wikifaq#FtpProxy">you |
|
47 |
+ href="<wikifaq>#FtpProxy">you |
|
48 | 48 |
should set them up anyway</a>.) You should also fill out the socks proxy entry to point directly to Tor ("localhost", "9050", and socks5) |
49 | 49 |
to cover protocols besides the first four. Then click "OK".</p> |
50 | 50 |
|
51 | 51 |