Andrew Lewman commited on 2010-05-18 21:19:08
Zeige 10 geänderte Dateien mit 23 Einfügungen und 22 Löschungen.
... | ... |
@@ -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://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">the |
|
37 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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 |
... | ... |
@@ -150,7 +150,7 @@ docs/tor-doc-relay>">normal Tor relay</a>, you should |
150 | 150 |
run a bridge relay. You can configure it either way: |
151 | 151 |
<ul> |
152 | 152 |
<li> manually <a |
153 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">edit |
|
153 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit |
|
154 | 154 |
your torrc file</a> to be just these four lines:<br /> |
155 | 155 |
<pre><code> |
156 | 156 |
SocksPort 0 |
... | ... |
@@ -166,7 +166,7 @@ settings page" /></li> |
166 | 166 |
|
167 | 167 |
<p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors |
168 | 168 |
on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a |
169 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">some |
|
169 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some |
|
170 | 170 |
complex port forwarding</a>. |
171 | 171 |
</p> |
172 | 172 |
|
... | ... |
@@ -38,7 +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://wiki.torproject.org/noreply/TheOnionRouter">the |
|
41 |
+sections on <a href="https://trac.torproject.org/projects/tor/wiki">the |
|
42 | 42 |
Tor wiki</a> first.</li> |
43 | 43 |
<li><tt>tor-volunteer</tt> wants to hear about your documents, patches, |
44 | 44 |
testing, experiences with supporting applications, and so forth inspired |
... | ... |
@@ -43,7 +43,7 @@ can screw up your anonymity. |
43 | 43 |
|
44 | 44 |
<li> |
45 | 45 |
Our <a |
46 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ">FAQ</a> |
|
46 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a> |
|
47 | 47 |
covers all sorts of topics, including questions about setting up a client |
48 | 48 |
or relay, concerns about anonymity attacks, why we didn't build Tor in |
49 | 49 |
other ways, etc. |
... | ... |
@@ -56,7 +56,7 @@ that arise from the Tor project in the US. |
56 | 56 |
|
57 | 57 |
<li>The <a href="<page tor-manual>">manual</a> |
58 | 58 |
lists all the possible entries you can put in your <a |
59 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc |
|
59 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc |
|
60 | 60 |
file</a>. We also provide a <a href="<page tor-manual-dev>">manual for |
61 | 61 |
the development version of Tor</a>.</li> |
62 | 62 |
|
... | ... |
@@ -64,7 +64,7 @@ the development version of Tor</a>.</li> |
64 | 64 |
operators, and developers) |
65 | 65 |
at <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>. If |
66 | 66 |
you have a bug, especially a crash bug, read <a |
67 |
-href="https://wiki.torproject.org/wiki/TheOnionRouter/TorFAQ#RelayCrashing">how |
|
67 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how |
|
68 | 68 |
to report a Tor bug</a> first and then tell us as much information |
69 | 69 |
about it as you can in |
70 | 70 |
<a href="https://bugs.torproject.org/tor">our bugtracker</a>. |
... | ... |
@@ -237,11 +237,11 @@ new specifications and proposed changes</a></li> |
237 | 237 |
<a id="NeatLinks"></a> |
238 | 238 |
<h2><a class="anchor" href="#NeatLinks">Neat Links</a></h2> |
239 | 239 |
<ul> |
240 |
-<li>The <a href="https://wiki.torproject.org/noreply/TheOnionRouter">Tor |
|
240 |
+<li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor |
|
241 | 241 |
wiki</a> provides a plethora of helpful contributions from Tor |
242 | 242 |
users. Check it out!</li> |
243 | 243 |
<li><a |
244 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">A |
|
244 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A |
|
245 | 245 |
list of supporting programs you might want to use in association with |
246 | 246 |
Tor</a>.</li> |
247 | 247 |
<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 && make && 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://wiki.torproject.org/noreply/TheOnionRouter/OpenbsdChrootedTor">Guide to chrooting Tor in OpenBSD</a> |
|
65 |
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">it |
|
214 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">it |
|
235 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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 — |
... | ... |
@@ -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://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#EntryGuards">entry |
|
109 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity"> |
|
62 |
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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>, |
... | ... |
@@ -234,7 +234,7 @@ us!)</dt><dd>The most dedicated bug reporter we've ever heard from. He |
234 | 234 |
must read Tor source code every day over breakfast.</dd> |
235 | 235 |
<dt>tup (another pseudonym)</dt><dd>Periodically adds new features for |
236 | 236 |
making Tor easier to use as a <a |
237 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TransparentProxy">transparent |
|
237 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TransparentProxy">transparent |
|
238 | 238 |
proxy</a>. Also maintains the <a |
239 | 239 |
href="http://p56soo2ibjkx23xo.onion/">TorDNSEL code</a>.</dd> |
240 | 240 |
<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://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">support |
|
24 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/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://wiki.torproject.org/noreply/TheOnionRouter/TorShirt">in |
|
41 |
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorShirt">in |
|
42 | 42 |
action</a> — add your own photos there too. |
43 | 43 |
</p> |
44 | 44 |
|
... | ... |
@@ -35,9 +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://wiki.torproject.org/wiki/TheOnionRouter/TorifyHOWTO">our |
|
38 |
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">our |
|
39 | 39 |
list of programs</a> that can be configured to use Tor.</li> |
40 |
-<li>We have a huge list of <a href="https://wiki.torproject.org/noreply/TheOnionRouter/SupportPrograms">potentially useful |
|
40 |
+<li>We have a huge list of <a |
|
41 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">potentially useful |
|
41 | 42 |
programs that interface to Tor</a>. Which ones are useful in which |
42 | 43 |
situations? Please help us test them out and document your results.</li> |
43 | 44 |
</ol> |
... | ... |
@@ -45,7 +46,7 @@ situations? Please help us test them out and document your results.</li> |
45 | 46 |
<a id="Advocacy"></a> |
46 | 47 |
<h2><a class="anchor" href="#Advocacy">Advocacy</a></h2> |
47 | 48 |
<ol> |
48 |
-<li>Create a <a href="https://wiki.torproject.org/noreply/CommunityLogos">community logo</a> under a Creative Commons license that all can use and modify</li> |
|
49 |
+<li>Create a <a href="https://trac.torproject.org/projects/tor/wiki/CommunityLogos">community logo</a> under a Creative Commons license that all can use and modify</li> |
|
49 | 50 |
<li>Create a presentation that can be used for various user group meetings around the world</li> |
50 | 51 |
<li>Create a video about the positive uses of Tor, what Tor is, or how |
51 | 52 |
to use it. Some have already |
... | ... |
@@ -836,7 +837,7 @@ might also be short on developers. |
836 | 837 |
Windows, Tor uses the standard <tt>select()</tt> system |
837 | 838 |
call, which uses space in the non-page pool. This means |
838 | 839 |
that a medium sized Tor relay will empty the non-page pool, <a |
839 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/WindowsBufferProblems">causing |
|
840 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/WindowsBufferProblems">causing |
|
840 | 841 |
havoc and system crashes</a>. We should probably be using overlapped IO |
841 | 842 |
instead. One solution would be to teach <a |
842 | 843 |
href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use |
... | ... |
@@ -873,7 +874,7 @@ getting credit when we put out a new release because of you!</li> |
873 | 874 |
encryption. This is nice and simple, but it means all cells |
874 | 875 |
on a link are delayed when a single packet gets dropped, and |
875 | 876 |
it means we can only reasonably support TCP streams. We have a <a |
876 |
-href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list |
|
877 |
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#YoushouldtransportallIPpacketsnotjustTCPpackets.">list |
|
877 | 878 |
of reasons why we haven't shifted to UDP transport</a>, but it would |
878 | 879 |
be great to see that list get shorter. We also have a proposed <a |
879 | 880 |
href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification |
880 | 881 |