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

Roger Dingledine 30520b926c solaris no longer needs special ./configure directions 20 lat temu
Win32Build 3c15876603 Turns out, these files should not actually be in cvs! 20 lat temu
contrib d16f142fa9 fix the rpm spec description again 20 lat temu
debian 52356f3e16 And tree.h is by Nils. Thanks arma 20 lat temu
doc 50354cbae7 Add TODO item to make everything use mark_for_close; not doing so will now skew the stats 20 lat temu
src ed0ef86c0e make OR not crash when non-OR connection dies 20 lat temu
.cvsignore 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements 20 lat temu
AUTHORS 51ca94fef3 add jbash and weasel to the AUTHORS list 20 lat temu
ChangeLog 161d7d19ae our changelog for 0.0.2 20 lat temu
INSTALL 30520b926c solaris no longer needs special ./configure directions 20 lat temu
LICENSE 431c8ad63b extend copyright to 2004 20 lat temu
Makefile.am a1503f667e Integrate jbash's RPM spec into build process. (Requires "rpmbuild" to 20 lat temu
README 325935b1c6 doc patches submitted by jason holt 20 lat temu
autogen.sh 01cf9c2dd8 don't --enable-debug by default on ./configure 20 lat temu
configure.in e5cf396285 oops, and make make work too on solaris 20 lat temu
depcomp f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 lat temu
install-sh f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 lat temu
missing f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 lat temu
mkinstalldirs f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 lat temu

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.