From 051c176219a79473204c04039e3df5fb1e14be1e Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Fri, 31 Mar 2006 05:07:12 +0000 Subject: [PATCH] Blow away the obsolete docs. Leave shells of them in case people link to them from elsewhere. svn:r6279 --- doc/stylesheet.css | 338 ----------------------------------- doc/tor-doc-osx.html | 268 +--------------------------- doc/tor-doc-server.html | 346 +----------------------------------- doc/tor-doc-unix.html | 223 +---------------------- doc/tor-doc-win32.es.html | 192 -------------------- doc/tor-doc-win32.html | 223 +---------------------- doc/tor-doc.css | 89 ---------- doc/tor-doc.html | 49 ----- doc/tor-hidden-service.html | 308 +------------------------------- doc/tor-switchproxy.html | 190 +------------------- 10 files changed, 36 insertions(+), 2190 deletions(-) delete mode 100644 doc/stylesheet.css delete mode 100644 doc/tor-doc-win32.es.html delete mode 100644 doc/tor-doc.css diff --git a/doc/stylesheet.css b/doc/stylesheet.css deleted file mode 100644 index d7c1d78758..0000000000 --- a/doc/stylesheet.css +++ /dev/null @@ -1,338 +0,0 @@ -/* This is copied from http://tor.eff.org/stylesheet.css - * If you want to edit something, edit that one and then - * copy it over to here. */ - -body { - background-color: #FFFFFF; - margin-top: 0px; - font-family: Arial, Helvetica, sans-serif; - font-size: 1em; - font-style: normal; - color: #000000; - padding-top: 0px; -} - -/* images */ - -img { - border: 0; -} - - -li { - margin: .2em .2em .2em 1em; - -} - -/* this centers the page */ - -.center { - text-align: center; - background-color: white; - margin: 0px auto 0 auto; - width: 85%; -} - -.center table { - margin-left: auto; - margin-right: auto; - text-align: left; -} - -/* for the shadow box */ - -table.shadowbox { - width: 788px; - border-collapse: collapse; - padding: 0; - margin-bottom: 2em; -} - -table.shadowbox td { - margin: 0; - padding: 0; -} - -/* spacer */ - -td.spacer { - width: 110px; -} - - - -div.banner { - text-align: center; - height: 79px; - margin-bottom: 10px; - width:100%; -} - -table.table-banner { - margin: 0 auto 0 auto; - background-image: url("/images/tor_mast.gif"); - background-repeat: no-repeat; -} - - - - -div.bottom { - font-size: 0.8em; - margin-top: 2cm; - margin-left: 1em; - margin-right: 1em; - text-align: right; -} - -/* the sidebar */ - -div.sidebar { - float: right; - padding-top: 10px; - padding-right: 10px; - padding-bottom: 15px; - padding-left: 10px; - width: 260px; - text-align: center; -} - - -/* The main column (left text) */ - -div.main-column { - padding: 15px 0 10px 10px; - text-indent: 0pt; - font-size: 1em; - text-align: left; -} - -/* formatting styles */ - -h1 { - font-size: 1.5em; - margin-bottom: 0.5em; -} - -h2 { - font-size: 1.2em; - margin-bottom: 0em; - font-weight: bold; - margin-top: 0; -} - -p { - margin-top: 0; - margin-bottom: 1em; -} - -a:link { - color: blue; - font-size: 1em; -} - -a:visited { - color: purple; - font-size: 1em; -} - - -a.anchor:link { - font-size: 1em; - color: black; - font-weight: bold; - text-decoration: none; -} - -a.anchor:visited { - font-size: 12pt; - color: black; - font-weight: bold; - text-decoration: none; -} - -a.anchor { - font-size: 1em; - color: black; - font-weight: bold; - text-decoration: none; -} - -td { - vertical-align: top; -} - -a.smalllink { - font-size: 0.8em; -} - -/* the banner */ - -table.banner { - width: 100%; - height: 79px; - margin-left: auto; - margin-right: auto; -} - -td.banner-left { - background-image: url("/images/top-left.png"); - background-repeat: no-repeat; - width: 193px; -} - -td.banner-middle { - background-image: url("/images/top-middle.png"); - background-repeat: repeat-x; - vertical-align: bottom; - padding-bottom: 10px; - color: white; - font-weight: bold; - font-size: 1em; -} - -td.banner-middle a, td.banner-middle a:visited { - color: white; - font-weight: bold; - font-size: 1em; -} - -td.banner-middle a:hover { - color: #FF7F00; - font-weight: bold; - font-size: 1em; -} - -td.banner-right { - background-image: url("/images/top-right.png"); - background-repeat: no-repeat; - width: 40px; - background-position: right; - padding-top: 8px; -} - -.banner-middle a.current { - text-decoration: none; - color: #FF7F00; - font-weight: bold; - font-size: 1em; - width: auto; - text-align: auto; - left: -50px; -} - -.donatebutton { - width: auto; - text-align: center; -} - -.donatebutton a { - margin: 10px 0 0 0; - font-weight: bold; - display: block; - padding: 6px; - background-color: #00802B; - border-top: 1px solid #00A838; - border-left: 1px solid #00A838; - border-bottom: 1px solid #00591E; - border-right: 1px solid #00591E; - color: #FFFFFF; -} - -.donatebutton a:hover { - color: orange; -} - -.donatebutton a:active { - color: orange; -} - -/* these styles are for the menu on the gui contest pages */ - -.guileft { - width: 25%; - float: left; - padding: 0; - margin: 0; -} - -.guimenu { - border: 1px solid #AAA6AB; - background-color: #E2DFE3; - margin: 0 15px 15px 0; - padding: 0; -} - -.guimenuinner a { - display: block; - text-decoration: none; - padding: 2px 0px 0px 12px; - margin: 0 0 0 0px; - color: #333333; -} - -.guimenuinner a:visited { - color: #333333; -} - -.guimenuinner a:hover { - background-image: url(gui/img/arrow.png); - background-repeat: no-repeat; - background-position: left; - color: #EF8012; -} - -.guimenuinner a.on { - background-image: url(gui/img/arrow.png); - background-repeat: no-repeat; - background-position: left; - color: #EF8012; -} - - -.guimenu h1 { - width: 85%; - font-size: 16px; - margin: 0 0 8px 0; - padding: 0; - border-bottom: 1px solid #AAA6AB; -} - -.curveleft { - background-image: url(gui/img/corner-topleft.png); - background-repeat: no-repeat; - background-position: top left; - margin: -1px; -} - -.curveright { - background-image: url(gui/img/corner-topright.png); - background-repeat: no-repeat; - background-position: top right; -} - -.guimenuinner { - - padding: 0 10px 0 10px; -} - -//.wiki { - padding: 5px 40px 0 0; - display: block; - text-align: right; -} - - -.curvebottomleft { - background-image: url(gui/img/corner-bottomleft.png); - background-repeat: no-repeat; - background-position: bottom left; - margin: -1px; -} - -.curvebottomright { - background-image: url(gui/img/corner-bottomright.png); - background-repeat: no-repeat; - background-position: bottom right; -} - diff --git a/doc/tor-doc-osx.html b/doc/tor-doc-osx.html index c79bebf2d5..0064eb3169 100644 --- a/doc/tor-doc-osx.html +++ b/doc/tor-doc-osx.html @@ -1,274 +1,18 @@ - - - + + - Tor Mac OS X Install Instructions - - - - - +Tor Documentation + + - - - - - - - - - - - - -
- -
-

This document is obsolete. See the new Tor documentation page. +href="http://tor.eff.org/documentation.html">Tor documentation page.

-

Running the Tor client on Mac OS X

-
- -

-Note that these are the installation instructions for running a Tor client on - Mac OS X. If you want to relay traffic for others to help the network - grow (please do), read the Configuring a server guide. -

- -
- -

Step One: Download and Install Tor

-
- -

-The latest stable and experimental releases of Tor for Macintosh -OS X bundle Tor and Privoxy (a filtering web proxy) -into one package, with Privoxy pre-configured to proxy through Tor. -Download one from the download -page. -

- -

Our Tor installer should make everything pretty simple. Below is a -screenshot of the setup page: -

- -tor installer splash page - -

-By default, Tor is configured to run at startup. If you do not want Tor to -run on startup, you can disable this by selecting "Customize" in the -Installer, and then un-checking the "Tor Startup Script" box. Be sure to -leave the other boxes checked. -

- -

Once the installer is finished and your computer restarts, Tor will -start automatically. Tor comes configured as a client by default. It -uses a built-in default configuration file in /Library/Tor/torrc, -but most people won't need to change any of the settings. Tor is now -installed.

- -

Privoxy is installed as part of the Tor bundle package -installer. Privoxy is a filtering web proxy that integrates well with -Tor. Once it's installed, it will start automatically when your computer -is restarted. -

- -

You do not need to configure Privoxy to use Tor. A custom Privoxy -configuration for Tor has been installed as part of the installer package. -

- -
- -

Step Two: Configure your applications to use Tor

-
- -

After installing Tor and Privoxy, you need to configure your -applications to use them. The first step is to set up web browsing.

- -

If you're using Firefox (we recommend it), check out our Tor SwitchProxy howto to set up -a plugin that makes it easy to switch between using Tor and using a -direct connection.

- -

Otherwise, you need to manually configure your browser to HTTP proxy -at localhost port 8118. -(That's where Privoxy listens.) -In Mozilla, this is in Mozilla|Preferences|Advanced|Proxies. -You should set both your Web Proxy (HTTP) and your Secure Web Proxy -(HTTPS or SSL) to localhost port 8118, to hide your SSL traffic too. -You should consider configuring your "FTP Proxy" too; see this -note about Tor and ftp proxies. -

- -

If you want to use Tor with Safari, you need to change your -Network Settings. Select your Network Preferences from the Apple | -Location menu:

- -Network settings - -

Select the Network Interface on which you want to enable Tor. If you use -more than one Interface you must change the proxy settings for each -individually.

- -Network preferences -

- -

Select and enter 127.0.0.1 and port 8118 for both -Web Proxy (HTTP) and your Secure Web Proxy (HTTPS). -You should also do this for "FTP Proxy" and "Gopher Proxy"; see this -note about Tor and ftp proxies. Leave your Use Passive FTP Mode -(PASV) setting as is.

- -Proxy settings - -

Using privoxy is necessary because browsers -leak your -DNS requests when they use a SOCKS proxy directly, which is bad for -your anonymity. Privoxy also removes certain dangerous headers from your -web requests, and blocks obnoxious ad sites like Doubleclick.

- -

To Torify other applications that support HTTP proxies, just -point them at Privoxy (that is, localhost port 8118). To use SOCKS -directly (for instant messaging, Jabber, IRC, etc), you can point -your application directly at Tor (localhost port 9050), but see this -FAQ entry for why this may be dangerous. For applications -that support neither SOCKS nor HTTP, take a look at connect or -socat.

- -

For information on how to Torify other applications, check out the -Torify -HOWTO. -

- -
- -

Step Three: Make sure it's working

-
- -

-Next, you should try using your browser with Tor and make -sure that your IP address is being anonymized. Click on the Tor -detector and see whether it thinks you're using Tor or not. -(If that site is down, see this -FAQ entry for more suggestions on how to test your Tor.) -

- -

If you have a personal firewall that limits your computer's -ability to connect to itself, be sure to allow connections from -your local applications to local port 8118 and port 9050. If -your firewall blocks outgoing connections, punch a hole so -it can connect to at least TCP ports 80 and 443, and then see this -FAQ entry. -

- -

If it's still not working, look at this -FAQ entry for hints.

- -
- -

Step Four: Configure it as a server

-
- -

The Tor network relies on volunteers to donate bandwidth. The more -people who run servers, 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 server too. We have many features that make Tor servers easy -and convenient, including rate limiting for bandwidth, exit policies so -you can limit your exposure to abuse complaints, and support for dynamic -IP addresses.

- -

Having servers in many different places on the Internet is what -makes Tor users secure. You -may also get stronger anonymity yourself, -since remote sites can't know whether connections originated at your -computer or were relayed from others.

- -

Read more at our Configuring a server -guide.

- -
- -

How To Uninstall Tor and Privoxy

-
- -

The Tor 0.1.0.x series does not come with an uninstaller; this feature - will be added in the 0.1.1.x series. If you want to remove Tor on OSX, - here's how:

- -

Change your application proxy settings back to their original values. - If you just want to stop using Tor, you can end at this point.

- -

To stop Tor and Privoxy from running on startup, remove the - /Library/StartupItems/Tor and /Library/StartupItems/Privoxy directories - respectively. If you just want to stop Tor from running, you can end at this - point.

- -

To erase all remaining Tor and Privoxy files from your computer, delete - the following: -

    -
  • /Library/Tor
    • -
  • /Library/Privoxy
    • -
  • /usr/bin/tor
    • -
  • /usr/bin/tor_resolve
    • -
  • /var/log/tor
    • -
  • /usr/share/man/man1/tor.1
    • -
  • /usr/share/man/man1/tor-resolve.1
    • -
  • /usr/share/man/man1/torify.1
    • -
  • /Library/Receipts/Privoxy.pkg/
    • -
  • /Library/Receipts/privoxyconf.pkg/
    • -
  • /Library/Receipts/Tor.pkg/
    • -
  • /Library/Receipts/torstartup.pkg/
    • -
-

- -
- -

If you have suggestions for improving this document, please post -them on our bugtracker in the -website category. Thanks!

- -
-
-
- Webmaster - $Id$ -
diff --git a/doc/tor-doc-server.html b/doc/tor-doc-server.html index 0577114ed4..0064eb3169 100644 --- a/doc/tor-doc-server.html +++ b/doc/tor-doc-server.html @@ -1,352 +1,18 @@ - - - + + - Tor Server Configuration Instructions - - - - +Tor Documentation + + - - - - - - - - - - - - -
- -
-

This document is obsolete. See the new Tor documentation page. +href="http://tor.eff.org/documentation.html">Tor documentation page.

-

Configuring a Tor server

-
- -

-The Tor network relies on volunteers to donate bandwidth. The more -people who run servers, 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 server too. We have many features that make Tor servers easy -and convenient, including rate limiting for bandwidth, exit policies so -you can limit your exposure to abuse complaints, and support for dynamic -IP addresses.

- -

Having servers in many different places on the Internet is what -makes Tor users secure. You -may also get stronger anonymity yourself, -since remote sites can't know whether connections originated at your -computer or were relayed from others.

- -

Setting up a Tor server is easy and convenient: -

    -
  • Tor has built-in support for rate -limiting. 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 hibernation -feature. -
    • -
  • Each Tor server has an exit -policy that specifies what sort of outbound connections are allowed -or refused from that server. If you are uncomfortable allowing people -to exit from your server, you can set it up to only allow connections -to other Tor servers. -
    • -
  • It's fine if the server goes offline sometimes. The directories -notice this quickly and stop advertising the server. Just try to make -sure it's not too often, since connections using the server when it -disconnects will break. -
    • -
  • We can handle servers with dynamic IPs just fine, as long as the -server itself knows its IP. Have a look at this - -entry in the FAQ. -
    • -
  • If your server 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 this FAQ entry offers some examples on how to do this. -
    • -
  • Your server will passively estimate and advertise its recent -bandwidth capacity, so high-bandwidth servers will attract more users than -low-bandwidth ones. Therefore having low-bandwidth servers is useful too. -
    • -
- -

You can run a Tor server on -pretty much any operating system, but see this -FAQ entry for advice about which ones work best and other problems -you might encounter.

- -
- -

Step Zero: Download and Install Tor

-
- -

Before you start, you need to make sure that Tor is up and running. -

- -

For Windows users, this means at least step one -of the Windows Tor installation howto. Mac OS X users need to do at least -step one -of OS X Tor installation howto. Linux/BSD/Unix users should do at least -step one -of the Unix Tor installation howto. -

- -

If it's convenient, you might also want to use it as a client for a -while to make sure it's actually working.

- -
- -

Step One: Set it up as a server

-
- -

-1. Verify that your clock is set correctly. If possible, synchronize -your clock with public time servers. -

- -

-2. Make sure name resolution works (that is, your computer can resolve addresses correctly). -

- -

-3. Edit the bottom part of your torrc. (See this -FAQ entry for help.) -Make sure to define at least Nickname and ORPort. Create the DataDirectory -if necessary, and make sure it's owned by the user that will be running -tor. If you want to run more than one server that's great, but -please set the -MyFamily option in all your servers' configuration files. -

- -

-4. If you are using a firewall, open a hole in your firewall so -incoming connections can reach the ports you configured (ORPort, plus -DirPort if you enabled it). Make sure you allow all outgoing connections, -so your server can reach the other Tor servers. -

- -

-5. Start your server: if you installed from source you can just -run tor, whereas packages typically launch Tor from their -initscripts or startup scripts. If it logs any warnings, address them. (By -default Tor logs to stdout, but some packages log to /var/log/tor/ -instead. You can edit your torrc to configure log locations.) -

- -

-6. Subscribe to the or-announce -mailing list. It is very low volume, and it will keep you informed -of new stable releases. You might also consider subscribing to or-talk (higher volume), -where new development releases are announced. -

- -

-7. Have a look at the manual. -The manual for the -latest stable version provides detailed instructions for how to install -and use Tor, including configuration of client and server options. -If you are running the CVS version the manual is available -here. -

- -

-8. Read -this document -to get ideas how you can increase the security of your server. -

- -

Step Two: Make sure it's working

-
- -

As soon as your server manages to connect to the network, it will -try to determine whether the ports you configured are reachable from -the outside. This may take up to 20 minutes. Look for a log entry like -Self-testing indicates your ORPort is reachable from the outside. Excellent. -If you don't see this message, it means that your server is not reachable -from the outside — you should re-check your firewalls, check that it's -testing the IP and port you think it should be testing, etc. -

- -

When it decides that it's reachable, it will upload a "server -descriptor" to the directories. This will let clients know -what address, ports, keys, etc your server is using. You can load the directory manually and -look through it to find the nickname you configured, to make sure it's -there. You may need to wait a few seconds to give enough time for it to -make a fresh directory.

- -
- -

Step Three: Register your nickname

-
- -

-Once you are convinced it's working (after a day or two maybe), you should -register your server. -This reserves your nickname so nobody else can take it, and lets us -contact you if you need to upgrade or something goes wrong. -

- -

-Send mail to tor-ops@freehaven.net with a -subject of '[New Server] <your server's nickname>' and -include the following information in the message: -

-
    -
  • Your server's nickname
    • -
  • The fingerprint for your server's key (the contents of the -"fingerprint" file in your DataDirectory — on Windows, look in -\username\Application Data\tor\ or \Application Data\tor\; -on OS X, look in /Library/Tor/var/lib/tor/; and on Linux/BSD/Unix, -look in /var/lib/tor or ~/.tor) -
    • -
  • Who you are, so we know whom to contact if a problem arises
    • -
  • What kind of connectivity the new server will have
    • -
- -
- -

Step Four: Once it's working

-
- -

-We recommend the following steps as well: -

- -

-6. Decide what exit policy you want. By default your server allows -access to many popular services, but we restrict some (such as port 25) -due to abuse potential. You might want an exit policy that is -less restrictive or more restrictive; edit your torrc appropriately. -Read the FAQ entry on issues you might -encounter if you use the default exit policy. -If you choose a particularly open exit policy, you should make -sure your ISP is ok with that choice. -

- -

-7. Decide about rate limiting. Cable modem, DSL, and other users -who have asymmetric bandwidth (e.g. more down than up) should -rate limit to their slower bandwidth, to avoid congestion. See the rate -limiting FAQ entry for details. -

- -

-8. If you control the name servers for your domain, consider setting -your hostname to 'anonymous' or 'proxy' or 'tor-proxy', so when other -people see the address in their web logs, they will more quickly -understand what's going on. -

- -

-9. If your computer isn't running a webserver, please consider -changing your ORPort to 443 and your DirPort to 80. Many Tor -users are stuck behind firewalls that only let them browse the -web, and this change will let them reach your Tor server. Win32 -servers can simply change their ORPort and DirPort directly -in their torrc and restart Tor. OS X or Unix servers can't bind -directly to these ports (since they don't run as root), so they will -need to set up some sort of -port forwarding so connections can reach their Tor server. If you are -using ports 80 and 443 already but still want to help out, other useful -ports are 22, 110, and 143. -

- -

-10. If your Tor server provides other services on the same IP address -— such as a public webserver — make sure that connections to the -webserver are allowed from the local host too. You need to allow these -connections because Tor clients will detect that your Tor server is the safest -way to reach that webserver, and always build a circuit that ends -at your server. If you don't want to allow the connections, you must -explicitly reject them in your exit policy. -

- -

-11. (Unix only). Make a separate user to run the server. If you -installed the OS X package or the deb or the rpm, this is already -done. Otherwise, you can do it by hand. (The Tor server doesn't need to -be run as root, so it's good practice to not run it as root. Running -as a 'tor' user avoids issues with identd and other services that -detect user name. If you're the paranoid sort, feel free to put Tor -into a chroot jail.) -

- -

-12. (Unix only.) Your operating system probably limits the number -of open file descriptors per process to 1024 (or even less). If you -plan to be running a fast exit node, this is probably not enough. On -Linux, you should add a line like "toruser hard nofile 8192" to your -/etc/security/limits.conf file (where toruser is the user that runs the -Tor process), and then restart Tor if it's installed as a package (or log -out and log back in if you run it yourself). If that doesn't work, see this -FAQ entry for other suggested ways to run "ulimit -n 8192" before -you launch Tor. -

- -

-13. If you installed Tor via some package or installer, it probably starts -Tor for you automatically on boot. But if you installed from source, -you may find the initscripts in contrib/tor.sh or contrib/torctl useful. -

- -When you change your Tor configuration, be sure to restart Tor, and -remember to verify that your server still works correctly after the -change. - -
- -

If you have suggestions for improving this document, please post -them on our bugtracker in the -website category. Thanks!

- -
-
-
- Webmaster - $Id$ -
diff --git a/doc/tor-doc-unix.html b/doc/tor-doc-unix.html index be4bc34b70..0064eb3169 100644 --- a/doc/tor-doc-unix.html +++ b/doc/tor-doc-unix.html @@ -1,229 +1,18 @@ - - - + + - Tor Linux/BSD/Unix Install Instructions - - - - +Tor Documentation + + - - - - - - - - - - - - -
- -
-

This document is obsolete. See the new Tor documentation page. +href="http://tor.eff.org/documentation.html">Tor documentation page.

-

Running the Tor client on Linux/BSD/Unix

-
- -

-Note that these are the installation instructions for running a Tor -client. If you want to relay traffic for others to help the network grow -(please do), read the Configuring a server guide. -

- -
- -

Step One: Download and Install Tor

-
- -

-The latest release of Tor can be found on the download page. We have packages for Debian, -Red Hat, Gentoo, *BSD, etc there too. -

- -

If you're building from source, first install libevent, and -make sure you have openssl and zlib (including the -devel packages if -applicable). Then Run tar xzf tor-0.1.0.15.tar.gz; -cd tor-0.1.0.15. Then ./configure && make. Now you -can run tor as src/or/tor, or you can run make install -(as root if necessary) to install it into /usr/local/, and then you can -start it just by running tor. -

- -

Tor comes configured as a client by default. It uses a built-in -default configuration file, and most people won't need to change any of -the settings. Tor is now installed. -

- -
- -

Step Two: Install Privoxy for Web Browsing

-
- -

After installing Tor, you need to configure your applications to use it. -

- -

-The first step is to set up web browsing. Start by installing Privoxy: click on 'recent releases' -and pick your favorite package or install from source. Privoxy is a -filtering web proxy that integrates well with Tor. -

- -

You need to configure Privoxy to use Tor. -Open Privoxy's "config" file (look in /etc/privoxy/ or /usr/local/etc/) -and add the line
-forward-socks4a / localhost:9050 .
-to the top of the config file. Don't forget to add the dot at the end. -

- -

Privoxy keeps a log file of everything passed through it. In -order to stop this you will need to comment out two lines by inserting a -# before the line. The two lines are:
-logfile logfile
-and the line
-jarfile jarfile
-

- -

You'll need to restart Privoxy for the changes to take effect.

- -
- -

Step Three: Configure your applications to use Tor

-
- -

After installing Tor and Privoxy, you need to configure your -applications to use them. The first step is to set up web browsing.

- -

If you're using Firefox (we recommend it), check out our Tor SwitchProxy howto to set up -a plugin that makes it easy to switch between using Tor and using a -direct connection.

- -

Otherwise, you need to manually configure your browser to HTTP proxy -at localhost port 8118. -(That's where Privoxy listens.) -In Mozilla, this is in Edit|Preferences|Advanced|Proxies. -In Opera 7.5x it's Tools|Preferences|Network|Proxy servers. -You should click the "use the same proxy server for all protocols" -button; but see this -note about Tor and ftp proxies. - -

Using privoxy is necessary because browsers -leak your DNS requests when they use a SOCKS proxy directly, which -is bad for your anonymity. Privoxy also removes certain dangerous -headers from your web requests, and blocks obnoxious ad sites like -Doubleclick.

- -

To Torify other applications that support HTTP proxies, just -point them at Privoxy (that is, localhost port 8118). To use SOCKS -directly (for instant messaging, Jabber, IRC, etc), you can point -your application directly at Tor (localhost port 9050), but see this -FAQ entry for why this may be dangerous. For applications -that support neither SOCKS nor HTTP, take a look at tsocks or socat. -

- -

For information on how to Torify other applications, check out the -Torify -HOWTO. -

- -
- -

Step Four: Make sure it's working

-
- -

-Next, you should try using your browser with Tor and make -sure that your IP address is being anonymized. Click on the Tor -detector and see whether it thinks you're using Tor or not. -(If that site is down, see this -FAQ entry for more suggestions on how to test your Tor.) -

- -

If you have a personal firewall that limits your computer's -ability to connect to itself (this includes something like SELinux on -Fedora Core 4), be sure to allow connections from -your local applications to Privoxy (local port 8118) and Tor (local port -9050). If -your firewall blocks outgoing connections, punch a hole so -it can connect to at least TCP ports 80 and 443, and then see this -FAQ entry. If your SELinux config is not allowing tor or privoxy to -run correctly, create a file named booleans.local in the directory -/etc/selinux/targeted. Edit this file in your favorite text editor and -insert "allow_ypbind=1". Restart your machine for this change to take -effect. -

- -

If it's still not working, look at this -FAQ entry for hints.

- -
- -

Step Five: Configure it as a server

-
- -

The Tor network relies on volunteers to donate bandwidth. The more -people who run servers, 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 server too. We have many features that make Tor servers easy -and convenient, including rate limiting for bandwidth, exit policies so -you can limit your exposure to abuse complaints, and support for dynamic -IP addresses.

- -

Having servers in many different places on the Internet is what -makes Tor users secure. You -may also get stronger anonymity yourself, -since remote sites can't know whether connections originated at your -computer or were relayed from others.

- -

Read more at our Configuring a server -guide.

- -
- -

If you have suggestions for improving this document, please post -them on our bugtracker in the -website category. Thanks!

- -
-
-
- Webmaster - $Id$ -
diff --git a/doc/tor-doc-win32.es.html b/doc/tor-doc-win32.es.html deleted file mode 100644 index 1300ed3abf..0000000000 --- a/doc/tor-doc-win32.es.html +++ /dev/null @@ -1,192 +0,0 @@ - -Tor MS Windows Install Instructions - - - - - - - - - - - - - - - - - - -
- -
- -

Ejecutando el cliente Tor en MS Windows

-
-

N. del T.(TOR->The Onion Router, el enrutador "cebolla")

-

Nótese que estas son las instrucciones de instalación para ejecutar un cliente -en MS Windows (98, 98SE, NT4, 2000, XP, Server). -Si quieres gestionar tráfico para otros y ayudar a crecer la red Tor, - (házlo por favor), lee la guía -Configurar un servidor (English) - -

- -
- -

Paso Uno: Descarga e Instala Tor

-
- -

La instalacion del "paquete" para MS Windows Tor, -TorCP -(un controlador de Tor que monitoriza y contola Tor), y -Privoxy (un proxy con filtro web) en un solo paquete, -con las tres aplicaciones preconfiguradas para trabajar juntas. -Descarga la versión estable o la experimental. -

- -

-Si quieres configurar un servidor Tor, necesitas instalar la versión experimental. -

- -

Si el paquete no funciona para tus requisitos, puedes descargar Tor desde la página de descargas, y -instalar y configurar Privoxy por ti mismo. -

- -tor installer splash page - -

Si ya has instalado Tor, TorCP, o Privoxy previamente, puedes deseleccionar cualquier componente -que no necesites en cuadro de dialogo mostrado abajo. -

- -select components to install - -

Tras completar la instalacion, los componentes seleccionados se iniciarán automáticamente.

- - -

Si no se inicia TorCP, hacer click con el boton derecho sobre su icono, y aparece un menú contextual -con opcion de iniciar, parar, configurar, ... y salir definitivamente. - - - -

- -

Paso Dos: Configurar tus aplicaciones para Tor

-
- -

Tras instalar Tor y Privoxy, debes configurar tus aplicaciones para usarlos. -El primer paso es configurar tu explorador.

- -

Si usas Firefox (te lo recomendamos), visitar Tor SwitchProxy howto para -configurar una extensión de Firefox que hace muy facil cambiar entre usar Tor o usar conexión directa.

- -

De otro modo debes configurar tu explorador para -HTTP proxy en localhost, port 8118. -(Este es el puerto en el que Privoxy atiende.) -

    -
  • En Mozilla, entrar en Editar|Preferencias|Avanzado|Proxies.
    • -
  • En Opera 7.5x, es en Herramientas|Preferencias|Red|Proxy servers.
    • -
  • En IE, es en Herramientas|Opciones de Internet|Conexiones|Configuración LAN|Avanzado.
    • -
-Deberías marcar la casilla "usar el mismo proxy para todos los protocolos" -pero visita esta nota sobre Tor y ftp proxies. -En IE, aparece algo como esto:

- -Proxy settings in IE - -

Usar Privoxy es necesario porque - -los exploradores fallan al hacer peticiones DNS cuando usan un proxy SOCKS directamente, -lo cual es malo para el anonimato. Privoxy tambien elimina ciertas cabeceras -peligrosas de tus peticiones web, y bloquea incómodos sitios como Doubleclick.

- -

Para usar con TOR otras aplicaciones que soportan proxies HTTP, simplemente -dirigirlo a Privoxy (localhost, puerto 8118). Para usar SOCKS directamente (para -mensajería instantanea, Jabber, IRC, etc.) puedes dirigir tu aplicación directamente -a Tor (localhost, puerto 9050), pero visita esta FAQ -donde se explica por qué esto puede ser peligroso. Para aplicaciones que no soportan ni SOCKS ni HTTP, -visitar SocksCap o -FreeCap. -(FreeCap es free software; SocksCap es propietario)

- -

Para más información sobre como "TOR"ificar otras aplicaciones -visitar Torify -HOWTO. -

- -
- -

Paso Tres: Asegurarse que funciona

-
- -

Comprueba que Privoxy y TorCP se están ejecutando y que TorCP ha iniciado TOR con éxito. -El icono de Privoxy es un circulo azul o verde con una "P" dentro, y TorCP es una -cabeza de cebolla gris con una marca "V" en verde (cuando está activado) como aquí:

- -TorCP Tray Icon - -

Después, deberías intentar usar tu explorador con Tor y asegurarte que tu direccion -IP esta siendo anonimizada. -Visitar Tor detector -y comprobar si cree que usas Tor o no. -(Si este sitio no responde, visitar -esta FAQ para mas sugerencias sobre como testear Tor.) -

- -

Si usas un cortafuegos personal que limita la capacidad de conexión de tu computadora, -asegurate que permite conexiones de aplicaciones locales al puerto local 8118 y al puerto 9050.

-

Si tu cortafuegos bloquea conexiones salientes, configuralo para que puedan hacerse conexiones -al menos por los puertos TCP 80 y 443 y visita -este apartado de la FAQ. -

- -

Si aún no funciona, visita -este apartado de la FAQ -para seguir consejos.

- -
- -

Paso Cuatro: Configurarlo como servidor

-
- -

La red Tor se basa en voluntarios que donan su ancho de banda. -Cuantos más servidores, más rapida será la red Tor. Si tienes al menos 20Kbytes/s en ambos sentidos, -por favor ayuda a Tor configurándolo para que sea Servidor también. Tenemos varias características para que -hacer a Tor servidor sea facil y conveniente, incluyendo limitación del ancho de banda cedido, politicas de -conexiones de salida que pueden limitar tu exposición a casos de abuso, y soporte para IP dinámicas. - -

Tener servidores en varios y diferentes sitios en la Internet es lo que convierte a los usuarios de Tor seguros. -Puedes reforzar tu propio anonimato, -haciendo que sitios remotos no puedan saber si las conexiones se originaron en -tu computadora o fueron iniciadas desde otras.

- -

Lee mas en nuestra guía Configurando un servidor

- -
- -

Si tienes sugerencias para mejorar este documento, por favor envíalas a -nuestro bugtracker en la categoría "website". Gracias!

- -
-
-
- Webmaster - $Id$ -
- diff --git a/doc/tor-doc-win32.html b/doc/tor-doc-win32.html index 769e9facd9..0064eb3169 100644 --- a/doc/tor-doc-win32.html +++ b/doc/tor-doc-win32.html @@ -1,229 +1,18 @@ - - - + + - Tor MS Windows Install Instructions - - - - +Tor Documentation + + - - - - - - - - - - - - -
- -
-

This document is obsolete. See the new Tor documentation page. +href="http://tor.eff.org/documentation.html">Tor documentation page.

-

Running the Tor client on MS Windows

-
- -

-Note that these are the installation instructions for running a Tor -client on MS Windows (98, 98SE, NT4, 2000, XP, Server). -If you want to relay traffic for others to help the network grow (please -do), read the Configuring a server -guide. -

- -
- -

Step One: Download and Install Tor

-
- -

-The install for MS Windows bundles Tor, -TorCP -(a Tor controller that lets you monitor and control Tor), and Privoxy (a filtering web proxy) into -one package, with the three applications pre-configured to work together. -Download either the stable or -the experimental version from the download page. -

- -

-If you want to configure yourself to be a Tor server via TorCP, -you will need the experimental version of the bundle. -

- -

If the bundles don't work for you, you can download Tor by itself -from the download page, and then install -and configure Privoxy on your own. -

- -tor installer splash page - -

If you have previously installed Tor, TorCP, or Privoxy -you can deselect whichever components you do not need to install -in the dialog shown below. -

- -select components to install - -

After you have completed the installer, the components -you selected will automatically be started for you. -

- - - -
- -

Step Two: Configure your applications to use Tor

-
- -

After installing Tor and Privoxy, you need to configure your -applications to use them. The first step is to set up web browsing.

- -

If you're using Firefox (we recommend it), check out our Tor SwitchProxy howto to set up -a plugin that makes it easy to switch between using Tor and using a -direct connection.

- -

Otherwise, you need to manually configure your browser to HTTP proxy -at localhost port 8118. -(That's where Privoxy listens.) -In Mozilla, this is in Edit|Preferences|Advanced|Proxies. -In Opera 7.5x it's Tools|Preferences|Network|Proxy servers. -In IE, it's Tools|Internet Options|Connections|LAN Settings|Advanced. -You should click the "use the same proxy server for all protocols" -button; but see this -note about Tor and ftp proxies. -In IE, this looks something like:

- -Proxy settings in IE - -

Using Privoxy is necessary because browsers -leak your DNS requests when they use a SOCKS proxy directly, which -is bad for your anonymity. Privoxy also removes certain dangerous -headers from your web requests, and blocks obnoxious ad sites like -Doubleclick.

- -

To Torify other applications that support HTTP proxies, just -point them at Privoxy (that is, localhost port 8118). To use SOCKS -directly (for instant messaging, Jabber, IRC, etc), you can point -your application directly at Tor (localhost port 9050), but see this -FAQ entry for why this may be dangerous. For applications -that support neither SOCKS nor HTTP, take a look at SocksCap or -FreeCap. -(FreeCap is free software; SocksCap is proprietary.)

- -

For information on how to Torify other applications, check out the -Torify -HOWTO. -

- -
- -

Step Three: Make sure it's working

-
- -

-Check to see that Privoxy and TorCP are running and that TorCP has -successfully started Tor. Privoxy's icon is a green or blue circle with a "P" -in it, and TorCP uses a fat grey onion with a green checkmark in your -system notification area, as shown below: -

- -TorCP Tray Icon - -

-Next, you should try using your browser with Tor and make -sure that your IP address is being anonymized. Click on the Tor -detector and see whether it thinks you're using Tor or not. -(If that site is down, see this -FAQ entry for more suggestions on how to test your Tor.) -

- -

If you have a personal firewall that limits your computer's -ability to connect to itself, be sure to allow connections from -your local applications to local port 8118 and port 9050. If -your firewall blocks outgoing connections, punch a hole so -it can connect to at least TCP ports 80 and 443, and then see this -FAQ entry. -

- -

If it's still not working, look at this -FAQ entry for hints.

- -
- -

Step Four: Configure it as a server

-
- -

The Tor network relies on volunteers to donate bandwidth. The more -people who run servers, 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 server too. We have many features that make Tor servers easy -and convenient, including rate limiting for bandwidth, exit policies so -you can limit your exposure to abuse complaints, and support for dynamic -IP addresses.

- -

Having servers in many different places on the Internet is what -makes Tor users secure. You -may also get stronger anonymity yourself, -since remote sites can't know whether connections originated at your -computer or were relayed from others.

- -

Read more at our Configuring a server -guide.

- -
- -

If you have suggestions for improving this document, please post -them on our bugtracker in the -website category. Thanks!

- -
-
-
- Webmaster - $Id$ -
diff --git a/doc/tor-doc.css b/doc/tor-doc.css deleted file mode 100644 index 82d673b1ac..0000000000 --- a/doc/tor-doc.css +++ /dev/null @@ -1,89 +0,0 @@ -/* ******************************************************* - $Id$ - - This file is maintained in CVS; edit the version in the - repository. - ******************************************************* - */ - -BODY { - background-color: #FFF; - color: #000; -} - -P, TD, TH, DD, DT, LI { - font-family: lucida, "Lucida Sans", "Geneva", sans-serif; -} - -TH, DT { - font-weight: bold; -} - -H1, H2, H3, H4, H5, H6 { - font-family: lucida, "Lucida Sans", "Geneva", sans-serif; -} - -H1 { - text-align: center; -} - -H2, H3, H4, H5, H6 { - text-align: left; -} - -H2 { - background-color: #AFA; - color: #000; - padding: 2px 2px 2px 2px; - border-width: 2px 2px 2px 2px; - border-color: #000; - border-style: solid; -} - -H3 { - background-color: #CCF; - color: #000; - padding: 2px 2px 2px 2px; - margin: 0 0 0 1em; - border-width: 2px 2px 2px 2px; - border-color: #000; - border-style: solid; -} - -DIV.answer { - margin: 0 0 0 2em; -} - -SPAN.heading { - background-color: #ABF; - color: #000; - border-width: 1px; - padding: 0 0.2em 0 0.2em; - border-color: #000; - border-style: solid; -} - -SPAN.date { - background-color: #FFF; - color: #0A0; - font-weight: bold; -} - -P.date { - background-color: #FFF; - color: #0A0; - font-weight: bold; - margin-bottom: 0; -} - -P.news { - margin-top: 0; - margin-left: 3em; -} - -P.credit { - font-size: smaller; - font-style: italic; - padding-left: 3px; - border-left: 3px solid; -} \ No newline at end of file diff --git a/doc/tor-doc.html b/doc/tor-doc.html index 8edb03f39e..0064eb3169 100644 --- a/doc/tor-doc.html +++ b/doc/tor-doc.html @@ -4,64 +4,15 @@ Tor Documentation - - -

Tor documentation

-

This document is obsolete. See the new Tor documentation page.

- -

Why should I use Tor?

- -

See the first section of the Tor Overview to read about -the variety of users Tor has. -

- - - -

Installing and configuring Tor

- -

See the Windows, -OS X, and Linux/BSD/Unix documentation guides. - - - -

Configuring a server

- -

-We've moved this section over to the new -Tor Server -Configuration Guide. Hope you like it. -

- - -

Configuring a hidden service

- -

-We've moved this section over to the new Tor Hidden Service -Howto. Hope you like it. -

- - -

Setting up your own network

- -

-See the new -FAQ entry for how to set up your -own Tor network. -

- diff --git a/doc/tor-hidden-service.html b/doc/tor-hidden-service.html index 1d2085a975..0064eb3169 100644 --- a/doc/tor-hidden-service.html +++ b/doc/tor-hidden-service.html @@ -1,314 +1,18 @@ - - - + + - Tor Hidden Service Configuration Instructions - - - - +Tor Documentation + + - - - - - - - - - - - - -
- -
-

This document is obsolete. See the new Tor documentation page. +href="http://tor.eff.org/documentation.html">Tor documentation page.

-

Configuring Hidden Services for Tor

-
- -

Tor allows clients and servers to offer hidden services. That is, -you can offer a web server, SSH server, etc., without revealing your -IP to its users. In fact, because you don't use any public address, -you can run a hidden service from behind your firewall. -

- -

If you have Tor and Privoxy installed, you can see hidden services -in action by visiting the -hidden wiki. -

- -

This howto describes the steps for setting up your own hidden service -website. -

- -
- -

Step Zero: Get Tor and Privoxy working

-
- -

Before you start, you need to make sure 1) Tor is up and running, -2) Privoxy is up and running, 3) Privoxy is configured to point -to Tor, and 4) You actually set it up correctly.

- -

Windows users should follow the Windows -howto, OS X users should follow the OS -X howto, and Linux/BSD/Unix users should follow the Unix howto. -

- -

Once you've got Tor and Privoxy installed and configured, -you can see hidden services in action by following this link to the hidden wiki. -It will typically take 10-60 seconds to load -(or to decide that it is currently unreachable). If it fails -immediately and your browser pops up an alert saying that -"www.6sxoyfb3h2nvok2d.onion could not be found, please check the name and -try again" then you haven't configured Tor and Privoxy correctly; see this -FAQ entry for some help. -

- -
- -

Step One: Configure an example hidden service

-
- -

In this step, you're going to configure a hidden service that points -to www.google.com. This way we can make sure you have this step -working before we start thinking about setting up a web server locally. -

- -

First, open your torrc file in your favorite text editor. (See this -FAQ entry to learn what this means.) Go to the middle section and -look for the line

- -
-############### This section is just for location-hidden services ###
-
- -

-This section of the file consists of groups of lines, each representing -one hidden service. Right now they are all commented out (the lines -start with #), so hidden services are disabled. Each group of lines -consists of one HiddenServiceDir line, and one or more HiddenServicePort -lines:

-
    -
  • HiddenServiceDir is a directory where Tor will store information -about that hidden service. In particular, Tor will create a file here named -hostname which will tell you the onion URL. You don't need to add any -files to this directory.
    • -
  • HiddenServicePort lets you specify a virtual port (that is, what -port people accessing the hidden service will think they're using) and an -IP address and port for redirecting connections to this virtual port.
    • -
- -

In this example, we're going to set up a hidden service that points to -Google. So add the following lines to your torrc: -

- -
-HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
-HiddenServicePort 80 www.google.com:80
-
- -

You're going to want to change the HiddenServiceDir line, so it points -to an actual directory that is readable/writeable by the user that will -be running Tor. The above line should work if you're using the OS X Tor -package. On Unix, try "/home/username/hidserv/" and fill in your own -username in place of "username". On Windows you might pick:

-
-HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\
-HiddenServicePort 80 www.google.com:80
-
- -

Now save the torrc, shut down -your Tor, and then start it again. (See this -FAQ entry for tips on restarting Tor.) -

- -

If Tor starts up again, great. Otherwise, something is wrong. Look -at your torrc for obvious mistakes like typos. Then double-check -that the directory you picked is writeable by you. If it's still -not working, you should look at the Tor logs for hints. (See this -FAQ entry if you don't know how to enable or find your log file.) -

- -

When Tor starts, it will automatically create the HiddenServiceDir -that you specified (if necessary), and it will create two files there. -First, it will generate a new -public/private keypair for your hidden service, and write it into a -file called "private_key". Don't share this key with others -- if you -do they will be able to impersonate your hidden service. -

- -

The other file it will create is called "hostname". This contains -a short summary of your public key -- it will look something like -6sxoyfb3h2nvok2d.onion. This is the public name for your service, -and you can tell it to people, publish it on websites, put it on business -cards, etc. (If Tor runs as a different user than you, for example on -OS X, Debian, or Red Hat, then you may need to become root to be able -to view these files.) -

- -

Now that you've restarted Tor, it is busy picking introduction points -in the Tor network, and generating what's called a "hidden service -descriptor", which is a signed list of introduction points along with -the service's full public key. It anonymously publishes this descriptor -to the directory servers, and other people anonymously fetch it from the -directory servers when they're trying to access your service. -

- -

Try it now: paste the contents of the hostname file into your web -browser. If it works, you'll get the google frontpage, but the URL in your -browser's window will be your hidden service hostname. If it doesn't work, -look in your logs for some hints, and keep playing with it until it works. -

- -
- -

Step Two: Now install a web server locally

-
- -

Now that you have hidden services working on Tor, you need to -set up your web server locally. Setting up a web server is tricky, -so we're just going to go over a few basics here. If you get stuck -or want to do more, find a friend who can help you. We recommend you -install a new separate web server for your hidden service, since even -if you already have one installed, you may be using it (or want to use -it later) for an actual website. -

- -

If you're on Unix or OS X and you're comfortable with -the command-line, by far the best way to go is to install thttpd. Just grab the -latest tarball, untar it (it will create its own directory), and run -./configure && make. Then mkdir hidserv, cd hidserv, and run -"../thttpd -p 5222 -h localhost". It will give you back your prompt, -and now you're running a webserver on port 5222. You can put files to -serve in the hidserv directory. -

- -

If you're on Windows, ...what should we suggest here? Is there -a good simple free software (not -just "freeware") web server for Windows? Please -let me know what we should say here. In the meantime, -check out apache, -and be sure to -configure it to bind only to localhost. You should also figure out -what port you're listening on, because you'll use it below. -

- -

(The reason we bind the web server only to localhost is to make -sure it isn't publically accessible. If people could get to it directly, -they could confirm that your computer is the one offering the hidden -service.) -

- -

Once you've got your web server set up, make sure it works: open your -browser and go to http://localhost:5222/. Then -try putting a file -in the main html directory, and make sure it shows up when you access -the site. -

- -
- -

Step Three: Connect your web server to your hidden service

-
- -

This part is very simple. Open up your torrc again, and change the -HiddenServicePort line from "www.google.com:80" to "localhost:5222". -Then restart -Tor. Make sure that it's working by reloading your hidden -service hostname in your browser. -

- -
- -

Step Four: More advanced tips

-
- -

If you plan to keep your service available for a long time, you might -want to make a backup copy of the private_key file somewhere. -

- -

We avoided recommending Apache above, a) because many people might -already be running it for a public web server on their computer, and b) -because it's big -and has lots of places where it might reveal your IP address or other -identifying information, for example in 404 pages. For people who need -more functionality, though, Apache may be the right answer. Can -somebody make us a checklist of ways to lock down your Apache when you're -using it as a hidden service? -

- -

If you want to forward multiple virtual ports for a single hidden -service, just add more HiddenServicePort lines. -If you want to run multiple hidden services from the same Tor -client, just add another HiddenServiceDir line. All the following -HiddenServicePort lines refer to this HiddenServiceDir line, until -you add another HiddenServiceDir line: -

- -
-HiddenServiceDir /usr/local/etc/tor/hidden_service/
-HiddenServicePort 80 127.0.0.1:8080
-
-HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
-HiddenServicePort 6667 127.0.0.1:6667
-HiddenServicePort 22 127.0.0.1:22
-
- -

There are some anonymity issues you should keep in mind too: -

-
    -
  • As mentioned above, be careful of letting your web server reveal -identifying information about you, your computer, or your location. -For example, readers can probably determine whether it's thttpd or -Apache, and learn something about your operating system.
    • -
  • If your computer isn't online all the time, your hidden service -won't be either. This leaks information to an observant adversary.
    • - -
- - - -
- -

If you have suggestions for improving this document, please send them to us. Thanks!

- -
-
-
- Webmaster - $Id$ -
diff --git a/doc/tor-switchproxy.html b/doc/tor-switchproxy.html index 1855822943..0064eb3169 100644 --- a/doc/tor-switchproxy.html +++ b/doc/tor-switchproxy.html @@ -1,196 +1,18 @@ - - - + + - Tor SwitchProxy Install Instructions - - - - +Tor Documentation + + - - - - - - - - - - - - -
- -
-

This document is obsolete. See the new Tor documentation page. +href="http://tor.eff.org/documentation.html">Tor documentation page.

-

Installing SwitchProxy for Tor

-
- -

-SwitchProxy is a Firefox plugin that makes it easy for you to switch -between using a proxy and connecting to websites directly.

- -

In this howto, you'll set up SwitchProxy to let you change -between using Tor and a direct connection. We assume you already -have Firefox installed and working.

- -

The screenshots here are oriented towards Windows users, but -SwitchProxy works anywhere Firefox works. Hopefully everybody else can -follow along just fine.

- -
- -

Step Zero: Download and Install Tor and Privoxy

-
- -

Before you start, you need to make sure 1) Tor is up and running, -2) Privoxy is up and running, and 3) Privoxy is configured to point -to Tor.

