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

Nick Mathewson 06624df622 Log number of bytes pending after read. 20 years ago
Win32Build 3c15876603 Turns out, these files should not actually be in cvs! 20 years ago
contrib a1a4c5be19 Update cvsignores 20 years ago
debian 2b1441e49f New upstream release candidate. 20 years ago
doc b4b9b27adb rewrite the todo list 20 years ago
src 06624df622 Log number of bytes pending after read. 20 years ago
.cvsignore 2c81a6cb1d Remove automake files from cvs. Let's see whether it works for Roger too. 20 years ago
AUTHORS 51ca94fef3 add jbash and weasel to the AUTHORS list 21 years ago
ChangeLog 3dad8557a6 commit a changelog for 0.0.5 20 years ago
INSTALL 30520b926c solaris no longer needs special ./configure directions 20 years ago
LICENSE 431c8ad63b extend copyright to 2004 20 years ago
Makefile.am a1503f667e Integrate jbash's RPM spec into build process. (Requires "rpmbuild" to 20 years ago
README 736bc9628e add 'Do you want to run a hidden service?' section 20 years ago
autogen.sh 2c81a6cb1d Remove automake files from cvs. Let's see whether it works for Roger too. 20 years ago
configure.in 1b4dd10cfe bump us to rc2 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?

First, copy torrc.sample to torrc 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
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.

Do you want to run a hidden service?

Copy torrc.sample to torrc, 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 proxy.

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.