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

Nick Mathewson ee9e54b434 Make buffers grow and shrink as needed. 21 years ago
Win32Build 1777487f4e Tor now builds on win32. 21 years ago
doc 411a18e34c put out 0.0.2pre12 21 years ago
src ee9e54b434 Make buffers grow and shrink as needed. 21 years ago
.cvsignore 03544caca7 Make cvsignores reflect build process 21 years ago
AUTHORS f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 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 88a068b594 don't forget the dot in privoxy config line. 21 years ago
LICENSE 9fcd893e8b fill in some blanks 21 years ago
Makefile.am de6cbe53c0 some early bugfixes 21 years ago
NEWS f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
README 5ccb28c335 remove more confusing parts of the README 21 years ago
autogen.sh dcc9fa8657 ./autogen.sh runs auto* and then ./configure 22 years ago
configure.in 411a18e34c put out 0.0.2pre12 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

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, set up a config file for your node (start with sample-orrc and
edit the top portion). Then run the node (as above, but with the new
config file) 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.