2003-10-07 18:57:18 +02:00
|
|
|
|
2002-09-23 21:16:00 +02: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/.
|
|
|
|
|
2002-11-23 07:49:01 +01:00
|
|
|
Is your question in the FAQ? Should it be?
|
|
|
|
|
2003-07-14 19:54:56 +02:00
|
|
|
**************************************************************************
|
2003-10-07 23:27:33 +02:00
|
|
|
See the INSTALL file for a quickstart. That is all you will probably need.
|
2003-10-07 18:57:18 +02:00
|
|
|
**************************************************************************
|
2002-09-23 21:16:00 +02:00
|
|
|
|
2003-10-05 07:54:12 +02:00
|
|
|
**************************************************************************
|
2003-10-07 18:57:18 +02:00
|
|
|
You only need to look beyond this point if the quickstart in the INSTALL
|
|
|
|
doesn't work for you.
|
2003-07-14 19:54:56 +02:00
|
|
|
**************************************************************************
|
2002-07-16 18:18:16 +02:00
|
|
|
|
2003-10-05 07:54:12 +02:00
|
|
|
Do you want to run a tor server?
|
|
|
|
|
2003-10-22 06:33:11 +02:00
|
|
|
First, move sample-server-torrc onto torrc, and edit it. Create the
|
|
|
|
DataDirectory, and make sure it's owned by whoever will be running
|
2003-10-27 11:28:26 +01:00
|
|
|
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 generated files is your
|
|
|
|
'fingerprint' file. Mail it to arma@mit.edu. Remember that you won't
|
|
|
|
be able to authenticate to the other tor nodes until I've added you
|
|
|
|
to the directory.
|
2002-07-19 10:13:42 +02:00
|
|
|
|
2003-10-12 01:44:51 +02:00
|
|
|
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:
|
2003-03-16 05:55:19 +01:00
|
|
|
server_port = 9050
|
|
|
|
server = 127.0.0.1
|
2003-07-14 19:54:56 +02:00
|
|
|
(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.)
|
2003-10-12 00:38:44 +02:00
|
|
|
Then you can do "tsocks ssh arma@moria.mit.edu". But note that if
|
2003-03-16 05:55:19 +01:00
|
|
|
ssh is suid root, you either need to do this as root, or cp a local
|
|
|
|
version of ssh that isn't suid.
|
|
|
|
|