[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r23527: {website} fix a bunch of broken links to the wiki and faq. use our tag (website/trunk/docs/en)
Author: arma
Date: 2010-10-09 23:35:02 +0000 (Sat, 09 Oct 2010)
New Revision: 23527
Modified:
website/trunk/docs/en/bridges.wml
website/trunk/docs/en/documentation.wml
website/trunk/docs/en/faq-abuse.wml
website/trunk/docs/en/faq.wml
website/trunk/docs/en/hidden-services.wml
website/trunk/docs/en/tor-doc-relay.wml
website/trunk/docs/en/tor-doc-web.wml
Log:
fix a bunch of broken links to the wiki and faq. use our tags more uniformly.
Modified: website/trunk/docs/en/bridges.wml
===================================================================
--- website/trunk/docs/en/bridges.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/bridges.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -38,7 +38,7 @@
reasons. The latest version of <a href="<page projects/torbrowser>">The
Tor Browser Bundle</a> on Windows tries to give you better hints about
why Tor is having problems connecting. You should also read <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.";>the
+ href="<wikifaq>#IinstalledTorandPolipobutitsnotworking.">the
FAQ about problems with running Tor properly</a> when you have issues.
If you feel that the issue is clearly blocking, or you'd simply like to try
because you're unsure or feeling adventurous, please read on. Ensure
@@ -154,7 +154,7 @@
run a bridge relay. You can configure it either way:
<ul>
<li> manually <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean";>edit
+ href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
your torrc file</a> to be just these four lines:<br />
<pre><code>
SocksPort 0
@@ -170,7 +170,7 @@
<p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.";>some
+ href="<wikifaq>#Myfirewallonlyallowsafewoutgoingports.">some
complex port forwarding</a>.
</p>
Modified: website/trunk/docs/en/documentation.wml
===================================================================
--- website/trunk/docs/en/documentation.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/documentation.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -46,7 +46,7 @@
<li>
Our <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ";>FAQ</a>
+ href="<wikifaq>">FAQ</a>
covers all sorts of topics, including questions about setting up a client
or relay, concerns about anonymity attacks, why we didn't build Tor in
other ways, etc.
@@ -59,7 +59,7 @@
<li>The <a href="<page docs/tor-manual>">manual</a>
lists all the possible entries you can put in your <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean";>torrc
+ href="<wikifaq>#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
file</a>. We also provide a <a href="<page docs/tor-manual-dev>">manual for
the development version of Tor</a>.</li>
@@ -67,7 +67,7 @@
operators, and developers)
at <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>. If
you have a bug, especially a crash bug, read <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.";>how
+ href="<wikifaq>#MyTorkeepscrashing.">how
to report a Tor bug</a> first and then tell us as much information
about it as you can in
<a href="https://bugs.torproject.org/tor";>our bugtracker</a>.
@@ -240,11 +240,11 @@
<a id="NeatLinks"></a>
<h1><a class="anchor" href="#NeatLinks">Neat Links</a></h1>
<ul>
- <li>The <a href="https://trac.torproject.org/projects/tor/wiki";>Tor
+ <li>The <a href="<wiki>">Tor
wiki</a> provides a plethora of helpful contributions from Tor
users. Check it out!</li>
<li><a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms";>A
+ href="<wiki>TheOnionRouter/SupportPrograms">A
list of supporting programs you might want to use in association with
Tor</a>.</li>
<li><a href="https://check.torproject.org/";>The
Modified: website/trunk/docs/en/faq-abuse.wml
===================================================================
--- website/trunk/docs/en/faq-abuse.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/faq-abuse.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -114,7 +114,7 @@
<h3><a class="anchor" href="#ExitPolicies">How do Tor exit policies work?</a></h3>
<p>
- <a href="<wiki>TorFAQ#ExitPolicies">See the FAQ</a>
+ <a href="<wikifaq>#ExitPolicies">See the FAQ</a>
</p>
<a id="HowMuchAbuse"></a>
@@ -234,7 +234,7 @@
<p>Finally, if you become aware of an IRC network that seems to be
blocking Tor, or a single Tor exit node, please put that information on <a
- href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc";>The Tor
+ href="<wiki>TheOnionRouter/BlockingIrc">The Tor
IRC block tracker</a>
so that others can share. At least one IRC network consults that page
to unblock exit nodes that have been blocked inadvertently. </p>
@@ -295,7 +295,7 @@
not so different from AOL in this respect.</p>
<p>Lastly, please remember that Tor relays have <a
- href="<wiki>#ExitPolicies">individual exit policies</a>. Many Tor relays do
+ href="<wikifaq>#ExitPolicies">individual exit policies</a>. Many Tor relays do
not allow exiting connections at all. Many of those that do allow some
exit connections might already disallow connections to
your service. When you go about banning nodes, you should parse the
Modified: website/trunk/docs/en/faq.wml
===================================================================
--- website/trunk/docs/en/faq.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/faq.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -81,8 +81,7 @@
</ul>
<p>For other questions not yet on this version of the FAQ, see the <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ";>wiki
- FAQ</a> for now.</p>
+ href="<wikifaq>">wiki FAQ</a> for now.</p>
<hr />
@@ -164,9 +163,9 @@
but we haven't researched the application-level anonymity
issues on them well enough to be able to recommend a safe
configuration. Our wiki has a list of instructions for <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO";>Torifying
+ href="<wiki>TheOnionRouter/TorifyHOWTO">Torifying
specific applications</a>. There's also a <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms";>list
+ href="<wiki>TheOnionRouter/SupportPrograms">list
of applications that help you direct your traffic through Tor</a>.
Please add to these lists and help us keep them accurate!
</p>
@@ -394,7 +393,7 @@
<li>
There are some steps that individuals
can take to improve their Tor performance. <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf";>You
+ href="<wiki>TheOnionRouter/FireFoxTorPerf">You
can configure your Firefox to handle Tor better</a>, <a
href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html";>you can use
Polipo with Tor</a>, or you can try <a href="<page download/download>">upgrading
@@ -698,7 +697,7 @@
Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
non-Tor traffic from accidentally leaving your computer. More information at
<a
- href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine";>https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li>
+ href="<wiki>VirtualPrivacyMachine"><wiki>VirtualPrivacyMachine</a>.</li>
<li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
than Linux for maximum security. It was designed to be anonymous and secure
from the ground up, and thus has some features and limitations not found in
@@ -783,11 +782,11 @@
<ul>
<li>Tor has built-in support for <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth";>
+ href="<wikifaq>#LimitBandwidth">
rate limiting</a>. Further, if you have a fast
link but want to limit the number of bytes per
day (or week or month) that you donate, check out the <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation";>hibernation
+ href="<wikifaq>#Hibernation">hibernation
feature</a>.
</li>
<li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
@@ -806,7 +805,7 @@
<li>If your relay is behind a NAT and it doesn't know its public
IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
forwarding. Forwarding TCP connections is system dependent but
- <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients";>this FAQ entry</a>
+ <a href="<wikifaq>#ServerForFirewalledClients">this FAQ entry</a>
offers some examples on how to do this.
</li>
<li>Your relay will passively estimate and advertise its recent
@@ -842,12 +841,12 @@
<p>
The default exit policy allows access to many popular services (e.g. web browsing), but
- <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts";>restricts</a>
+ <a href="<wikifaq>#DefaultPorts">restricts</a>
some due to abuse potential (e.g. mail) and some since
the Tor network can't handle the load (e.g. default
file-sharing ports). You can change your exit policy
using Vidalia's "Sharing" tab, or by manually editing your
- <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc";>torrc</a>
+ <a href="<wikifaq>#torrc">torrc</a>
file. If you want to avoid most if not all abuse potential, set it to
"reject *:*" (or un-check all the boxes in Vidalia). This setting means
that your relay will be used for relaying traffic inside the Tor network,
@@ -927,7 +926,7 @@
<li>If you're running on Solaris, OpenBSD, NetBSD, or
old FreeBSD, Tor is probably forking separate processes
rather than using threads. Consider switching to a <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS";>better
+ href="<wikifaq>#RelayOS">better
operating system</a>.</li>
<li>If you still can't handle the memory load, consider reducing the
@@ -1037,7 +1036,7 @@
<p>
Requiring every Tor user to be a relay would help with scaling the
- network to handle all our users, and <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity";>running a Tor
+ network to handle all our users, and <a href="<wikifaq>#RelayAnonymity">running a Tor
relay may help your anonymity</a>. However, many Tor users cannot be good
relays — for example, some Tor clients operate from behind restrictive
firewalls, connect via modem, or otherwise aren't in a position where they
@@ -1074,7 +1073,7 @@
<a href="<page getinvolved/volunteer>#Research">research section of the
volunteer page</a>: "Tor doesn't work very well when relays
have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP";>switching
+ href="<wikifaq>#TransportIPnotTCP">switching
to UDP transport</a> is the simplest answer here — which alas is
not a very simple answer at all.
</p>
@@ -1135,7 +1134,7 @@
<p>
A collection of templates for successfully responding to ISPs is <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates";>collected
+ href="<wiki>TheOnionRouter/TorAbuseTemplates">collected
here</a>.
</p>
Modified: website/trunk/docs/en/hidden-services.wml
===================================================================
--- website/trunk/docs/en/hidden-services.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/hidden-services.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -110,7 +110,7 @@
<p>
At this point it is of special importance that the hidden service sticks to
the same set of <a
- href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Whatsthisaboutentryguardformerlyknownashelpernodes";>entry
+ href="<wikifaq>#Whatsthisaboutentryguardformerlyknownashelpernodes">entry
guards</a> when creating new circuits. Otherwise an attacker
could run his own relay and force a hidden service to create an arbitrary
number of circuits in the hope that the corrupt relay is picked as entry
Modified: website/trunk/docs/en/tor-doc-relay.wml
===================================================================
--- website/trunk/docs/en/tor-doc-relay.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/tor-doc-relay.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -32,12 +32,12 @@
people who run relays, the faster the Tor network will be. If you have
at least 20 kilobytes/s each way, please help out Tor by configuring your
Tor to be a relay too. We have many features that make Tor relays easy
- and convenient, including <a href="<wiki>TorFAQ#RelayFlexible">rate limiting
+ and convenient, including <a href="<wikifaq>#RelayFlexible">rate limiting
for bandwidth, exit policies so you can limit your exposure to abuse
complaints, and support for dynamic IP addresses</a>.
</p>
- <p>You can run a Tor relay on <a href="<wiki>/TorFAQ#RelayOS">pretty
+ <p>You can run a Tor relay on <a href="<wikifaq>#RelayOS">pretty
much any</a> operating system. Tor relays work best on Linux, OS X Tiger
or later, FreeBSD 5.x+, NetBSD 5.x+, and Windows Server 2003 or later.
</p>
@@ -83,7 +83,7 @@
<dt>Choose <tt>Relay Traffic for the Tor network</tt> if you
want to be a public relay (recommended), or choose <tt>Help
censored users reach the Tor network</tt> if you want to be a <a
-href="<wiki>TorFAQ#RelayOrBridge">bridge</a> for users in countries that censor their Internet.</dt>
+href="<wikifaq>#RelayOrBridge">bridge</a> for users in countries that censor their Internet.</dt>
<dd><img alt="vidalia basic settings" src="../img/screenshot-win32-configure-relay-1.png"></dd>
</li>
@@ -100,7 +100,7 @@
<li><dt>Choose the <tt>Exit Policies</tt> tab. If you want to allow others
to use your relay for these services, don't change anything. Un-check
- 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>
+ 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>
<dd><img alt="vidalia exit policies" src="../img/screenshot-win32-configure-relay-3.png"></dd>
</li>
@@ -111,9 +111,9 @@
<br />
<strong>Manual Configuration</strong>:
<ul>
- <li>Edit the bottom part of <a href="<wiki>/TorFAQ#torrc">your torrc file</a>. If you want to be a public relay (recommended),
- make sure to define ORPort and <a href="<wiki>TorFAQ#ExitPolicies">look at ExitPolicy</a>; otherwise
- if you want to be a <a href="<wiki>TorFAQ#RelayOrBridge">bridge</a>
+ <li>Edit the bottom part of <a href="<wikifaq>#torrc">your torrc file</a>. If you want to be a public relay (recommended),
+ make sure to define ORPort and <a href="<wikifaq>#ExitPolicies">look at ExitPolicy</a>; otherwise
+ if you want to be a <a href="<wikifaq>#RelayOrBridge">bridge</a>
for users in countries that censor their Internet,
just use <a href="<page docs/bridges>#RunningABridge">these lines</a>.
</li>
Modified: website/trunk/docs/en/tor-doc-web.wml
===================================================================
--- website/trunk/docs/en/tor-doc-web.wml 2010-10-09 23:16:47 UTC (rev 23526)
+++ website/trunk/docs/en/tor-doc-web.wml 2010-10-09 23:35:02 UTC (rev 23527)
@@ -44,7 +44,7 @@
You should fill in "localhost"
and "8118" to point the top four protocols to Polipo, as shown here. (Even
though Polipo doesn't support FTP and Gopher, <a
- href="wikifaq#FtpProxy">you
+ href="<wikifaq>#FtpProxy">you
should set them up anyway</a>.) You should also fill out the socks proxy entry to point directly to Tor ("localhost", "9050", and socks5)
to cover protocols besides the first four. Then click "OK".</p>