[or-cvs] and link some sandbox stuff to the svnsandbox instead

[arma at seul.org]

Update of /home2/or/cvsroot/website/en
In directory moria:/home/arma/work/onion/cvs/website/en

Modified Files:
	documentation.wml download.wml faq-abuse.wml volunteer.wml 
Log Message:
and link some sandbox stuff to the svnsandbox instead


Index: documentation.wml
===================================================================
RCS file: /home2/or/cvsroot/website/en/documentation.wml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -p -d -r1.15 -r1.16
--- documentation.wml	25 Jul 2006 19:03:06 -0000	1.15
+++ documentation.wml	31 Jul 2006 05:54:43 -0000	1.16
@@ -77,20 +77,20 @@ may be interesting for developers.</li>
 <ul>
 <li>The <b>design document</b> (published at Usenix Security 2004)
 gives our justifications and security analysis for the Tor design:
-<a href="<cvssandbox>tor/doc/design-paper/tor-design.pdf">PDF</a> and
-<a href="<cvssandbox>tor/doc/design-paper/tor-design.html">HTML</a>
+<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> and
+<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
 versions available.</li>
 <li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
 (still in draft form) details more recent experiences and directions:
-<a href="<cvssandbox>tor/doc/design-paper/challenges.pdf">PDF
+<a href="<svnsandbox>doc/design-paper/challenges.pdf">PDF
 version</a>.</li>
 <li>The <b>specifications</b> aim to give
 developers enough information to build a compatible version of Tor:
 <ul>
-<li><a href="<cvssandbox>tor/doc/tor-spec.txt">Main Tor specification</a></li>
-<li><a href="<cvssandbox>tor/doc/rend-spec.txt">Tor rendezvous specification</a></li>
-<li><a href="<cvssandbox>tor/doc/dir-spec.txt">Tor directory server specification</a></li>
-<li><a href="<cvssandbox>tor/doc/control-spec.txt">Tor UI control specification</a></li>
+<li><a href="<svnsandbox>doc/tor-spec.txt">Main Tor specification</a></li>
+<li><a href="<svnsandbox>doc/rend-spec.txt">Tor rendezvous specification</a></li>
+<li><a href="<svnsandbox>doc/dir-spec.txt">Tor directory server specification</a></li>
+<li><a href="<svnsandbox>doc/control-spec.txt">Tor UI control specification</a></li>
 </ul></li>
 <li>Look at the <a href="http://freehaven.net/~arma/wth1.pdf">slides
 (PDF)</a> and <a
@@ -132,7 +132,7 @@ of anonymous communication systems.</li>
 <h2><a class="anchor" href="#Developers">For Developers</a></h2>
   Browse the Tor <b>source repository</b>: (which may not necessarily work or even compile)
   <ul>
-    <li><a href="<cvssandbox>">Regularly updated CVS sandbox</a></li>
+    <li><a href="<svnsandbox>">Regularly updated SVN sandbox</a></li>
     <li><a href="http://tor-svn.freehaven.net/svn/tor/trunk">Browse the repository's source tree directly</a></li>
 # XXX FIXME - still points to cvs thing
     <li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/tor/?root=tor">ViewCVS</a></li>

Index: download.wml
===================================================================
RCS file: /home2/or/cvsroot/website/en/download.wml,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -p -d -r1.64 -r1.65
--- download.wml	30 Jul 2006 20:39:47 -0000	1.64
+++ download.wml	31 Jul 2006 05:54:43 -0000	1.65
@@ -9,7 +9,7 @@
 <hr />
 
 <p>Tor is distributed as <a href="http://www.fsf.org/">Free Software</a>
-under the <a href="<cvssandbox>tor/LICENSE">3-clause BSD license</a>.
+under the <a href="<svnsandbox>LICENSE">3-clause BSD license</a>.
 </p>
 
 <p>If you want Tor to become faster and more usable, please consider <a
@@ -243,10 +243,13 @@ even compile!</li>
 <h2>Stable releases</h2>
 
 <p>2006-07-30:
-Tor 0.1.1.23 fixes <a
-href="http://archives.seul.org/or/announce/Aug-2006/msg00000.html">more
-bugs in server reachability testing, a few more crash bugs, and an
-important client-side bug</a>. Clients and servers should both upgrade.
+Tor 0.1.1.23 fixes
+<!-- <a
+href="http://archives.seul.org/or/announce/Aug-2006/msg00000.html">
+-->
+more bugs in server reachability testing, a few more crash bugs, and an
+important client-side bug.
+Clients and servers should both upgrade.
 </p>
 
 <p>2006-07-05:
@@ -281,7 +284,7 @@ with Tor; and many scalability and perfo
 
 <hr />
 
-<p>You can read the <a href="<cvssandbox>tor/ChangeLog">ChangeLog</a> for more
+<p>You can read the <a href="<svnsandbox>ChangeLog">ChangeLog</a> for more
 details.</p>
 
   </div><!-- #main -->

Index: faq-abuse.wml
===================================================================
RCS file: /home2/or/cvsroot/website/en/faq-abuse.wml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -p -d -r1.7 -r1.8
--- faq-abuse.wml	26 May 2006 16:46:51 -0000	1.7
+++ faq-abuse.wml	31 Jul 2006 05:54:43 -0000	1.8
@@ -284,7 +284,7 @@ and you should keep in mind that exit po
 the overall list of nodes in the network). </p>
 
 <p>If you really want to do this, we provide a
-<a href="<cvssandbox>tor/contrib/exitlist">Python script to parse the Tor
+<a href="<svnsandbox>contrib/exitlist">Python script to parse the Tor
 directory</a>.
 </p>
 

Index: volunteer.wml
===================================================================
RCS file: /home2/or/cvsroot/website/en/volunteer.wml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -p -d -r1.23 -r1.24
--- volunteer.wml	10 May 2006 03:43:26 -0000	1.23
+++ volunteer.wml	31 Jul 2006 05:54:43 -0000	1.24
@@ -62,7 +62,7 @@ script that speaks via the <a href="<pag
 and does a setconf to change the bandwidth rate. Perhaps it would run out
 of cron, or perhaps it would sleep until appropriate times and then do
 its tweak (that's probably more portable). Can somebody write one for us
-and we'll put it into <a href="<cvssandbox>tor/contrib/">tor/contrib/</a>?
+and we'll put it into <a href="<svnsandbox>contrib/">contrib/</a>?
 This is a good entry for the <a href="<page gui/index>">Tor GUI
 competition</a>.</li>
 <li>Tor can <a
@@ -150,7 +150,7 @@ buffers. Maybe this should be modelled a
 design, where you have many smaller buffers that link to each other,
 rather than monolithic buffers?</li>
 <li>Implement reverse DNS requests inside Tor (already specified in
-Section 5.4 of <a href="<cvssandbox>tor/doc/tor-spec.txt">tor-spec.txt</a>).</li>
+Section 5.4 of <a href="<svnsandbox>doc/tor-spec.txt">tor-spec.txt</a>).</li>
 <li>Perform a security analysis of Tor with <a
 href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determine
 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 
 href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list
 of reasons why we haven't shifted to UDP transport</a>, but it would
 be great to see that list get shorter. We also have a proposed <a
-href="<cvssandbox>tor/doc/tor-spec-udp.txt">specification for Tor and
+href="<svnsandbox>doc/tor-spec-udp.txt">specification for Tor and
 UDP</a> &mash; please let us know what's wrong with it.</li>
 <li>We're not that far from having IPv6 support for destination addresses
 (at exit nodes). If you care strongly about IPv6, that's probably the