- -

Windows users need to do step one -of the Windows Tor installation howto, and Mac OS X users need to do step one -of OS X Tor installation howto, since our Win32 and OS X packages include -Privoxy and configure it already. Linux/BSD/Unix users should do step one -and step -two of the Unix Tor installation howto. -

- -
- -

Step One: Download and Install SwitchProxy

-
- -

SwitchProxy is a Firefox plugin, so you need to go through -the process of installing a new plugin. First, go to the -SwitchProxy web page. If you're using Firefox 1.5, you might need to -download SwitchProxy from -here instead. -Turn on JavaScript for now and click "Install Now":

- -switchproxy web page - -

It will pop up a window asking for permission to install the plugin. -Click on the "Install Now" button: -

- -firefox plugin warning - -

Once the installer is finished, you should close all of your Firefox -windows and restart Firefox.

- -firefox plugin finished - -
- -

Step Two: Configure SwitchProxy

-
- -

When you restart Firefox, you'll notice there's a new toolbar -that lets you control your proxies. Now we're going to set up a proxy -configuration for Tor. Click on "Add" in the new Proxy toolbar:

- -new toolbar - -

It will ask you to select a proxy type. Choose -"Standard." (There's also an "anonymous" proxy type that -uses an ad hoc set of anonymous proxies out there. You -don't want this, because those other "anonymous" proxies give -you much weaker security than Tor.) -

