mirror repository of the tor core protocol in case of issues
Go to file
Roger Dingledine 2d3ac08633 Refactor directory servers
* read all the time (before we would ignore eof sometimes, oops)
* we can handle different urls now
* send back 404 for an un-handled url
* commands initiated by the client can handle payloads now
* introduce conn->purpose to avoid exponential state-space explosion


svn:r1400
2004-03-30 22:57:49 +00:00
contrib Add more stuff to cvsignores 2004-03-29 20:38:49 +00:00
debian New upstream release 2004-03-30 18:54:40 +00:00
doc Add rendezvous-related metadata and code to circuits. Initially, we 2004-03-30 19:52:42 +00:00
src Refactor directory servers 2004-03-30 22:57:49 +00:00
Win32Build Turns out, these files should not actually be in cvs! 2004-03-18 04:54:54 +00:00
.cvsignore Remove automake files from cvs. Let's see whether it works for Roger too. 2004-03-29 22:09:11 +00:00
AUTHORS add jbash and weasel to the AUTHORS list 2004-02-17 05:05:34 +00:00
autogen.sh Remove automake files from cvs. Let's see whether it works for Roger too. 2004-03-29 22:09:11 +00:00
ChangeLog commit a changelog for 0.0.5 2004-03-30 18:39:05 +00:00
configure.in bump to 0.0.5 2004-03-30 18:34:30 +00:00
INSTALL solaris no longer needs special ./configure directions 2004-03-20 20:48:27 +00:00
LICENSE extend copyright to 2004 2004-03-18 03:00:03 +00:00
Makefile.am Integrate jbash's RPM spec into build process. (Requires "rpmbuild" to 2004-03-02 19:09:30 +00:00
README clean up README to mention torrc.sample 2004-03-30 00:06:20 +00:00

'tor' is an implementation of The Onion Routing system, as
described in a bit more detail at http://www.onion-router.net/. You
can read list archives, and subscribe to the mailing list, at
http://archives.seul.org/or/dev/.

Is your question in the FAQ? Should it be?

**************************************************************************
See the INSTALL file for a quickstart. That is all you will probably need.
**************************************************************************

**************************************************************************
You only need to look beyond this point if the quickstart in the INSTALL
doesn't work for you.
**************************************************************************

Do you want to run a tor server?

  First, copy torrc.sample to torrc and edit the bottom part. Create the
  DataDirectory, and make sure it's owned by whoever will be running
  tor. Fix your system clock so it's not too far off. Make sure name
  resolution works. Make sure other people can reliably resolve the
  Address you chose.

  Then run tor to generate keys. One of the files generated
  in your DataDirectory is your 'fingerprint' file. Mail it to
  arma@mit.edu.

  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.

Configuring tsocks:

  If you want to use Tor for protocols that can't use Privoxy, or
  with applications that are not socksified, then download tsocks
  (tsocks.sourceforge.net) and configure it to talk to localhost:9050
  as a socks4 server. My /etc/tsocks.conf simply has:
    server_port = 9050
    server = 127.0.0.1
  (I had to "cd /usr/lib; ln -s /lib/libtsocks.so" to get the tsocks
   library working after install, since my libpath didn't include /lib.)
  Then you can do "tsocks ssh arma@moria.mit.edu". But note that if
  ssh is suid root, you either need to do this as root, or cp a local
  version of ssh that isn't suid.