Browse code

and link some sandbox stuff to the svnsandbox instead

Roger Dingledine authored on31/07/2006 07:54:43
Showing4 changed files
... ...
@@ -77,20 +77,20 @@ may be interesting for developers.</li>
77 77
 <ul>
78 78
 <li>The <b>design document</b> (published at Usenix Security 2004)
79 79
 gives our justifications and security analysis for the Tor design:
80
-<a href="<cvssandbox>tor/doc/design-paper/tor-design.pdf">PDF</a> and
81
-<a href="<cvssandbox>tor/doc/design-paper/tor-design.html">HTML</a>
80
+<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> and
81
+<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
82 82
 versions available.</li>
83 83
 <li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
84 84
 (still in draft form) details more recent experiences and directions:
85
-<a href="<cvssandbox>tor/doc/design-paper/challenges.pdf">PDF
85
+<a href="<svnsandbox>doc/design-paper/challenges.pdf">PDF
86 86
 version</a>.</li>
87 87
 <li>The <b>specifications</b> aim to give
88 88
 developers enough information to build a compatible version of Tor:
89 89
 <ul>
90
-<li><a href="<cvssandbox>tor/doc/tor-spec.txt">Main Tor specification</a></li>
91
-<li><a href="<cvssandbox>tor/doc/rend-spec.txt">Tor rendezvous specification</a></li>
92
-<li><a href="<cvssandbox>tor/doc/dir-spec.txt">Tor directory server specification</a></li>
93
-<li><a href="<cvssandbox>tor/doc/control-spec.txt">Tor UI control specification</a></li>
90
+<li><a href="<svnsandbox>doc/tor-spec.txt">Main Tor specification</a></li>
91
+<li><a href="<svnsandbox>doc/rend-spec.txt">Tor rendezvous specification</a></li>
92
+<li><a href="<svnsandbox>doc/dir-spec.txt">Tor directory server specification</a></li>
93
+<li><a href="<svnsandbox>doc/control-spec.txt">Tor UI control specification</a></li>
94 94
 </ul></li>
95 95
 <li>Look at the <a href="http://freehaven.net/~arma/wth1.pdf">slides
96 96
 (PDF)</a> and <a
... ...
@@ -132,7 +132,7 @@ of anonymous communication systems.</li>
132 132
 <h2><a class="anchor" href="#Developers">For Developers</a></h2>
133 133
   Browse the Tor <b>source repository</b>: (which may not necessarily work or even compile)
134 134
   <ul>
135
-    <li><a href="<cvssandbox>">Regularly updated CVS sandbox</a></li>
135
+    <li><a href="<svnsandbox>">Regularly updated SVN sandbox</a></li>
136 136
     <li><a href="http://tor-svn.freehaven.net/svn/tor/trunk">Browse the repository's source tree directly</a></li>
137 137
 # XXX FIXME - still points to cvs thing
138 138
     <li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/tor/?root=tor">ViewCVS</a></li>
... ...
@@ -9,7 +9,7 @@
9 9
 <hr />
10 10
 
11 11
 <p>Tor is distributed as <a href="http://www.fsf.org/">Free Software</a>
12
-under the <a href="<cvssandbox>tor/LICENSE">3-clause BSD license</a>.
12
+under the <a href="<svnsandbox>LICENSE">3-clause BSD license</a>.
13 13
 </p>
14 14
 
15 15
 <p>If you want Tor to become faster and more usable, please consider <a
... ...
@@ -243,10 +243,13 @@ even compile!</li>
243 243
 <h2>Stable releases</h2>
244 244
 
245 245
 <p>2006-07-30:
246
-Tor 0.1.1.23 fixes <a
247
-href="http://archives.seul.org/or/announce/Aug-2006/msg00000.html">more
248
-bugs in server reachability testing, a few more crash bugs, and an
249
-important client-side bug</a>. Clients and servers should both upgrade.
246
+Tor 0.1.1.23 fixes
247
+<!-- <a
248
+href="http://archives.seul.org/or/announce/Aug-2006/msg00000.html">
249
+-->
250
+more bugs in server reachability testing, a few more crash bugs, and an
251
+important client-side bug.
252
+Clients and servers should both upgrade.
250 253
 </p>
251 254
 
252 255
 <p>2006-07-05:
... ...
@@ -281,7 +284,7 @@ with Tor; and many scalability and performance improvements</a>.
281 284
 
282 285
 <hr />
283 286
 
284
-<p>You can read the <a href="<cvssandbox>tor/ChangeLog">ChangeLog</a> for more
287
+<p>You can read the <a href="<svnsandbox>ChangeLog">ChangeLog</a> for more
285 288
 details.</p>
286 289
 
287 290
   </div><!-- #main -->
... ...
@@ -284,7 +284,7 @@ and you should keep in mind that exit policies can change (as well as
284 284
 the overall list of nodes in the network). </p>
285 285
 
286 286
 <p>If you really want to do this, we provide a
287
-<a href="<cvssandbox>tor/contrib/exitlist">Python script to parse the Tor
287
+<a href="<svnsandbox>contrib/exitlist">Python script to parse the Tor
288 288
 directory</a>.
289 289
 </p>
290 290
 
... ...
@@ -62,7 +62,7 @@ script that speaks via the <a href="<page gui/index>">Tor Controller Interface</
62 62
 and does a setconf to change the bandwidth rate. Perhaps it would run out
63 63
 of cron, or perhaps it would sleep until appropriate times and then do
64 64
 its tweak (that's probably more portable). Can somebody write one for us
65
-and we'll put it into <a href="<cvssandbox>tor/contrib/">tor/contrib/</a>?
65
+and we'll put it into <a href="<svnsandbox>contrib/">contrib/</a>?
66 66
 This is a good entry for the <a href="<page gui/index>">Tor GUI
67 67
 competition</a>.</li>
68 68
 <li>Tor can <a
... ...
@@ -150,7 +150,7 @@ buffers. Maybe this should be modelled after the Linux kernel buffer
150 150
 design, where you have many smaller buffers that link to each other,
151 151
 rather than monolithic buffers?</li>
152 152
 <li>Implement reverse DNS requests inside Tor (already specified in
153
-Section 5.4 of <a href="<cvssandbox>tor/doc/tor-spec.txt">tor-spec.txt</a>).</li>
153
+Section 5.4 of <a href="<svnsandbox>doc/tor-spec.txt">tor-spec.txt</a>).</li>
154 154
 <li>Perform a security analysis of Tor with <a
155 155
 href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determine
156 156
 if there are good fuzzing libraries out there for what we want. Win fame by
... ...
@@ -167,7 +167,7 @@ it means we can only reasonably support TCP streams. We have a <a
167 167
 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list
168 168
 of reasons why we haven't shifted to UDP transport</a>, but it would
169 169
 be great to see that list get shorter. We also have a proposed <a
170
-href="<cvssandbox>tor/doc/tor-spec-udp.txt">specification for Tor and
170
+href="<svnsandbox>doc/tor-spec-udp.txt">specification for Tor and
171 171
 UDP</a> &mash; please let us know what's wrong with it.</li>
172 172
 <li>We're not that far from having IPv6 support for destination addresses
173 173
 (at exit nodes). If you care strongly about IPv6, that's probably the