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

Nick Mathewson 1694315a1d Tighten paper a little; drop a couple of inches of whitespace. 21 anni fa
Win32Build 1777487f4e Tor now builds on win32. 21 anni fa
debian 2125da817b adduser is not essential 21 anni fa
doc 1694315a1d Tighten paper a little; drop a couple of inches of whitespace. 21 anni fa
src deda0d93dd Let AP edges receive 'end' relay cells while waiting for 'connected' 21 anni fa
.cvsignore 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements 21 anni fa
AUTHORS 8bb4f473a9 note Christian Grothoff's daemonize patch 21 anni fa
ChangeLog f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 anni fa
INSTALL 2b765c54f5 rearrange authors, correct install notes 21 anni fa
LICENSE 8222fe8e4f clean up some copyrights 21 anni fa
Makefile.am b1d8973990 figured out how to make autoconf a bit less viral 21 anni fa
README 325935b1c6 doc patches submitted by jason holt 21 anni fa
autogen.sh 01cf9c2dd8 don't --enable-debug by default on ./configure 21 anni fa
configure.in 689823f41b move us to pre19 21 anni fa
depcomp f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 anni fa
install-sh f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 anni fa
missing f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 anni fa
mkinstalldirs f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 anni fa
tor.sh.in b820d3bc42 define the pidfile on the commandline, if you want it 21 anni fa

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