- -standard proxy - -

Now it will show you the standard proxy config window for Firefox. -Give this configuration a proxy label of "tor". Then fill in "localhost" -and "8118" for all four entries, as shown here. (Even -though Privoxy doesn't support FTP and Gopher, you -should set them up anyway.) Then click "OK":

- -proxy config - -

Now you've created the "tor" proxy label, but you're not using it yet. -Click on the pull-down list and select tor, as shown here:

- -switch to tor - -

Almost done. Click "Apply" to make your change take effect:

- -apply - -

Done! Firefox will reload your current page. In -this example screenshot, it reloaded the page and happened -to get a German exit node:

- -german google - -
- -

Step Step Three: Check if it works

-
- -

Now Firefox is using Privoxy as an HTTP proxy, Privoxy is using Tor as -a socks4a proxy, and Tor is making your connections to the Internet.

- -

In the above example, it was clear that it worked because the web -page showed up in a different language. In other cases, though, -you'll want to verify that your setup is working. Do -step three -of the Windows Tor installation howto, or -step three -of the OS X Tor installation howto.

- -

You should be aware of one anonymity gotcha: when you switch from -using Tor to a direct connection (or vice versa), by default the page -that's currently active will be reloaded through the new proxy setting. -So make sure you're on a page that isn't sensitive, before switching. -(You can also change this behavior in SwitchProxy's "Options | -Preferences" menu.)

- -
- -

If you have suggestions for improving this document, please send them to us. Thanks!

- -
-
-
- Webmaster - $Id$ -