mirror repository of the tor core protocol in case of issues
Go to file
2004-03-20 20:48:27 +00:00
contrib fix the rpm spec description again 2004-03-02 19:28:15 +00:00
debian And tree.h is by Nils. Thanks arma 2004-03-20 02:07:37 +00:00
doc Add TODO item to make everything use mark_for_close; not doing so will now skew the stats 2004-03-20 04:57:27 +00:00
src make OR not crash when non-OR connection dies 2004-03-20 20:37:49 +00:00
Win32Build Turns out, these files should not actually be in cvs! 2004-03-18 04:54:54 +00:00
.cvsignore Update .cvsignores to exclude files generated due to recent build improvements 2003-10-21 17:49:52 +00:00
AUTHORS add jbash and weasel to the AUTHORS list 2004-02-17 05:05:34 +00:00
autogen.sh don't --enable-debug by default on ./configure 2003-12-03 09:53:46 +00:00
ChangeLog our changelog for 0.0.2 2004-03-19 07:08:15 +00:00
configure.in oops, and make make work too on solaris 2004-03-20 20:08:19 +00:00
depcomp added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
INSTALL solaris no longer needs special ./configure directions 2004-03-20 20:48:27 +00:00
install-sh added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +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
missing added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
mkinstalldirs added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
README doc patches submitted by jason holt 2003-12-13 22:56:32 +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, edit the bottom part of your torrc. 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.