and move them to cvs/website/docs/
Roger Dingledine

Roger Dingledine commited on 2006-03-15 20:56:16
Zeige 5 geänderte Dateien mit 1089 Einfügungen und 0 Löschungen.

... ...
@@ -0,0 +1,235 @@
1
+## translation metadata
2
+# Revision: $Revision$
3
+
4
+#include "head.wmi" TITLE="Tor Mac OS X Install Instructions"
5
+
6
+<div class="center">
7
+
8
+<div class="main-column">
9
+
10
+<h1>Running the <a href="<page index>">Tor</a> client on Mac OS X</h1>
11
+<br />
12
+
13
+<p>
14
+<b>Note that these are the installation instructions for running a Tor client on
15
+  Mac OS X. If you want to relay traffic for others to help the network
16
+  grow (please do), read the <a
17
+  href="<page tor-doc-server>">Configuring a server</a> guide.</b>
18
+</p>
19
+
20
+<hr />
21
+<a id="installing"></a>
22
+<h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
23
+<br />
24
+
25
+<p>
26
+The latest stable and experimental releases of Tor for Macintosh
27
+OS X bundle <a href="<page index>">Tor</a> and <a
28
+href="http://www.privoxy.org">Privoxy</a> (a filtering web proxy)
29
+into one package, with Privoxy pre-configured to proxy through Tor.
30
+<a href="<page download>">Download one from the download
31
+page</a>.
32
+</p>
33
+
34
+<p>Our Tor installer should make everything pretty simple. Below is a
35
+screenshot of the setup page:
36
+</p>
37
+
38
+<img alt="tor installer splash page"
39
+src="http://tor.eff.org/img/screenshot-osx-installer-splash.png"
40
+border="1">
41
+
42
+<p>
43
+By default, Tor is configured to run at startup.  If you do not want Tor to
44
+run on startup, you can disable this by selecting "Customize" in the
45
+Installer, and then un-checking the "Tor Startup Script" box. Be sure to
46
+leave the other boxes checked.
47
+</p>
48
+
49
+<p>Once the installer is finished and your computer restarts, Tor will
50
+start automatically.  Tor comes configured as a client by default. It
51
+uses a built-in default configuration file in <tt>/Library/Tor/torrc</tt>,
52
+but most people won't need to change any of the settings. Tor is now
53
+installed.</p>
54
+
55
+<p>Privoxy is installed as part of the Tor bundle package
56
+installer. Privoxy is a filtering web proxy that integrates well with
57
+Tor. Once it's installed, it will start automatically when your computer
58
+is restarted.
59
+</p>
60
+
61
+<p>You do not need to configure Privoxy to use Tor. A custom Privoxy
62
+configuration for Tor has been installed as part of the installer package.
63
+</p>
64
+
65
+<hr />
66
+<a id="using"></a>
67
+<h2><a class="anchor" href="#using">Step Two: Configure your applications to use Tor</a></h2>
68
+<br />
69
+
70
+<p>After installing Tor and Privoxy, you need to configure your
71
+applications to use them. The first step is to set up web browsing.</p>
72
+
73
+<p>If you're using Firefox (we recommend it), check out our <a
74
+href="<page tor-switchproxy>">Tor SwitchProxy howto</a> to set up
75
+a plugin that makes it easy to switch between using Tor and using a
76
+direct connection.</p>
77
+
78
+<p>Otherwise, you need to manually configure your browser to HTTP proxy
79
+at localhost port 8118.
80
+(That's where Privoxy listens.)
81
+In Mozilla, this is in Mozilla|Preferences|Advanced|Proxies.
82
+You should set both your Web Proxy (HTTP) and your Secure Web Proxy
83
+(HTTPS or SSL) to localhost port 8118, to hide your SSL traffic too.
84
+You should consider configuring your "FTP Proxy" too; see <a
85
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">this
86
+note</a> about Tor and ftp proxies.
87
+</p>
88
+
89
+<p>If you want to use Tor with Safari, you need to change your
90
+Network Settings. Select your Network Preferences from the Apple |
91
+Location menu:</p>
92
+
93
+<img alt="Network settings"
94
+src="http://tor.eff.org/img/screenshot-osx-choose-network.png"
95
+border="1">
96
+
97
+<p>Select the Network Interface on which you want to enable Tor. If you use
98
+more than one Interface you must change the proxy settings for each
99
+individually.</p>
100
+
101
+<img alt="Network preferences"
102
+src="http://tor.eff.org/img/screenshot-osx-choose-interface.png"
103
+border="1">
104
+<p>
105
+
106
+<p>Select and enter 127.0.0.1 and port 8118 for both
107
+Web Proxy (HTTP) and your Secure Web Proxy (HTTPS).
108
+You should also do this for "FTP Proxy" and "Gopher Proxy"; see <a
109
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">this
110
+note</a> about Tor and ftp proxies. Leave your Use Passive FTP Mode
111
+(PASV) setting as is.</p>
112
+
113
+<img alt="Proxy settings"
114
+src="http://tor.eff.org/img/screenshot-osx-proxy-settings.png"
115
+border="1">
116
+
117
+<p>Using privoxy is <strong>necessary</strong> because <a
118
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">browsers
119
+leak your
120
+DNS requests when they use a SOCKS proxy directly</a>, which is bad for
121
+your anonymity. Privoxy also removes certain dangerous headers from your
122
+web requests, and blocks obnoxious ad sites like Doubleclick.</p>
123
+
124
+<p>To Torify other applications that support HTTP proxies, just
125
+point them at Privoxy (that is, localhost port 8118). To use SOCKS
126
+directly (for instant messaging, Jabber, IRC, etc), you can point
127
+your application directly at Tor (localhost port 9050), but see <a
128
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
129
+FAQ entry</a> for why this may be dangerous. For applications
130
+that support neither SOCKS nor HTTP, take a look at <a
131
+href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> or
132
+<a href="http://www.dest-unreach.org/socat/">socat</a>.</p>
133
+
134
+<p>For information on how to Torify other applications, check out the
135
+<a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">Torify
136
+HOWTO</a>.
137
+</p>
138
+
139
+<hr />
140
+<a id="verify"></a>
141
+<h2><a class="anchor" href="#verify">Step Three: Make sure it's working</a></h2>
142
+<br />
143
+
144
+<p>
145
+Next, you should try using your browser with Tor and make
146
+sure that your IP address is being anonymized. Click on the <a
147
+href="http://serifos.eecs.harvard.edu/cgi-bin/ipaddr.pl?tor=1">Tor
148
+detector</a> and see whether it thinks you're using Tor or not.
149
+(If that site is down, see <a
150
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
151
+FAQ entry</a> for more suggestions on how to test your Tor.)
152
+</p>
153
+
154
+<p>If you have a personal firewall that limits your computer's
155
+ability to connect to itself, be sure to allow connections from
156
+your local applications to local port 8118 and port 9050. If
157
+your firewall blocks outgoing connections, punch a hole so
158
+it can connect to at least TCP ports 80 and 443, and then see <a
159
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
160
+FAQ entry</a>.
161
+</p>
162
+
163
+<p>If it's still not working, look at <a
164
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
165
+FAQ entry</a> for hints.</p>
166
+
167
+<hr />
168
+<a id="server"></a>
169
+<h2><a class="anchor" href="#server">Step Four: Configure it as a server</a></h2>
170
+<br />
171
+
172
+<p>The Tor network relies on volunteers to donate bandwidth. The more
173
+people who run servers, the faster the Tor network will be. If you have
174
+at least 20 kilobytes/s each way, please help out Tor by configuring your
175
+Tor to be a server too. We have many features that make Tor servers easy
176
+and convenient, including rate limiting for bandwidth, exit policies so
177
+you can limit your exposure to abuse complaints, and support for dynamic
178
+IP addresses.</p>
179
+
180
+<p>Having servers in many different places on the Internet is what
181
+makes Tor users secure. <a
182
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">You
183
+may also get stronger anonymity yourself</a>,
184
+since remote sites can't know whether connections originated at your
185
+computer or were relayed from others.</p>
186
+
187
+<p>Read more at our <a href="<page tor-doc-server>">Configuring a server</a>
188
+guide.</p>
189
+
190
+<hr />
191
+<a id="uninstall"></a>
192
+<h2><a class="anchor" href="#uninstall">How To Uninstall Tor and Privoxy</a></h2>
193
+<br />
194
+
195
+<p>The Tor 0.1.0.x series does not come with an uninstaller; this feature
196
+  will be added in the 0.1.1.x series.  If you want to remove Tor on OSX,
197
+  here's how:</p>
198
+
199
+<p>Change your application proxy settings back to their original values.
200
+   If you just want to stop using Tor, you can end at this point.</p>
201
+
202
+<p>To stop Tor and Privoxy from running on startup</b>, remove the
203
+   /Library/StartupItems/Tor and /Library/StartupItems/Privoxy directories
204
+   respectively. If you just want to stop Tor from running, you can end at this
205
+   point.</p>
206
+
207
+<p>To erase all remaining Tor and Privoxy files from your computer, delete
208
+  the following:
209
+   <ul>
210
+   <li>/Library/Tor</li>
211
+   <li>/Library/Privoxy</li>
212
+   <li>/usr/bin/tor</li>
213
+   <li>/usr/bin/tor_resolve</li>
214
+   <li>/var/log/tor</li>
215
+   <li>/usr/share/man/man1/tor.1</li>
216
+   <li>/usr/share/man/man1/tor-resolve.1</li>
217
+   <li>/usr/share/man/man1/torify.1</li>
218
+   <li>/Library/Receipts/Privoxy.pkg/</li>
219
+   <li>/Library/Receipts/privoxyconf.pkg/</li>
220
+   <li>/Library/Receipts/Tor.pkg/</li>
221
+   <li>/Library/Receipts/torstartup.pkg/</li>
222
+  </ul>
223
+</p>
224
+
225
+<hr />
226
+
227
+<p>If you have suggestions for improving this document, please post
228
+them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
229
+website category. Thanks!</p>
230
+
231
+  </div><!-- #main -->
232
+</div>
233
+
234
+#include <foot.wmi>
235
+
... ...
@@ -0,0 +1,314 @@
1
+## translation metadata
2
+# Revision: $Revision$
3
+
4
+#include "head.wmi" TITLE="Tor Server Configuration Instructions"
5
+
6
+<div class="center">
7
+
8
+<div class="main-column">
9
+
10
+<h1>Configuring a <a href="<page index>">Tor</a> server</h1>
11
+<br />
12
+
13
+<p>
14
+The Tor network relies on volunteers to donate bandwidth. The more
15
+people who run servers, the faster the Tor network will be. If you have
16
+at least 20 kilobytes/s each way, please help out Tor by configuring your
17
+Tor to be a server too. We have many features that make Tor servers easy
18
+and convenient, including rate limiting for bandwidth, exit policies so
19
+you can limit your exposure to abuse complaints, and support for dynamic
20
+IP addresses.</p>
21
+
22
+<p>Having servers in many different places on the Internet is what
23
+makes Tor users secure. <a
24
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">You
25
+may also get stronger anonymity yourself</a>,
26
+since remote sites can't know whether connections originated at your
27
+computer or were relayed from others.</p>
28
+
29
+<p>Setting up a Tor server is easy and convenient:
30
+<ul>
31
+<li>Tor has built-in support for <a
32
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">rate
33
+limiting</a>. Further, if you have a fast link
34
+but want to limit the number of bytes per day
35
+(or week or month) that you donate, check out the <a
36
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Hibernation">hibernation
37
+feature</a>.
38
+</li>
39
+<li>Each Tor server has an <a
40
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#RunAServerBut">exit
41
+policy</a> that specifies what sort of outbound connections are allowed
42
+or refused from that server. If you are uncomfortable allowing people
43
+to exit from your server, you can set it up to only allow connections
44
+to other Tor servers.
45
+</li>
46
+<li>It's fine if the server goes offline sometimes. The directories
47
+notice this quickly and stop advertising the server. Just try to make
48
+sure it's not too often, since connections using the server when it
49
+disconnects will break.
50
+</li>
51
+<li>We can handle servers with dynamic IPs just fine, as long as the
52
+server itself knows its IP. Have a look at this
53
+<a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#DynamicIP">
54
+entry in the FAQ</a>.
55
+</li>
56
+<li>If your server is behind a NAT and it doesn't know its public
57
+IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
58
+forwarding. Forwarding TCP connections is system dependent but <a
59
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledCli
60
+ents">this FAQ entry</a> offers some examples on how to do this.
61
+</li>
62
+<li>Your server will passively estimate and advertise its recent
63
+bandwidth capacity, so high-bandwidth servers will attract more users than
64
+low-bandwidth ones. Therefore having low-bandwidth servers is useful too.
65
+</li>
66
+</ul>
67
+
68
+<p>You can run a Tor server on
69
+pretty much any operating system, but see <a
70
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerOS">this
71
+FAQ entry</a> for advice about which ones work best and other problems
72
+you might encounter.</p>
73
+
74
+<hr />
75
+<a id="zero"></a>
76
+<h2><a class="anchor" href="#zero">Step Zero: Download and Install Tor</a></h2>
77
+<br />
78
+
79
+<p>Before you start, you need to make sure that Tor is up and running.
80
+</p>
81
+
82
+<p>For Windows users, this means at least <a
83
+href="<page tor-doc-win32>#installing">step one</a>
84
+of the Windows Tor installation howto. Mac OS X users need to do at least
85
+<a href="<page tor-doc-osx>#installing">step one</a>
86
+of OS X Tor installation howto.  Linux/BSD/Unix users should do at least
87
+<a href="<page tor-doc-unix>#installing">step one</a>
88
+of the Unix Tor installation howto.
89
+</p>
90
+
91
+<p>If it's convenient, you might also want to use it as a client for a
92
+while to make sure it's actually working.</p>
93
+
94
+<hr />
95
+<a id="one"></a>
96
+<h2><a class="anchor" href="#one">Step One: Set it up as a server</a></h2>
97
+<br />
98
+
99
+<p>
100
+1. Verify that your clock is set correctly. If possible, synchronize
101
+your clock with public time servers. 
102
+</p>
103
+
104
+<p>
105
+2. Make sure name resolution works (that is, your computer can resolve addresses correctly).
106
+</p>
107
+
108
+<p>
109
+3. Edit the bottom part of your torrc. (See <a
110
+href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#torrc">this
111
+FAQ entry</a> for help.)
112
+Make sure to define at least Nickname and ORPort. Create the DataDirectory
113
+if necessary, and make sure it's owned by the user that will be running
114
+tor. <em>If you want to run more than one server that's great, but
115
+please set <a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#MultipleServers">the
116
+MyFamily option</a> in all your servers' configuration files.</em>
117
+</p>
118
+
119
+<p>
120
+4. If you are using a firewall, open a hole in your firewall so
121
+incoming connections can reach the ports you configured (ORPort, plus
122
+DirPort if you enabled it). Make sure you allow all outgoing connections,
123
+so your server can reach the other Tor servers.
124
+</p>
125
+
126
+<p>
127
+5. Start your server: if you installed from source you can just
128
+run <tt>tor</tt>, whereas packages typically launch Tor from their
129
+initscripts or startup scripts. If it logs any warnings, address them. (By
130
+default Tor logs to stdout, but some packages log to <tt>/var/log/tor/</tt>
131
+instead. You can edit your torrc to configure log locations.)
132
+</p>
133
+
134
+<p>
135
+6. Subscribe to the <a
136
+href="http://archives.seul.org/or/announce/">or-announce</a>
137
+mailing list. It is very low volume, and it will keep you informed
138
+of new stable releases. You might also consider subscribing to <a
139
+href="http://archives.seul.org/or/talk/">or-talk</a> (higher volume),
140
+where new development releases are announced.
141
+</p>
142
+
143
+<p>
144
+7. Have a look at the manual.
145
+The <a href="<page tor-manual>">manual</a> for the
146
+latest stable version provides detailed instructions for how to install
147
+and use Tor, including configuration of client and server options.
148
+If you are running the CVS version the manual is available
149
+<a href="<page tor-manual-cvs>">here</a>.
150
+</p>
151
+
152
+<p>
153
+8. Read
154
+<a href="http://wiki.noreply.org/noreply/TheOnionRouter/OperationalSecurity">this document</a>
155
+to get ideas how you can increase the security of your server.
156
+<hr />
157
+<a id="two"></a>
158
+<h2><a class="anchor" href="#two">Step Two: Make sure it's working</a></h2>
159
+<br />
160
+
161
+<p>As soon as your server manages to connect to the network, it will
162
+try to determine whether the ports you configured are reachable from
163
+the outside. This may take up to 20 minutes. Look for a log entry like
164
+<tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>
165
+If you don't see this message, it means that your server is not reachable
166
+from the outside &mdash; you should re-check your firewalls, check that it's
167
+testing the IP and port you think it should be testing, etc.
168
+</p>
169
+
170
+<p>When it decides that it's reachable, it will upload a "server
171
+descriptor" to the directories. This will let clients know
172
+what address, ports, keys, etc your server is using. You can <a
173
+href="http://belegost.seul.org/">load the directory manually</a> and
174
+look through it to find the nickname you configured, to make sure it's
175
+there. You may need to wait a few seconds to give enough time for it to
176
+make a fresh directory.</p>
177
+
178
+<hr />
179
+<a id="three"></a>
180
+<h2><a class="anchor" href="#three">Step Three: Register your nickname</a></h2>
181
+<br />
182
+
183
+<p>
184
+Once you are convinced it's working (after a day or two maybe), you should
185
+register your server.
186
+This reserves your nickname so nobody else can take it, and lets us
187
+contact you if you need to upgrade or something goes wrong.
188
+</p>
189
+
190
+<p>
191
+Send mail to <a
192
+href="mailto:tor-ops@freehaven.net">tor-ops@freehaven.net</a> with a
193
+subject of '[New Server] &lt;your server's nickname&gt;' and
194
+include the following information in the message:
195
+</p>
196
+<ul>
197
+<li>Your server's nickname</li>
198
+<li>The fingerprint for your server's key (the contents of the
199
+"fingerprint" file in your DataDirectory &mdash; on Windows, look in
200
+\<i>username</i>\Application&nbsp;Data\tor\ or \Application&nbsp;Data\tor\;
201
+on OS X, look in /Library/Tor/var/lib/tor/; and on Linux/BSD/Unix,
202
+look in /var/lib/tor or ~/.tor)
203
+</li>
204
+<li>Who you are, so we know whom to contact if a problem arises</li>
205
+<li>What kind of connectivity the new server will have</li>
206
+</ul>
207
+
208
+<hr />
209
+<a id="four"></a>
210
+<h2><a class="anchor" href="#four">Step Four: Once it's working</a></h2>
211
+<br />
212
+
213
+<p>
214
+We recommend the following steps as well:
215
+</p>
216
+
217
+<p>
218
+6. Decide what exit policy you want. By default your server allows
219
+access to many popular services, but we restrict some (such as port 25)
220
+due to abuse potential. You might want an exit policy that is
221
+less restrictive or more restrictive; edit your torrc appropriately.
222
+Read the FAQ entry on <a
223
+href="<page faq-abuse>#TypicalAbuses">issues you might
224
+encounter if you use the default exit policy</a>.
225
+If you choose a particularly open exit policy, you should make
226
+sure your ISP is ok with that choice.
227
+</p>
228
+
229
+<p>
230
+7. Decide about rate limiting. Cable modem, DSL, and other users
231
+who have asymmetric bandwidth (e.g. more down than up) should
232
+rate limit to their slower bandwidth, to avoid congestion. See the <a
233
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">rate
234
+limiting FAQ entry</a> for details.
235
+</p>
236
+
237
+<p>
238
+8. If you control the name servers for your domain, consider setting
239
+your hostname to 'anonymous' or 'proxy' or 'tor-proxy', so when other
240
+people see the address in their web logs, they will more quickly
241
+understand what's going on.
242
+</p>
243
+
244
+<p>
245
+9. If your computer isn't running a webserver, please consider
246
+changing your ORPort to 443 and your DirPort to 80. Many Tor
247
+users are stuck behind firewalls that only let them browse the
248
+web, and this change will let them reach your Tor server. Win32
249
+servers can simply change their ORPort and DirPort directly
250
+in their torrc and restart Tor. OS X or Unix servers can't bind
251
+directly to these ports (since they don't run as root), so they will
252
+need to set up some sort of <a
253
+href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
254
+port forwarding</a> so connections can reach their Tor server. If you are
255
+using ports 80 and 443 already but still want to help out, other useful
256
+ports are 22, 110, and 143.
257
+</p>
258
+
259
+<p>
260
+10. If your Tor server provides other services on the same IP address
261
+&mdash; such as a public webserver &mdash; make sure that connections to the
262
+webserver are allowed from the local host too. You need to allow these
263
+connections because Tor clients will detect that your Tor server is the <a
264
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">safest
265
+way to reach that webserver</a>, and always build a circuit that ends
266
+at your server. If you don't want to allow the connections, you must
267
+explicitly reject them in your exit policy.
268
+</p>
269
+
270
+<p>
271
+11. (Unix only). Make a separate user to run the server. If you
272
+installed the OS X package or the deb or the rpm, this is already
273
+done. Otherwise, you can do it by hand. (The Tor server doesn't need to
274
+be run as root, so it's good practice to not run it as root. Running
275
+as a 'tor' user avoids issues with identd and other services that
276
+detect user name. If you're the paranoid sort, feel free to <a
277
+href="http://wiki.noreply.org/wiki/TheOnionRouter/TorInChroot">put Tor
278
+into a chroot jail</a>.)
279
+</p>
280
+
281
+<p>
282
+12. (Unix only.) Your operating system probably limits the number
283
+of open file descriptors per process to 1024 (or even less). If you
284
+plan to be running a fast exit node, this is probably not enough. On
285
+Linux, you should add a line like "toruser hard nofile 8192" to your
286
+/etc/security/limits.conf file (where toruser is the user that runs the
287
+Tor process), and then restart Tor if it's installed as a package (or log
288
+out and log back in if you run it yourself). If that doesn't work, see <a
289
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FileDescriptors">this
290
+FAQ entry</a> for other suggested ways to run "ulimit -n 8192" before
291
+you launch Tor.
292
+</p>
293
+
294
+<p>
295
+13. If you installed Tor via some package or installer, it probably starts
296
+Tor for you automatically on boot. But if you installed from source,
297
+you may find the initscripts in contrib/tor.sh or contrib/torctl useful.
298
+</p>
299
+
300
+When you change your Tor configuration, be sure to restart Tor, and
301
+remember to verify that your server still works correctly after the
302
+change.
303
+
304
+<hr />
305
+
306
+<p>If you have suggestions for improving this document, please post
307
+them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
308
+website category. Thanks!</p>
309
+
310
+  </div><!-- #main -->
311
+</div>
312
+
313
+#include <foot.wmi>
314
+
... ...
@@ -0,0 +1,191 @@
1
+## translation metadata
2
+# Revision: $Revision$
3
+
4
+#include "head.wmi" TITLE="Tor Linux/BSD/Unix Install Instructions"
5
+
6
+<div class="center">
7
+
8
+<div class="main-column">
9
+
10
+<h1>Running the <a href="<page index>">Tor</a> client on Linux/BSD/Unix</h1>
11
+<br />
12
+
13
+<p>
14
+<b>Note that these are the installation instructions for running a Tor
15
+client. If you want to relay traffic for others to help the network grow
16
+(please do), read the <a
17
+href="<page tor-doc-server>">Configuring a server</a> guide.</b>
18
+</p>
19
+
20
+<hr />
21
+<a id="installing"></a>
22
+<h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
23
+<br />
24
+
25
+<p>
26
+The latest release of Tor can be found on the <a
27
+href="<page download>">download</a> page. We have packages for Debian,
28
+Red Hat, Gentoo, *BSD, etc there too.
29
+</p>
30
+
31
+<p>If you're building from source, first install <a
32
+href="http://www.monkey.org/~provos/libevent/">libevent</a>, and
33
+make sure you have openssl and zlib (including the -devel packages if
34
+applicable). Then Run <tt>tar xzf tor-0.1.0.15.tar.gz;
35
+cd tor-0.1.0.15</tt>. Then <tt>./configure &amp;&amp; make</tt>. Now you
36
+can run tor as <tt>src/or/tor</tt>, or you can run <tt>make install</tt>
37
+(as root if necessary) to install it into /usr/local/, and then you can
38
+start it just by running <tt>tor</tt>.
39
+</p>
40
+
41
+<p>Tor comes configured as a client by default. It uses a built-in
42
+default configuration file, and most people won't need to change any of
43
+the settings. Tor is now installed.
44
+</p>
45
+
46
+<hr />
47
+<a id="privoxy"></a>
48
+<h2><a class="anchor" href="#privoxy">Step Two: Install Privoxy for Web Browsing</a></h2>
49
+<br />
50
+
51
+<p>After installing Tor, you need to configure your applications to use it.
52
+</p>
53
+
54
+<p>
55
+The first step is to set up web browsing. Start by installing <a
56
+href="http://www.privoxy.org/">Privoxy</a>: click on 'recent releases'
57
+and pick your favorite package or install from source. Privoxy is a
58
+filtering web proxy that integrates well with Tor.
59
+</p>
60
+
61
+<p>You need to configure Privoxy to use Tor.
62
+Open Privoxy's "config" file (look in /etc/privoxy/ or /usr/local/etc/)
63
+and add the line <br>
64
+<tt>forward-socks4a / localhost:9050 .</tt><br>
65
+to the top of the config file. Don't forget to add the dot at the end.
66
+</p>
67
+
68
+<p>Privoxy keeps a log file of everything passed through it.  In
69
+order to stop this you will need to comment out two lines by inserting a
70
+# before the line. The two lines are:<br>
71
+<tt>logfile logfile</tt><br>
72
+and the line <br>
73
+<tt>jarfile jarfile</tt><br>
74
+</p>
75
+
76
+<p>You'll need to restart Privoxy for the changes to take effect.</p>
77
+
78
+<hr />
79
+<a id="using"></a>
80
+<h2><a class="anchor" href="#using">Step Three: Configure your applications to use Tor</a></h2>
81
+<br />
82
+
83
+<p>After installing Tor and Privoxy, you need to configure your
84
+applications to use them. The first step is to set up web browsing.</p>
85
+
86
+<p>If you're using Firefox (we recommend it), check out our <a
87
+href="<page tor-switchproxy>">Tor SwitchProxy howto</a> to set up
88
+a plugin that makes it easy to switch between using Tor and using a
89
+direct connection.</p>
90
+
91
+<p>Otherwise, you need to manually configure your browser to HTTP proxy
92
+at localhost port 8118.
93
+(That's where Privoxy listens.)
94
+In Mozilla, this is in Edit|Preferences|Advanced|Proxies.
95
+In Opera 7.5x it's Tools|Preferences|Network|Proxy servers.
96
+You should click the "use the same proxy server for all protocols"
97
+button; but see <a
98
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">this
99
+note</a> about Tor and ftp proxies.
100
+
101
+<p>Using privoxy is <strong>necessary</strong> because <a
102
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">browsers
103
+leak your DNS requests when they use a SOCKS proxy directly</a>, which
104
+is bad for your anonymity. Privoxy also removes certain dangerous
105
+headers from your web requests, and blocks obnoxious ad sites like
106
+Doubleclick.</p>
107
+
108
+<p>To Torify other applications that support HTTP proxies, just
109
+point them at Privoxy (that is, localhost port 8118). To use SOCKS
110
+directly (for instant messaging, Jabber, IRC, etc), you can point
111
+your application directly at Tor (localhost port 9050), but see <a
112
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
113
+FAQ entry</a> for why this may be dangerous. For applications
114
+that support neither SOCKS nor HTTP, take a look at <a
115
+href="http://tsocks.sourceforge.net/">tsocks</a> or <a
116
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
117
+</p>
118
+
119
+<p>For information on how to Torify other applications, check out the
120
+<a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">Torify
121
+HOWTO</a>.
122
+</p>
123
+
124
+<hr />
125
+<a id="verify"></a>
126
+<h2><a class="anchor" href="#verify">Step Four: Make sure it's working</a></h2>
127
+<br />
128
+
129
+<p>
130
+Next, you should try using your browser with Tor and make
131
+sure that your IP address is being anonymized. Click on the <a
132
+href="http://serifos.eecs.harvard.edu/cgi-bin/ipaddr.pl?tor=1">Tor
133
+detector</a> and see whether it thinks you're using Tor or not.
134
+(If that site is down, see <a
135
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
136
+FAQ entry</a> for more suggestions on how to test your Tor.)
137
+</p>
138
+
139
+<p>If you have a personal firewall that limits your computer's
140
+ability to connect to itself (this includes something like SELinux on
141
+Fedora Core 4), be sure to allow connections from
142
+your local applications to Privoxy (local port 8118) and Tor (local port
143
+9050). If
144
+your firewall blocks outgoing connections, punch a hole so
145
+it can connect to at least TCP ports 80 and 443, and then see <a
146
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
147
+FAQ entry</a>.  If your SELinux config is not allowing tor or privoxy to
148
+run correctly, create a file named booleans.local in the directory
149
+/etc/selinux/targeted.  Edit this file in your favorite text editor and
150
+insert "allow_ypbind=1".  Restart your machine for this change to take
151
+effect.
152
+</p>
153
+
154
+<p>If it's still not working, look at <a
155
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
156
+FAQ entry</a> for hints.</p>
157
+
158
+<hr />
159
+<a id="server"></a>
160
+<h2><a class="anchor" href="#server">Step Five: Configure it as a server</a></h2>
161
+<br />
162
+
163
+<p>The Tor network relies on volunteers to donate bandwidth. The more
164
+people who run servers, the faster the Tor network will be. If you have
165
+at least 20 kilobytes/s each way, please help out Tor by configuring your
166
+Tor to be a server too. We have many features that make Tor servers easy
167
+and convenient, including rate limiting for bandwidth, exit policies so
168
+you can limit your exposure to abuse complaints, and support for dynamic
169
+IP addresses.</p>
170
+
171
+<p>Having servers in many different places on the Internet is what
172
+makes Tor users secure. <a
173
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">You
174
+may also get stronger anonymity yourself</a>,
175
+since remote sites can't know whether connections originated at your
176
+computer or were relayed from others.</p>
177
+
178
+<p>Read more at our <a href="<page tor-doc-server>">Configuring a server</a>
179
+guide.</p>
180
+
181
+<hr />
182
+
183
+<p>If you have suggestions for improving this document, please post
184
+them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
185
+website category. Thanks!</p>
186
+
187
+  </div><!-- #main -->
188
+</div>
189
+
190
+#include <foot.wmi>
191
+
... ...
@@ -0,0 +1,191 @@
1
+## translation metadata
2
+# Revision: $Revision$
3
+
4
+#include "head.wmi" TITLE="Tor MS Windows Install Instructions"
5
+
6
+<div class="center">
7
+
8
+<div class="main-column">
9
+
10
+<h1>Running the <a href="<page index>">Tor</a> client on MS Windows</h1>
11
+<br />
12
+
13
+<p>
14
+<b>Note that these are the installation instructions for running a Tor
15
+client on MS Windows (98, 98SE, NT4, 2000, XP, Server).
16
+If you want to relay traffic for others to help the network grow (please
17
+do), read the <a href="<page tor-doc-server>">Configuring a server</a>
18
+guide.</b>
19
+</p>
20
+
21
+<hr />
22
+<a id="installing"></a>
23
+<h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
24
+<br />
25
+
26
+<p>
27
+The install for MS Windows bundles <a href="<page index>">Tor</a>,
28
+<a href="http://www.freehaven.net/~edmanm/torcp/">TorCP</a>
29
+(a Tor controller that lets you monitor and control Tor), and <a
30
+href="http://www.privoxy.org">Privoxy</a> (a filtering web proxy) into
31
+one package, with the three applications pre-configured to work together.
32
+<a href="<page download>">Download either the stable or
33
+the experimental version from the download page</a>.
34
+</p>
35
+
36
+<p>
37
+<b>If you want to configure yourself to be a Tor server via TorCP,
38
+you will need the experimental version of the bundle.</b>
39
+</p>
40
+
41
+<p>If the bundles don't work for you, you can download Tor by itself
42
+from the <a href="<page download>">download page</a>, and then <a
43
+href="<page tor-doc-unix>#privoxy">install
44
+and configure Privoxy on your own</a>.
45
+</p>
46
+
47
+<img alt="tor installer splash page"
48
+src="http://tor.eff.org/img/screenshot-win32-installer-splash.png" />
49
+
50
+<p>If you have previously installed Tor, TorCP, or Privoxy
51
+you can deselect whichever components you do not need to install
52
+in the dialog shown below.
53
+</p>
54
+
55
+<img alt="select components to install"
56
+src="http://tor.eff.org/img/screenshot-win32-installer-components.png" />
57
+
58
+<p>After you have completed the installer, the components
59
+you selected will automatically be started for you.
60
+</p>
61
+
62
+<!--
63
+<p>Tor comes configured as a client by default. It uses a built-in
64
+default configuration file, and most people won't need to change any of
65
+the settings. Tor is now installed.
66
+</p>
67
+-->
68
+
69
+<hr />
70
+<a id="using"></a>
71
+<h2><a class="anchor" href="#using">Step Two: Configure your applications to use Tor</a></h2>
72
+<br />
73
+
74
+<p>After installing Tor and Privoxy, you need to configure your
75
+applications to use them. The first step is to set up web browsing.</p>
76
+
77
+<p>If you're using Firefox (we recommend it), check out our <a
78
+href="<page tor-switchproxy>">Tor SwitchProxy howto</a> to set up
79
+a plugin that makes it easy to switch between using Tor and using a
80
+direct connection.</p>
81
+
82
+<p>Otherwise, you need to manually configure your browser to HTTP proxy
83
+at localhost port 8118.
84
+(That's where Privoxy listens.)
85
+In Mozilla, this is in Edit|Preferences|Advanced|Proxies.
86
+In Opera 7.5x it's Tools|Preferences|Network|Proxy servers.
87
+In IE, it's Tools|Internet Options|Connections|LAN Settings|Advanced.
88
+You should click the "use the same proxy server for all protocols"
89
+button; but see <a
90
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">this
91
+note</a> about Tor and ftp proxies.
92
+In IE, this looks something like:</p>
93
+
94
+<img alt="Proxy settings in IE"
95
+src="http://tor.eff.org/img/screenshot-win32-ie-proxies.jpg" />
96
+
97
+<p>Using Privoxy is <strong>necessary</strong> because <a
98
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">browsers
99
+leak your DNS requests when they use a SOCKS proxy directly</a>, which
100
+is bad for your anonymity. Privoxy also removes certain dangerous
101
+headers from your web requests, and blocks obnoxious ad sites like
102
+Doubleclick.</p>
103
+
104
+<p>To Torify other applications that support HTTP proxies, just
105
+point them at Privoxy (that is, localhost port 8118). To use SOCKS
106
+directly (for instant messaging, Jabber, IRC, etc), you can point
107
+your application directly at Tor (localhost port 9050), but see <a
108
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
109
+FAQ entry</a> for why this may be dangerous. For applications
110
+that support neither SOCKS nor HTTP, take a look at <a
111
+href="http://www.socks.permeo.com/Download/SocksCapDownload/index.asp">SocksCap</a> or
112
+<a href="http://www.freecap.ru/eng/">FreeCap</a>.
113
+(FreeCap is free software; SocksCap is proprietary.)</p>
114
+
115
+<p>For information on how to Torify other applications, check out the
116
+<a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">Torify
117
+HOWTO</a>.
118
+</p>
119
+
120
+<hr />
121
+<a id="verify"></a>
122
+<h2><a class="anchor" href="#verify">Step Three: Make sure it's working</a></h2>
123
+<br />
124
+
125
+<p>
126
+Check to see that Privoxy and TorCP are running and that TorCP has
127
+successfully started Tor. Privoxy's icon is a green or blue circle with a "P"
128
+in it, and TorCP uses a fat grey onion with a green checkmark in your
129
+system notification area, as shown below:
130
+</p>
131
+
132
+<img alt="TorCP Tray Icon"
133
+src="http://tor.eff.org/img/screenshot-win32-torcp.png">
134
+
135
+<p>
136
+Next, you should try using your browser with Tor and make
137
+sure that your IP address is being anonymized. Click on the <a
138
+href="http://serifos.eecs.harvard.edu/cgi-bin/ipaddr.pl?tor=1">Tor
139
+detector</a> and see whether it thinks you're using Tor or not.
140
+(If that site is down, see <a
141
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
142
+FAQ entry</a> for more suggestions on how to test your Tor.)
143
+</p>
144
+
145
+<p>If you have a personal firewall that limits your computer's
146
+ability to connect to itself, be sure to allow connections from
147
+your local applications to local port 8118 and port 9050. If
148
+your firewall blocks outgoing connections, punch a hole so
149
+it can connect to at least TCP ports 80 and 443, and then see <a
150
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
151
+FAQ entry</a>.
152
+</p>
153
+
154
+<p>If it's still not working, look at <a
155
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
156
+FAQ entry</a> for hints.</p>
157
+
158
+<hr />
159
+<a id="server"></a>
160
+<h2><a class="anchor" href="#server">Step Four: Configure it as a server</a></h2>
161
+<br />
162
+
163
+<p>The Tor network relies on volunteers to donate bandwidth. The more
164
+people who run servers, the faster the Tor network will be. If you have
165
+at least 20 kilobytes/s each way, please help out Tor by configuring your
166
+Tor to be a server too. We have many features that make Tor servers easy
167
+and convenient, including rate limiting for bandwidth, exit policies so
168
+you can limit your exposure to abuse complaints, and support for dynamic
169
+IP addresses.</p>
170
+
171
+<p>Having servers in many different places on the Internet is what
172
+makes Tor users secure. <a
173
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">You
174
+may also get stronger anonymity yourself</a>,
175
+since remote sites can't know whether connections originated at your
176
+computer or were relayed from others.</p>
177
+
178
+<p>Read more at our <a href="<page tor-doc-server>">Configuring a server</a>
179
+guide.</p>
180
+
181
+<hr />
182
+
183
+<p>If you have suggestions for improving this document, please post
184
+them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
185
+website category. Thanks!</p>
186
+
187
+  </div><!-- #main -->
188
+</div>
189
+
190
+#include <foot.wmi>
191
+
... ...
@@ -0,0 +1,158 @@
1
+## translation metadata
2
+# Revision: $Revision$
3
+
4
+#include "head.wmi" TITLE="Tor SwitchProxy Install Instructions"
5
+
6
+<div class="center">
7
+
8
+<div class="main-column">
9
+
10
+<h1>Installing SwitchProxy for <a href="<page index>">Tor</a></h1>
11
+<hr />
12
+
13
+<p>
14
+SwitchProxy is a Firefox plugin that makes it easy for you to switch
15
+between using a proxy and connecting to websites directly.</p>
16
+
17
+<p>In this howto, you'll set up SwitchProxy to let you change
18
+between using Tor and a direct connection. We assume you already
19
+have Firefox installed and working.</p>
20
+
21
+<p>The screenshots here are oriented towards Windows users, but
22
+SwitchProxy works anywhere Firefox works. Hopefully everybody else can
23
+follow along just fine.</p>
24
+
25
+<hr />
26
+<a id="zero"></a>
27
+<h2><a class="anchor" href="#zero">Step Zero: Download and Install Tor and Privoxy</a></h2>
28
+<br />
29
+
30
+<p>Before you start, you need to make sure 1) Tor is up and running,
31
+2) Privoxy is up and running, and 3) Privoxy is configured to point
32
+to Tor.</p>
33
+
34
+<p>Windows users need to do <a
35
+href="<page tor-doc-win32>#installing">step one</a>
36
+of the Windows Tor installation howto, and Mac OS X users need to do <a
37
+href="<page tor-doc-osx>#installing">step one</a>
38
+of OS X Tor installation howto, since our Win32 and OS X packages include
39
+Privoxy and configure it already. Linux/BSD/Unix users should do <a
40
+href="<page tor-doc-unix>#installing">step one</a>
41
+and <a href="<page tor-doc-unix>#privoxy">step
42
+two</a> of the Unix Tor installation howto.
43
+</p>
44
+
45
+<hr />
46
+<a id="one"></a>
47
+<h2><a class="anchor" href="#one">Step One: Download and Install SwitchProxy</a></h2>
48
+<br />
49
+
50
+<p>SwitchProxy is a Firefox plugin, so you need to go through
51
+the process of installing a new plugin. First, go to the <a
52
+href="https://addons.mozilla.org/extensions/moreinfo.php?application=firefox&id=125">
53
+SwitchProxy</a> web page. If you're using Firefox 1.5, you might need to 
54
+download SwitchProxy <a href="http://www.roundtwo.com/product/switchproxy">from
55
+here</a> instead.
56
+Turn on JavaScript for now and click "Install Now":</p>
57
+
58
+<img alt="switchproxy web page"
59
+src="http://tor.eff.org/img/screenshot-switchproxy-webpage.jpg" />
60
+
61
+<p>It will pop up a window asking for permission to install the plugin.
62
+Click on the "Install Now" button:
63
+</p>
64
+
65
+<img alt="firefox plugin warning"
66
+src="http://tor.eff.org/img/screenshot-switchproxy-plugin-starting.jpg" />
67
+
68
+<p>Once the installer is finished, you should close all of your Firefox
69
+windows and restart Firefox.</p>
70
+
71
+<img alt="firefox plugin finished"
72
+src="http://tor.eff.org/img/screenshot-switchproxy-plugin-finished.jpg" />
73
+
74
+<hr />
75
+<a id="two"></a>
76
+<h2><a class="anchor" href="#two">Step Two: Configure SwitchProxy</a></h2>
77
+<br />
78
+
79
+<p>When you restart Firefox, you'll notice there's a new toolbar
80
+that lets you control your proxies. Now we're going to set up a proxy
81
+configuration for Tor. Click on "Add" in the new Proxy toolbar:</p>
82
+
83
+<img alt="new toolbar"
84
+src="http://tor.eff.org/img/screenshot-switchproxy-toolbar.jpg" />
85
+
86
+<p>It will ask you to select a proxy type. Choose
87
+"Standard." (There's also an "anonymous" proxy type that
88
+uses an ad hoc set of anonymous proxies out there. You
89
+don't want this, because those other "anonymous" proxies <a
90
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ComparisonProxyAggregators">give
91
+you much weaker security than Tor</a>.)
92
+</p>
93
+
94
+<img alt="standard proxy"
95
+src="http://tor.eff.org/img/screenshot-switchproxy-proxytype.jpg" />
96
+
97
+<p>Now it will show you the standard proxy config window for Firefox.
98
+Give this configuration a proxy label of "tor". Then fill in "localhost"
99
+and "8118" for all four entries, as shown here. (Even
100
+though Privoxy doesn't support FTP and Gopher, <a
101
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">you
102
+should set them up anyway</a>.) Then click "OK":</p>
103
+
104
+<img alt="proxy config"
105
+src="http://tor.eff.org/img/screenshot-switchproxy-proxyconfig.jpg" />
106
+
107
+<p>Now you've created the "tor" proxy label, but you're not using it yet.
108
+Click on the pull-down list and select tor, as shown here:</p>
109
+
110
+<img alt="switch to tor"
111
+src="http://tor.eff.org/img/screenshot-switchproxy-switch.jpg" />
112
+
113
+<p>Almost done. Click "Apply" to make your change take effect:</p>
114
+
115
+<img alt="apply"
116
+src="http://tor.eff.org/img/screenshot-switchproxy-apply.jpg" />
117
+
118
+<p>Done! Firefox will reload your current page. In
119
+this example screenshot, it reloaded the page and <a
120
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#GoogleLanguage">happened
121
+to get a German exit node</a>:</p>
122
+
123
+<img alt="german google"
124
+src="http://tor.eff.org/img/screenshot-switchproxy-german.jpg" />
125
+
126
+<hr />
127
+<a id="three"></a>
128
+<h2><a class="anchor" href="#three">Step Step Three: Check if it works</a></h2>
129
+<br />
130
+
131
+<p>Now Firefox is using Privoxy as an HTTP proxy, Privoxy is using Tor as
132
+a socks4a proxy, and Tor is making your connections to the Internet.</p>
133
+
134
+<p>In the above example, it was clear that it worked because the web
135
+page showed up in a different language. In other cases, though,
136
+you'll want to verify that your setup is working. Do
137
+<a href="<page tor-doc-win32>#verify">step three</a>
138
+of the Windows Tor installation howto, or
139
+<a href="<page tor-doc-osx>#verify">step three</a>
140
+of the OS X Tor installation howto.</p>
141
+
142
+<p>You should be aware of one anonymity gotcha: when you switch from
143
+using Tor to a direct connection (or vice versa), by default the page
144
+that's currently active will be reloaded through the new proxy setting.
145
+So make sure you're on a page that isn't sensitive, before switching.
146
+(You can also change this behavior in SwitchProxy's "Options |
147
+Preferences" menu.)</p>
148
+
149
+<hr />
150
+
151
+<p>If you have suggestions for improving this document, please <a
152
+href="/contact">send them to us</a>. Thanks!</p>
153
+
154
+  </div><!-- #main -->
155
+</div>
156
+
157
+#include <foot.wmi>
158
+
0 159