nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-27 22:03:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

setting up your own tor network is much simpler now

Browse Source 
svn:r2604
This commit is contained in:
Roger Dingledine 2004-10-27 06:24:16 +00:00
parent f67f83b1fa
commit 4a9c747f6e
1 changed files with 14 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
doc/tor-doc.html
View File

@ -284,7 +284,7 @@ servers, and you need to change the tarball so it points to your directory
servers rather than the default ones. servers rather than the default ones.
<ul> <ul>
<li>1: Grab the latest release. <li>1: Grab the latest release. Use at least 0.0.9pre5.
<li>2: For each directory server you want, <li>2: For each directory server you want,
<ul> <ul>
<li>2a: Set it up as a server (see <a href="#server">"setting up a <li>2a: Set it up as a server (see <a href="#server">"setting up a
@ -294,43 +294,24 @@ defined.
<li>2c: Set "RecommendedVersions" to a comma-separated list of acceptable <li>2c: Set "RecommendedVersions" to a comma-separated list of acceptable
versions of the code for clients and servers to be running (see step versions of the code for clients and servers to be running (see step
4c below). 4c below).
<!-- <li>2d: Create a file called approved-routers in your DataDirectory: <li>2d: Run it: <tt>tor --list-fingerprint</tt> if your torrc is in
<tt>touch approved-routers</tt>. It will be empty for now. We'll fill it in the default place, or <tt>tor -f torrc --list-fingerprint</tt> to
step 5. --> specify one. This will generate your keys and output a fingerprint
<li>2d: Create an empty dirservers file (<tt>touch dirservers</tt>). Point line.
RouterFile at it in your torrc.
<li>2e: Run it: <tt>tor -f torrc</tt>. This will generate your keys and a
router.desc (router descriptor) file. It will then exit with a complaint
that it can't open the fingerprint file; that's fine.
</ul> </ul>
<li>3: Create the new dirservers file. You do this by concatenating the <li>3: Create the new dirservers file. You do this by concatenating the
"router.desc" files from each dirserver's DataDirectory: <tt>cat router1.desc "router.desc" files from each dirserver's DataDirectory: <tt>cat router1.desc
router2.desc ... &gt; dirservers</tt> router2.desc ... &gt; dirservers</tt>
<li>4: Now you need to teach clients and servers to use the new <li>4a: Now you need to teach clients and servers to use the new
dirservers file. First, check out the tor cvs repository (instructions <a dirservers. For each fingerprint, add a line like<br>
href="http://freehaven.net/tor/">here</a> -- be sure to check out the <tt>DirServer 18.244.0.114:80 719B E45D E224 B607 C537 07D0 E214 3E2D 423E 74CF</tt><br>
tag that matches the version of the code you intend to use; and note that to the torrc of each client and server who will be using your network.
the latest cvs version may not compile or work right). Then:
<ul>
<li>4a: Edit src/or/config.c and change the default_dirservers_string array
so that it reflects the contents of the new dirservers file instead
of the old one. Be sure to get the quotes and newlines and semicolons
right. (This step sucks. We plan to have it solved by the release of 0.0.9.)
<li>4b: Replace the dirservers file in your sandbox (in src/config/)
with the one from step 3.
<li>4c: edit configure.in, change the AM_INIT_AUTOMAKE(tor, 0.0.8)
line so that it specifies a version that is specific to you, such as
0.0.8-arma. This will help you keep from being confused later. Be sure
to update the RecommendedVersions lines to include this version.
<li>4d: run <tt>./autogen.sh</tt> (you'll need a new enough set of auto* tools),
then <tt>make dist</tt>.
</ul>
<li>5: Create a file called approved-routers in the DataDirectory <li>5: Create a file called approved-routers in the DataDirectory
of each directory server. Collect the 'fingerprint' lines from the of each directory server. Collect the 'fingerprint' lines from
DataDirectory of each server (including directory servers), and include each server (including directory servers), and include them (one per
them (one per line) in each approved-routers file. You can hup the tor line) in each approved-routers file. You can hup the tor process for
process for each directory server to reload the approved-routers file each directory server to reload the approved-routers file (so you don't
(so you don't have to restart the process). have to restart the process).
</ul> </ul>
<!--<h2>Other doc resources</h2> <!--<h2>Other doc resources</h2>