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

Roger Dingledine b1d8973990 figured out how to make autoconf a bit less viral il y a 20 ans
Win32Build 1777487f4e Tor now builds on win32. il y a 21 ans
doc 0396449097 add the dirservers section il y a 20 ans
src faa0f7ffe7 Use daemon(3) function where available. il y a 20 ans
.cvsignore 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements il y a 20 ans
AUTHORS ba7236ee59 spell matej's name correctly (oops) il y a 20 ans
ChangeLog f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. il y a 22 ans
INSTALL 9981177001 update install and readme: people should now do 'make install' il y a 20 ans
LICENSE 9fcd893e8b fill in some blanks il y a 20 ans
Makefile.am b1d8973990 figured out how to make autoconf a bit less viral il y a 20 ans
README f84cdb9005 force the admin to mkdir the datadirectory himself, il y a 20 ans
autogen.sh dcc9fa8657 ./autogen.sh runs auto* and then ./configure il y a 22 ans
configure.in faa0f7ffe7 Use daemon(3) function where available. il y a 20 ans
depcomp f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. il y a 22 ans
install-sh f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. il y a 22 ans
missing f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. il y a 22 ans
mkinstalldirs f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. il y a 22 ans
tor.sh.in 25b0c92f0f patch from aaron to abstract into $TORARGS il y a 20 ans

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.