aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2003-10-22 04:33:11 +0000
committerRoger Dingledine <arma@torproject.org>2003-10-22 04:33:11 +0000
commitf84cdb9005317d12453395bf98c24626a918456a (patch)
treed66094e03157bba399d9e6e3613ae7e32d5f5c02 /README
parent1bf10257dad2a9070e2d408b2285922422b39e44 (diff)
downloadtor-f84cdb9005317d12453395bf98c24626a918456a.tar
tor-f84cdb9005317d12453395bf98c24626a918456a.tar.gz
force the admin to mkdir the datadirectory himself,
so he gets the permissions right. also this means clients will never need to make the datadirectory. also remind the admin to fix his clock before setting up his node. svn:r650
Diffstat (limited to 'README')
-rw-r--r--README11
1 files changed, 7 insertions, 4 deletions
diff --git a/README b/README
index fbe27b611..1f1e13eaa 100644
--- a/README
+++ b/README
@@ -17,10 +17,13 @@ doesn't work for you.
Do you want to run a tor server?
- First, move sample-server-torrc onto torrc, and edit it. Then run tor
- 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.
+ First, move sample-server-torrc onto torrc, and edit it. 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. Then run tor
+ 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: