From 6065f89544a0561d685513356cca125d332e0de3 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Wed, 4 Aug 2004 06:23:06 +0000 Subject: [PATCH] update tor-doc.html svn:r2140 --- doc/tor-doc.html | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/doc/tor-doc.html b/doc/tor-doc.html index 03ef71cf93..716883a4ee 100644 --- a/doc/tor-doc.html +++ b/doc/tor-doc.html @@ -47,7 +47,7 @@ rape and abuse survivors, or people with illnesses. home-made movie anonymously via a Tor hidden service; and reading, e.g. of news sites not permitted in some countries. -
  • Allowing their agents to check back with their home website while +
  • Allowing their workers to check back with their home website while they're in a foreign country, without notifying everybody nearby that they're working with that organization. @@ -103,7 +103,7 @@ your security.

    everybody is a client. This means you don't relay traffic for anybody but yourself.

    -

    If you have less than 768kbit in both directions, you should stay +

    If you have less than 1Mbit in both directions, you should stay a client. Otherwise, please consider being a server, to help out the network. (Currently each server uses 20-30 gigabytes of traffic per month; but that may go up.)

    @@ -175,7 +175,7 @@ from localhost. Connections from other computers are refused. If you want to torify applications on different computers than the Tor client, you should copy torrc.sample to torrc (it's installed by default to /usr/local/etc/tor/), change the SocksAddress line to -0.0.0.0, and then restart Tor.

    +0.0.0.0, and then hup or restart Tor.

    To test if it's working, point your browser to socks4 or socks5 proxy at localhost port 9050. In @@ -195,10 +195,10 @@ proxy that integrates well with Tor. Add the line
    (don't forget the dot) to its config file. Then change your mozilla to http proxy at localhost port 8118 (and no socks proxy). You should also set your SSL proxy to the same -thing, to hide your https traffic. Using privoxy will give you good html -scrubbing as well. -(See this explanation -for why direct socks gives you less anonymity.)

    +thing, to hide your https traffic. Using privoxy is necessary because +Mozilla leaks your +DNS requests when it uses a socks proxy directly. Privoxy also gives +you good html scrubbing.

    You might want to use Tor with an application that doesn't support socks directly. In this case, you should look at @@ -213,14 +213,14 @@ service url).

    Configuring a server

    We're looking for people with reasonably reliable Internet connections, -that have at least 768kbit each way. Currently we don't use all of that, +that have at least 1Mbit each way. Currently we don't use all of that, but we want it available for burst traffic.

    -

    The Tor server doesn't need to be run as root, and doesn't +

    (The Tor server doesn't need to be run as root, and doesn't need any special system permissions or kernel mods. If you're the paranoid sort, feel free to put it -into a chroot jail.

    +into a chroot jail.)

    First, copy torrc.sample to torrc (by default it's in /usr/local/etc/tor/), and edit the middle part. Create the DataDirectory, @@ -238,7 +238,8 @@ server will have. If possible, PGP sign your mail.

    NOTE: You won't be able to use tor as a client or server in this configuration until you've been added to the directory -and can authenticate to the other nodes.

    +and can authenticate to the other nodes. (This is no longer the case +for 0.0.8 and after.)

    Once your fingerprint has been approved, you can click here or 4a: Edit src/or/config.c and change the default_dirservers_string array so that it reflects the contents of the new dirservers file instead of the old one. Be sure to get the quotes and newlines and semicolons -right. (This step sucks. Please suggest a better way to handle this -step. ;) +right. (This step sucks. We plan to have it solved by the release of 0.0.8.)

  • 4b: Replace the dirservers file in your sandbox (in src/config/) with the one from step 3. -
  • 4c: edit configure.in, change the AM_INIT_AUTOMAKE(tor, 0.0.6) +
  • 4c: edit configure.in, change the AM_INIT_AUTOMAKE(tor, 0.0.8) line so that it specifies a version that is specific to you, such as -0.0.6-arma. This will help you keep from being confused later. Be sure +0.0.8-arma. This will help you keep from being confused later. Be sure to update the RecommendedVersions lines to include this version.
  • 4d: run ./autogen.sh (you'll need a new enough set of auto* tools), then make dist. @@ -328,13 +328,13 @@ process for each directory server to reload the approved-routers file (so you don't have to restart the process). -

    Other doc resources

    + -- 2.47.3