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

Peter Palfrader 0430b4c5a0 Move design-paper into its own directory, and ship it and all that is needed to build with it in the tarball 20 years ago
Win32Build 17b5b3685f Make tor build on win32 again; handle locking for server 20 years ago
contrib a450909716 rename tor_resolve to tor-resolve 20 years ago
debian 6a022bdcdc Fix changelog 20 years ago
doc 0430b4c5a0 Move design-paper into its own directory, and ship it and all that is needed to build with it in the tarball 20 years ago
src 2ff6d6d8b9 There is no space after network-status; make router_get_hash_impl more bulletproof. 20 years ago
.cvsignore 9d2cd7fc6e Allow multiple logfiles at different severity ranges 20 years ago
AUTHORS 51ca94fef3 add jbash and weasel to the AUTHORS list 20 years ago
ChangeLog c577fd497f add pre2 release notes to changelog 20 years ago
Doxyfile d15a95145e Add Doxygen config file and make target, along with section in HACKING document 20 years ago
INSTALL f9a0409714 mention that you should proxy your SSL traffic too 20 years ago
LICENSE 431c8ad63b extend copyright to 2004 20 years ago
Makefile.am d15a95145e Add Doxygen config file and make target, along with section in HACKING document 20 years ago
README 82a7855359 Ask people to be a little more verbose in the mails they send to tor-ops 20 years ago
autogen.sh 0430b4c5a0 Move design-paper into its own directory, and ship it and all that is needed to build with it in the tarball 20 years ago
configure.in 0430b4c5a0 Move design-paper into its own directory, and ship it and all that is needed to build with it in the tarball 20 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?

We're looking for people with reasonably reliable Internet connections,
that have at least 768kbit each way. Currently we don't use all of that,
but we want it available for burst traffic.

First, copy torrc.sample to torrc (by default it's in
/usr/local/etc/tor/), and edit the middle part. 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.

Then run tor to generate keys. One of the files generated
in your DataDirectory is your 'fingerprint' file. Mail it to
tor-ops@freehaven.net.

Please also tell us in that mail who you are, so we know whom to contact
if there's any problem. Also describe what kind of connectivity the new
server will have. If possible PGP sign your mail.

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.

Do you want to run a hidden service?

Copy torrc.sample to torrc (by default it's in /usr/local/etc/tor/), and
edit the bottom part. Then run Tor. It will create each HiddenServiceDir
you have configured, and it will create a 'hostname' file which
specifies the url (xyz.onion) for that service. You can tell people
the url, and they can connect to it via their Tor client.

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.