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

Roger Dingledine af4192b172 start tracking a rare bug: package_raw_inbuf gets called with package_window 0 21 years ago
Win32Build 1777487f4e Tor now builds on win32. 21 years ago
doc 5b99985e79 we have a man page. 21 years ago
src af4192b172 start tracking a rare bug: package_raw_inbuf gets called with package_window 0 21 years ago
.cvsignore 009f2f6dbb Update .cvsignores to exclude files generated due to recent build improvements 21 years ago
AUTHORS 5d48aa622a patch the README more for new routers 21 years ago
ChangeLog f09e25e9f5 added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 22 years ago
INSTALL 84fffd3652 install now recognizes that -l warn is default 21 years ago
LICENSE 9fcd893e8b fill in some blanks 21 years ago
Makefile.am b1d8973990 figured out how to make autoconf a bit less viral 21 years ago
README 2c93463535 change 'so you want to run your own server' directions 21 years ago
autogen.sh dcc9fa8657 ./autogen.sh runs auto* and then ./configure 22 years ago
configure.in 1d9b1550e0 stop building sample-server-torrc, start building tor.1 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
tor.sh.in b820d3bc42 define the pidfile on the commandline, if you want it 21 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, 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. 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.