Replace links to wiki with new <wiki> shortcut for easier maintenance/translation.
Sebastian Hahn

Sebastian Hahn commited on 2010-08-19 20:56:40
Zeige 13 geänderte Dateien mit 38 Einfügungen und 39 Löschungen.


Patch contributed by Simon Ruderich <simon@ruderich.org>
... ...
@@ -34,7 +34,7 @@ Note that it's also possible that Tor is non-functional for other
34 34
 reasons. The latest version of <a href="<page torbrowser/index>">The
35 35
 Tor Browser Bundle</a> on Windows tries to give you better hints about
36 36
 why Tor is having problems connecting. You should also read <a
37
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.">the
37
+href="<wiki>TorFAQ#IinstalledTorandPolipobutitsnotworking.">the
38 38
 FAQ about problems with running Tor properly</a> when you have issues.
39 39
 If you feel that the issue is clearly blocking, or you'd simply like to try
40 40
 because you're unsure or feeling adventurous, please read on. Ensure
... ...
@@ -146,7 +146,7 @@ docs/tor-doc-relay>">normal Tor relay</a>, you should
146 146
 run a bridge relay. You can configure it either way:
147 147
 <ul>
148 148
 <li> manually <a
149
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
149
+href="<wiki>TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
150 150
 your torrc file</a> to be just these four lines:<br />
151 151
 <pre><code>
152 152
 SocksPort 0
... ...
@@ -162,7 +162,7 @@ settings page" /></li>
162 162
 
163 163
 <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
164 164
 on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
165
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some
165
+href="<wiki>TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some
166 166
 complex port forwarding</a>.
167 167
 </p>
168 168
 
... ...
@@ -38,8 +38,7 @@ problem with your relay.</li>
38 38
 <li><tt>tor-webmaster</tt> can fix typos on the website, change wrong
39 39
 statements or directions on the website, and add new sections and
40 40
 paragraphs that you send us. You might want to make a draft of your new
41
-sections on <a href="https://trac.torproject.org/projects/tor/wiki">the
42
-Tor wiki</a> first.</li>
41
+sections on <a href="<wiki>">the Tor wiki</a> first.</li>
43 42
 <li><tt>tor-volunteer</tt> wants to hear about your documents, patches,
44 43
 testing, experiences with supporting applications, and so forth inspired
45 44
 by our <a href="<page volunteer>">volunteer page</a> (or other problems
... ...
@@ -42,8 +42,7 @@ can screw up your anonymity.
42 42
 </li>
43 43
 
44 44
 <li>
45
-Our <a
46
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a>
45
+Our <a href="<wiki>TorFAQ">FAQ</a>
47 46
 covers all sorts of topics, including questions about setting up a client
48 47
 or relay, concerns about anonymity attacks, why we didn't build Tor in
49 48
 other ways, etc.
... ...
@@ -56,7 +55,7 @@ that arise from the Tor project in the US.
56 55
 
57 56
 <li>The <a href="<page tor-manual>">manual</a>
58 57
 lists all the possible entries you can put in your <a
59
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
58
+href="<wiki>TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
60 59
 file</a>. We also provide a <a href="<page tor-manual-dev>">manual for
61 60
 the development version of Tor</a>.</li>
62 61
 
... ...
@@ -64,7 +63,7 @@ the development version of Tor</a>.</li>
64 63
 operators, and developers)
65 64
 at <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>. If
66 65
 you have a bug, especially a crash bug, read <a
67
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how
66
+href="<wiki>TorFAQ#MyTorkeepscrashing.">how
68 67
 to report a Tor bug</a> first and then tell us as much information
69 68
 about it as you can in
70 69
 <a href="https://bugs.torproject.org/tor">our bugtracker</a>.
... ...
@@ -237,11 +236,11 @@ new specifications and proposed changes</a></li>
237 236
 <a id="NeatLinks"></a>
238 237
 <h2><a class="anchor" href="#NeatLinks">Neat Links</a></h2>
239 238
 <ul>
240
-<li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor
239
+<li>The <a href="<wiki>">Tor
241 240
 wiki</a> provides a plethora of helpful contributions from Tor
242 241
 users. Check it out!</li>
243 242
 <li><a
244
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A
243
+href="<wiki>SupportPrograms">A
245 244
 list of supporting programs you might want to use in association with
246 245
 Tor</a>.</li>
247 246
 <li><a href="https://check.torproject.org/">The
