rewrite the links to the wiki.
Andrew Lewman

Andrew Lewman commited on 2010-05-18 21:29:03
Zeige 1 geänderte Dateien mit 14 Einfügungen und 14 Löschungen.

... ...
@@ -78,7 +78,7 @@ relay?</a></li>
78 78
 </ul>
79 79
 
80 80
 <p>For other questions not yet on this version of the FAQ, see the <a
81
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ">wiki
81
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki
82 82
 FAQ</a> for now.</p>
83 83
 
84 84
 <hr />
... ...
@@ -161,9 +161,9 @@ There are plenty of other programs you can use with Tor,
161 161
 but we haven't researched the application-level anonymity
162 162
 issues on them well enough to be able to recommend a safe
163 163
 configuration. Our wiki has a list of instructions for <a
164
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torifying
164
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying
165 165
 specific applications</a>. There's also a <a
166
-href="https://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">list
166
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list
167 167
 of applications that help you direct your traffic through Tor</a>.
168 168
 Please add to these lists and help us keep them accurate!
169 169
 </p>
... ...
@@ -391,7 +391,7 @@ then we can focus better on fixing them.
391 391
 <li>
392 392
 There are some steps that individuals
393 393
 can take to improve their Tor performance. <a
394
-href="https://wiki.torproject.org/noreply/TheOnionRouter/FireFoxTorPerf">You
394
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You
395 395
 can configure your Firefox to handle Tor better</a>, <a
396 396
 href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
397 397
 Polipo with Tor</a>, or you can try <a href="<page download>">upgrading
... ...
@@ -695,7 +695,7 @@ href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity
695 695
 Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
696 696
 non-Tor traffic from accidentally leaving your computer. More information at
697 697
 <a
698
-href="https://wiki.torproject.org/noreply/VirtualPrivacyMachine">https://wiki.torproject.org/noreply/VirtualPrivacyMachine</a>.</li>
698
+href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine">https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li>
699 699
 <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
700 700
 than Linux for maximum security. It was designed to be anonymous and secure
701 701
 from the ground up, and thus has some features and limitations not found in
... ...
@@ -780,11 +780,11 @@ We aim to make setting up a Tor relay easy and convenient:
780 780
 
781 781
 <ul>
782 782
 <li>Tor has built-in support for <a
783
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">
783
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth">
784 784
 rate limiting</a>. Further, if you have a fast
785 785
 link but want to limit the number of bytes per
786 786
 day (or week or month) that you donate, check out the <a
787
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Hibernation">hibernation
787
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation
788 788
 feature</a>.
789 789
 </li>
790 790
 <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
... ...
@@ -803,7 +803,7 @@ leave the Address config option blank, and Tor will try to guess.
803 803
 <li>If your relay is behind a NAT and it doesn't know its public
804 804
 IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
805 805
 forwarding. Forwarding TCP connections is system dependent but 
806
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> 
806
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> 
807 807
 offers some examples on how to do this.
808 808
 </li>
809 809
 <li>Your relay will passively estimate and advertise its recent
... ...
@@ -839,12 +839,12 @@ for running an exit node with minimal harassment</a>.
839 839
 
840 840
 <p>
841 841
 The default exit policy allows access to many popular services (e.g. web browsing), but 
842
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
842
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
843 843
 some due to abuse potential (e.g. mail) and some since
844 844
 the Tor network can't handle the load (e.g. default
845 845
 file-sharing ports). You can change your exit policy
846 846
 using Vidalia's "Sharing" tab, or by manually editing your 
847
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a>
847
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
848 848
 file. If you want to avoid most if not all abuse potential, set it to
849 849
 "reject *:*" (or un-check all the boxes in Vidalia). This setting means
850 850
 that your relay will be used for relaying traffic inside the Tor network,
... ...
@@ -924,7 +924,7 @@ this feature.</li>
924 924
 <li>If you're running on Solaris, OpenBSD, NetBSD, or
925 925
 old FreeBSD, Tor is probably forking separate processes
926 926
 rather than using threads. Consider switching to a <a
927
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">better
927
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better
928 928
 operating system</a>.</li>
929 929
 
930 930
 <li>If you still can't handle the memory load, consider reducing the
... ...
@@ -1034,7 +1034,7 @@ user be a relay.</a></h3>
1034 1034
 
1035 1035
 <p>
1036 1036
 Requiring every Tor user to be a relay would help with scaling the
1037
-network to handle all our users, and <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor
1037
+network to handle all our users, and <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor
1038 1038
 relay may help your anonymity</a>. However, many Tor users cannot be good
1039 1039
 relays &mdash; for example, some Tor clients operate from behind restrictive
1040 1040
 firewalls, connect via modem, or otherwise aren't in a position where they
... ...
@@ -1071,7 +1071,7 @@ the right amount of bandwidth to allow. See item #7 on the
1071 1071
 <a href="<page volunteer>#Research">research section of the
1072 1072
 volunteer page</a>: "Tor doesn't work very well when relays
1073 1073
 have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a
1074
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1074
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1075 1075
 to UDP transport</a> is the simplest answer here &mdash; which alas is
1076 1076
 not a very simple answer at all.
1077 1077
 </p>
... ...
@@ -1132,7 +1132,7 @@ exit relay?</a></h3>
1132 1132
 
1133 1133
 <p>
1134 1134
 A collection of templates for successfully responding to ISPs is <a
1135
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorAbuseTemplates">collected
1135
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected
1136 1136
 here</a>.
1137 1137
 </p>
1138 1138
 
1139 1139