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

Roger Dingledine 5d48aa622a patch the README more for new routers 20 jaren geleden
Win32Build 1777487f4e Tor now builds on win32. 21 jaren geleden
doc 42b2f341a4 add a few more new TODO items (bugfixes) 20 jaren geleden
src a27b570788 bugfix for win32 with lots of users 20 jaren geleden
.cvsignore 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements 20 jaren geleden
AUTHORS 5d48aa622a patch the README more for new routers 20 jaren geleden
ChangeLog f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 jaren geleden
INSTALL 9981177001 update install and readme: people should now do 'make install' 20 jaren geleden
LICENSE 9fcd893e8b fill in some blanks 20 jaren geleden
Makefile.am b1d8973990 figured out how to make autoconf a bit less viral 20 jaren geleden
README 5d48aa622a patch the README more for new routers 20 jaren geleden
autogen.sh dcc9fa8657 ./autogen.sh runs auto* and then ./configure 22 jaren geleden
configure.in faa0f7ffe7 Use daemon(3) function where available. 20 jaren geleden
depcomp f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 jaren geleden
install-sh f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 jaren geleden
missing f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 jaren geleden
mkinstalldirs f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 jaren geleden
tor.sh.in 25b0c92f0f patch from aaron to abstract into $TORARGS 20 jaren geleden

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. 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.

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.