... ...
@@ -62,7 +62,7 @@ Please take time to read the <a href="<page download-unix>#Warning">warning</a>
62 62
 <td colspan="2"><kbd>cd /usr/ports/net/tor &amp;&amp; make &amp;&amp; make install</kbd></td>
63 63
 <td>
64 64
 <a href="<page docs/tor-doc-unix>">Linux/BSD/Unix</a><br />
65
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/OpenbsdChrootedTor">Guide to chrooting Tor in OpenBSD</a>
65
+<a href="<wiki>OpenbsdChrootedTor">Guide to chrooting Tor in OpenBSD</a>
66 66
 </td>
67 67
 </tr>
68 68
 
... ...
@@ -211,7 +211,7 @@ protect any cookies you do not want to lose.
211 211
 <li>
212 212
 Tor anonymizes the origin of your traffic,
213 213
 and it encrypts everything inside the Tor network, but <a
214
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ExitEavesdroppers">it
214
+href="<wiki>TorFAQ#ExitEavesdroppers">it
215 215
 can't encrypt your traffic between the Tor network and its final
216 216
 destination.</a>
217 217
 If you are communicating sensitive information, you should use as much
... ...
@@ -232,7 +232,7 @@ protect any cookies you do not want to lose.
232 232
 Tor anonymizes the origin of your traffic, and it encrypts everything
233 233
 between you and the Tor network and everything inside the Tor network,
234 234
 but <a
235
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#SoImtotallyanonymousifIuseTor">it
235
+href="<wiki>TorFAQ#SoImtotallyanonymousifIuseTor">it
236 236
 can't encrypt your traffic between the Tor network and its final
237 237
 destination.</a> If you are communicating sensitive information, you
238 238
 should use as much care as you would on the normal scary Internet &mdash;
... ...
@@ -231,8 +231,7 @@ will help show them that we are not all evil people. </p>
231 231
 
232 232
 <p>Finally, if you become aware of an IRC network that seems to be
233 233
 blocking Tor, or a single Tor exit node, please put that information on <a
234
-href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc">The Tor
235
-IRC block tracker</a>
234
+href="<wiki>BlockingIrc">The Tor IRC block tracker</a>
236 235
 so that others can share.  At least one IRC network consults that page
237 236
 to unblock exit nodes that have been blocked inadvertently. </p>
238 237
 
... ...
@@ -79,7 +79,7 @@ relay?</a></li>
79 79
 </ul>
80 80
 
81 81
 <p>For other questions not yet on this version of the FAQ, see the <a
82
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki
82
+href="<wiki>TorFAQ">wiki
83 83
 FAQ</a> for now.</p>
84 84
 
85 85
 <hr />
... ...
@@ -162,9 +162,9 @@ There are plenty of other programs you can use with Tor,
162 162
 but we haven't researched the application-level anonymity
163 163
 issues on them well enough to be able to recommend a safe
164 164
 configuration. Our wiki has a list of instructions for <a
165
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying
165
+href="<wiki>TorifyHOWTO">Torifying
166 166
 specific applications</a>. There's also a <a
167
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list
167
+href="<wiki>SupportPrograms">list
168 168
 of applications that help you direct your traffic through Tor</a>.
169 169
 Please add to these lists and help us keep them accurate!
170 170
 </p>
... ...
@@ -392,7 +392,7 @@ then we can focus better on fixing them.
392 392
 <li>
393 393
 There are some steps that individuals
394 394
 can take to improve their Tor performance. <a
395
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You
395
+href="<wiki>FireFoxTorPerf">You
396 396
 can configure your Firefox to handle Tor better</a>, <a
397 397
 href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
398 398
 Polipo with Tor</a>, or you can try <a href="<page download>">upgrading
... ...
@@ -752,7 +752,7 @@ talk to the already running Tor. Vidalia generates a random password,
752 752
 but it is different than the saved password in the Tor service.
753 753
 <br />
754 754
 You need to reconfigure Tor to not be a service. See the FAQ entry on
755
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#HowdoIrunmyTorrelayasanNTservice">running Tor as a Windows NT service</a>
755
+<a href="<wiki>TorFAQ#HowdoIrunmyTorrelayasanNTservice">running Tor as a Windows NT service</a>
756 756
 for more information on how to remove the Tor service.
757 757
 </li>
758 758
 </ol>
... ...
@@ -826,11 +826,11 @@ We aim to make setting up a Tor relay easy and convenient:
826 826
 
827 827
 <ul>
828 828
 <li>Tor has built-in support for <a
