Code added to Tor to support PIR-based onion service descriptor lookups

Roger Dingledine f84cdb9005 force the admin to mkdir the datadirectory himself, 21 years ago
Win32Build 1777487f4e Tor now builds on win32. 21 years ago
doc 1bf10257da fill in some lncs numbers 21 years ago
src 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements 21 years ago
.cvsignore 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements 21 years ago
AUTHORS ba7236ee59 spell matej's name correctly (oops) 21 years ago
COPYING 99df8ea487 and give it some content 21 years ago
ChangeLog f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
INSTALL 9981177001 update install and readme: people should now do 'make install' 21 years ago
LICENSE 9fcd893e8b fill in some blanks 21 years ago
Makefile.am f84cdb9005 force the admin to mkdir the datadirectory himself, 21 years ago
NEWS f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
README f84cdb9005 force the admin to mkdir the datadirectory himself, 21 years ago
autogen.sh dcc9fa8657 ./autogen.sh runs auto* and then ./configure 22 years ago
configure.in b4117d2a37 move to 0.0.2pre13 21 years ago
depcomp f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
install-sh f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
missing f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
mkinstalldirs f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
tor.sh.in 25b0c92f0f patch from aaron to abstract into $TORARGS 21 years ago

README


'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, move sample-server-torrc onto torrc, and edit it. 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. 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.

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.