From acd37110d2fb5e3dcc2c7638448411e3dbf64aab Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Sun, 19 Dec 2004 07:36:05 +0000 Subject: it is beautiful now svn:r3187 --- doc/tor-doc-win32.html | 18 ++++++++++++------ doc/tor-doc.html | 50 +++++++++++++++++++++----------------------------- 2 files changed, 33 insertions(+), 35 deletions(-) (limited to 'doc') diff --git a/doc/tor-doc-win32.html b/doc/tor-doc-win32.html index 30754571e..b193a3590 100644 --- a/doc/tor-doc-win32.html +++ b/doc/tor-doc-win32.html @@ -1,6 +1,6 @@ -Tor: an anonymizing overlay network for TCP +Tor Win32 Install Instructions @@ -49,11 +49,15 @@ not close it.) default configuration file, and most people won't need to change any of the settings. Tor is now installed.

-

After installing Tor, you should install +

Configuring your applications to use Tor

+ +

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', then scroll down to the Win32 installer packages). Privoxy is a filtering web proxy that integrates well with Tor. Once it's installed, it should -appear in your system tray, as pictured below: +appear in your system tray as a "P" in a circle, as pictured below:

privoxy icon in the system tray @@ -103,9 +107,11 @@ For more troubleshooting suggestions, see the FAQ.

-

To Torify an application that supports http, just point it at -Privoxy. To use socks directly, point it at localhost port 9050. For -applications that support neither socks nor http, take a look at To Torify an application that supports http, just point it at Privoxy +(that is, localhost port 8118). To use socks directly (for example, for +instant messaging, Jabber, IRC, etc), point your application directly at +Tor (localhost port 9050). For applications that support neither socks +nor http, take a look at SocksCap, FreeCap, or the -Tor: an anonymizing overlay network for TCP +Tor Documentation @@ -11,17 +11,10 @@

Tor documentation

-

The simple version: Tor provides a distributed network of servers -("onion routers"). Users bounce their TCP streams (web traffic, FTP, SSH, -etc.) around the routers. This makes it hard for recipients, observers, and -even the onion routers themselves to track the source of the stream.

- -

The complex version: Onion Routing is a connection-oriented anonymizing -communication service. Users choose a source-routed path through a set of -nodes, and negotiate a "virtual circuit" through the network, in which -each node knows its predecessor and successor, but no others. Traffic -flowing down the circuit is unwrapped by a symmetric key at each node, -which reveals the downstream node.

+

Tor provides a distributed network of servers ("onion routers"). Users +bounce their communications (web requests, IM, IRC, SSH, etc.) around +the routers. This makes it hard for recipients, observers, and even the +onion routers themselves to track the source of the stream.

Why should I use Tor?

@@ -133,11 +126,16 @@ server below.

Installing Tor

+

Win32 users can use our Tor installer. See these instructions for help with +installing, configuring, and using Tor on Win32. +

+

You can get the latest releases here.

If you got Tor from a tarball, unpack it: tar xzf -tor-0.0.9.tar.gz; cd tor-0.0.9. Run ./configure, then +tor-0.0.9.1.tar.gz; cd tor-0.0.9.1. Run ./configure, then make, and then make install (as root if necessary). Then you can launch tor from the command-line by running tor. Otherwise, if you got it prepackaged (e.g. in the ), these steps are already done for you, and you may even already have Tor started in the background (logging to /var/log/something).

-

Win32 users can use our Tor installer. It will run Tor in a dos window -so you can see its logs and errors. (You can minimize this window, but -do not close it.) -

-

In any case, see the next section for what to do with it now that you've got it running.

@@ -178,9 +171,8 @@ proxy that integrates well with Tor. Add the line
forward-socks4a / localhost:9050 .
(don't forget the dot) to privoxy's config file (you can just add it to the top). Then change your browser to http proxy at localhost port 8118. -(In Mozilla, this is in Edit|Preferences|Advanced|Proxies. In IE, it's -Tools|Internet Options|Connections|LAN Settings|Advanced.) -You should also set your SSL proxy (IE calls it "Secure") to the same +(In Mozilla, this is in Edit|Preferences|Advanced|Proxies.) +You should also set your SSL proxy to the same thing, to hide your SSL traffic. Using privoxy is necessary because Mozilla leaks your DNS requests when it uses a socks proxy directly. Privoxy also gives @@ -203,9 +195,11 @@ For more troubleshooting suggestions, see the FAQ.

-

To Torify an application that supports http, just point it at -Privoxy. To use socks directly, point it at localhost port 9050. For -applications that support neither socks nor http, you should look at +

To Torify an application that supports http, just point it at Privoxy +(that is, localhost port 8118). To use socks directly (for example, for +instant messaging, Jabber, IRC, etc), point your application directly at +Tor (localhost port 9050). For applications that support neither socks +nor http, you should look at using tsocks to dynamically replace the system calls in your program to route through Tor. If you want to use socks4a, consider using socat (specific instructions are on this hidden service url).

-

(Windows doesn't have tsocks; instead, you can try - SocksCap - or the Hummingbird - SOCKS client.)

+

(Windows doesn't have tsocks; see the bottom of the +Win32 instructions for alternatives.) +

Configuring a server

-- cgit v1.2.3