829
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth">
829
+href="<wiki>TorFAQ#LimitBandwidth">
830 830
 rate limiting</a>. Further, if you have a fast
831 831
 link but want to limit the number of bytes per
832 832
 day (or week or month) that you donate, check out the <a
833
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation
833
+href="<wiki>TorFAQ#Hibernation">hibernation
834 834
 feature</a>.
835 835
 </li>
836 836
 <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
... ...
@@ -849,7 +849,7 @@ leave the Address config option blank, and Tor will try to guess.
849 849
 <li>If your relay is behind a NAT and it doesn't know its public
850 850
 IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
851 851
 forwarding. Forwarding TCP connections is system dependent but 
852
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> 
852
+<a href="<wiki>TorFAQ#ServerForFirewalledClients">this FAQ entry</a>
853 853
 offers some examples on how to do this.
854 854
 </li>
855 855
 <li>Your relay will passively estimate and advertise its recent
... ...
@@ -885,12 +885,12 @@ for running an exit node with minimal harassment</a>.
885 885
 
886 886
 <p>
887 887
 The default exit policy allows access to many popular services (e.g. web browsing), but 
888
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
888
+<a href="<wiki>TorFAQ#DefaultPorts">restricts</a>
889 889
 some due to abuse potential (e.g. mail) and some since
890 890
 the Tor network can't handle the load (e.g. default
891 891
 file-sharing ports). You can change your exit policy
892 892
 using Vidalia's "Sharing" tab, or by manually editing your 
893
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
893
+<a href="<wiki>TorFAQ#torrc">torrc</a>
894 894
 file. If you want to avoid most if not all abuse potential, set it to
895 895
 "reject *:*" (or un-check all the boxes in Vidalia). This setting means
896 896
 that your relay will be used for relaying traffic inside the Tor network,
... ...
@@ -970,7 +970,7 @@ this feature.</li>
970 970
 <li>If you're running on Solaris, OpenBSD, NetBSD, or
971 971
 old FreeBSD, Tor is probably forking separate processes
972 972
 rather than using threads. Consider switching to a <a
973
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better
973
+href="<wiki>TorFAQ#RelayOS">better
974 974
 operating system</a>.</li>
975 975
 
976 976
 <li>If you still can't handle the memory load, consider reducing the
... ...
@@ -1080,7 +1080,7 @@ user be a relay.</a></h3>
1080 1080
 
1081 1081
 <p>
1082 1082
 Requiring every Tor user to be a relay would help with scaling the
1083
-network to handle all our users, and <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor
1083
+network to handle all our users, and <a href="<wiki>TorFAQ#RelayAnonymity">running a Tor
1084 1084
 relay may help your anonymity</a>. However, many Tor users cannot be good
1085 1085
 relays &mdash; for example, some Tor clients operate from behind restrictive
1086 1086
 firewalls, connect via modem, or otherwise aren't in a position where they
... ...
@@ -1117,7 +1117,7 @@ the right amount of bandwidth to allow. See item #7 on the
1117 1117
 <a href="<page volunteer>#Research">research section of the
1118 1118
 volunteer page</a>: "Tor doesn't work very well when relays
1119 1119
 have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a
1120
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1120
+href="<wiki>TorFAQ#TransportIPnotTCP">switching
1121 1121
 to UDP transport</a> is the simplest answer here &mdash; which alas is
1122 1122
 not a very simple answer at all.
1123 1123
 </p>
... ...
@@ -1178,7 +1178,7 @@ exit relay?</a></h3>
1178 1178
 
1179 1179
 <p>
1180 1180
 A collection of templates for successfully responding to ISPs is <a
1181
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected
1181
+href="<wiki>TorAbuseTemplates">collected
1182 1182
 here</a>.
1183 1183
 </p>
1184 1184
 
... ...
@@ -106,7 +106,7 @@ it in a rendezvous message.
106 106
 <p>
107 107
 At this point it is of special importance that the hidden service sticks to
108 108
 the same set of <a
109
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Whatsthisaboutentryguardformerlyknownashelpernodes">entry
109
+href="<wiki>TorFAQ#Whatsthisaboutentryguardformerlyknownashelpernodes">entry
110 110
 guards</a> when creating new circuits. Otherwise an attacker
111 111
 could run his own relay and force a hidden service to create an arbitrary
112 112
 number of circuits in the hope that the corrupt relay is picked as entry
... ...
@@ -59,7 +59,7 @@ Tor's security improves as its user
59 59
 base grows and as more people volunteer to
60 60
 <a href="<page docs/tor-doc-relay>">run relays</a>. (It isn't
61 61
 nearly as hard to set up as you might think, and can significantly
62
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">
62
+<a href="<wiki>TorFAQ#RelayAnonymity">
63 63
 enhance your own security</a>.)
64 64
 If running a relay isn't for you, we need
65 65
 <a href="<page volunteer>">help with many other aspects of the project</a>,
... ...
@@ -250,7 +250,7 @@ us!)</dt><dd>The most dedicated bug reporter we've ever heard from. He
250 250
 must read Tor source code every day over breakfast.</dd>
251 251
 <dt>tup (another pseudonym)</dt><dd>Periodically adds new features for
252 252
 making Tor easier to use as a <a
253
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TransparentProxy">transparent
253
+href="<wiki>TransparentProxy">transparent
254 254
 proxy</a>. Also maintains the <a
255 255
 href="http://p56soo2ibjkx23xo.onion/">TorDNSEL code</a>.</dd>
256 256
 <dt>Kyle Williams</dt><dd>Developer for
... ...
@@ -21,7 +21,7 @@ allow exits to port 80 and you average 100 KB/s traffic, or if you're
21 21
 not an exit but you average 500 KB/s traffic.</li>
22 22
 <li>Help out in <a href="<page volunteer>">other ways</a>. <a href="<page
23 23
 translation>">Maintain a translation for the website</a>. Write a good <a
24
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">support
24
+href="<wiki>SupportPrograms">support
25 25
 program and get a lot of people to use it</a>. Do research on Tor
26 26
 and anonymity, solve some of <a href="https://bugs.torproject.org/">our
27 27
 bugs</a>, or establish yourself as a Tor advocate.
... ...
@@ -38,7 +38,7 @@ and a shipping address.
38 38
 <p>
39 39
 You can choose between the traditional black and our conversation-starting
40 40
 bright green. You can also see the shirts
41
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorShirt">in
41
+<a href="<wiki>TorShirt">in
42 42
 action</a> &mdash; add your own photos there too.
43 43
 </p>
44 44
 
... ...
@@ -35,10 +35,10 @@ languages. See the <a href="<page translation>">translation
35 35
 guidelines</a> if you want to help out. We especially need Arabic or
36 36
 Farsi translations, for the many Tor users in censored areas.</li>
37 37
 <li>Evaluate and document
38
-<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">our
38
+<a href="<wiki>TorifyHOWTO">our
39 39
 list of programs</a> that can be configured to use Tor.</li>
40 40
 <li>We have a huge list of <a
41
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">potentially useful
41
+href="<wiki>SupportPrograms">potentially useful
42 42
 programs that interface to Tor</a>. Which ones are useful in which
43 43
 situations? Please help us test them out and document your results.</li>
44 44
 </ol>
... ...
@@ -689,7 +689,7 @@ might also be short on developers.
689 689
 Windows, Tor uses the standard <tt>select()</tt> system
690 690
 call, which uses space in the non-page pool. This means
691 691
 that a medium sized Tor relay will empty the non-page pool, <a
692
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/WindowsBufferProblems">causing
692
+href="<wiki>WindowsBufferProblems">causing
693 693
 havoc and system crashes</a>. We should probably be using overlapped IO
694 694
 instead. One solution would be to teach <a
695 695
 href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
... ...
@@ -726,7 +726,7 @@ getting credit when we put out a new release because of you!</li>
726 726
 encryption. This is nice and simple, but it means all cells
727 727
 on a link are delayed when a single packet gets dropped, and
728 728
 it means we can only reasonably support TCP streams. We have a <a
729
-href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#YoushouldtransportallIPpacketsnotjustTCPpackets.">list
729
+href="<wiki>TorFAQ#YoushouldtransportallIPpacketsnotjustTCPpackets.">list
730 730
 of reasons why we haven't shifted to UDP transport</a>, but it would
731 731
 be great to see that list get shorter. We also have a proposed <a
732 732
 href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
... ...
@@ -32,3 +32,5 @@
32 32
 		warn "$WML_SRC_FILENAME has a [page $page] (parses to docdir: $(DOCROOT)/; dir: $dir; base: $base -> $(DOCROOT)/$dir/$lang/$base.wml), but that doesn't exist.";
33 33
 	};
34 34
 }:></define-tag>
35
+
36
+<define-tag wiki whitespace=delete>https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/</define-tag>
35 37