tor-webwml.git

@@ -173,7 +173,7 @@ in <tt>/var/lib/tor/fingerprint</tt> depending on your platform.

 <p>

 If you would like to learn more about Bridges from a technical standpoint,

 please read the <a

-href="https://svn.torproject.org/svn/tor/trunk/doc/spec/bridges-spec.txt">Tor

+href="<svnsandbox>doc/spec/bridges-spec.txt">Tor

 bridges specification</a>. If you're interested in running a private bridge or

 other specific uses, please do read the specification.

 </p>

@@ -163,7 +163,7 @@ ask us for specific permission.

 <p>

 However, if you want to redistribute the Tor software you must follow our

-<a href="https://svn.torproject.org/svn/trunk/LICENSE">LICENSE</a>.

+<a href="<svnsandbox>LICENSE">LICENSE</a>.

 Essentially this means that you need to include our LICENSE file along

 with whatever part of the Tor software you're distributing.

 </p>

@@ -44,7 +44,7 @@ like how to run a non-profit and generally helps keep everything moving

 forward.</dd>

 <dt>Karsten Loesing</dt><dd> Worked during the 2007 Google Summer of

 Code on <a

-href="https://www.torproject.org/svn/trunk/doc/spec/proposals/114-distributed-storage.txt">distributing

+href="<svnsandbox>doc/spec/proposals/114-distributed-storage.txt">distributing

 and securing the publishing and fetching of hidden service

 descriptors</a>.</dd>

 <dt>Nick Mathewson (Chief architect; Director)</dt><dd>One of the

@@ -58,7 +58,7 @@ the security, performance, and usability of Tor. Creator of the

 runs one of the directory authorities, runs the website and the wiki,

 and generally helps out a lot.</dd>

 <dt>Mike Perry</dt><dd>Author of <a

-href="https://www.torproject.org/svn/torflow/README">TorFlow</a>, a Tor

+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, a Tor

 controller that builds paths through the Tor network and

 measures various properties and behaviors. Working now on a <a

 href="<page torbutton/index>">much more comprehensive

@@ -227,7 +227,7 @@ href="http://www.globalvoicesonline.org/">Global Voices Online</a>.</dd>

 Tor is based on, so we didn't have to start from scratch.</dd>

 <dt>Johannes Renner</dt><dd> Worked during the 2007 Google Summer of

 Code on modifying <a

-href="https://www.torproject.org/svn/torflow/README">TorFlow</a>

+href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>

 to measure various properties of the Tor network; mentored by Mike

 Perry.</dd>

 <dt>Scott Squires</dt><dd>The original developer of <a

@@ -121,7 +121,7 @@ will listen.

 <br />

 In addition, these same statistics can be gathered about the traffic

 through a node. Events can be added to the <a

-href="https://www.torproject.org/svn/torctl/doc/howto.txt">Tor Control

+href="https://svn.torproject.org/svn/torctl/trunk/doc/howto.txt">Tor Control

 Protocol</a> to

 report if a circuit extend attempt through the node succeeds or fails, and

 passive statistics can be gathered on both bandwidth and reliability

@@ -348,7 +348,7 @@ href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal

 The <a href="http://p56soo2ibjkx23xo.onion/">exitlist software</a>

 is written by our fabulous anonymous

 contributer Tup. It's a DNS server written in Haskell that supports part of our <a

-href="https://www.torproject.org/svn/trunk/doc/contrib/torel-design.txt">exitlist

+href="<svnsandbox>doc/contrib/torel-design.txt">exitlist

 design document</a>. Currently, it is functional and it is used by

 check.torproject.org and other users. The issues that are outstanding

 are mostly aesthetic. This wonderful service could use a much better

@@ -777,7 +777,7 @@ throughput experiment</a>. We'll need to measure and tweak, and maybe

 overhaul if the results are good.</li>

 <li>Our censorship-resistance goals include preventing

 an attacker who's looking at Tor traffic on the wire from <a

-href="https://www.torproject.org/svn/trunk/doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing

+href="<svnsandbox>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing

 it from normal SSL traffic</a>. Obviously we can't achieve perfect

 steganography and still remain usable, but for a first step we'd like to

 block any attacks that can win by observing only a few packets. One of

@@ -49,15 +49,16 @@ to this version of Tor will be announced on the

 Let us know if you find bugs!

 </p>

-<p>You may find the <a href="../<svnsandbox>doc/control-spec.txt">Tor controller

-specification</a> or the <a href="/svn/torctl/doc/howto.txt">Tor

+<p>You may find the <a href="<svnsandbox>doc/control-spec.txt">Tor controller

+specification</a> or the <a

+href="https://svn.torproject.org/svn/torctl/trunk/doc/howto.txt">Tor

 controller howto</a> helpful.

 </p>

 <p>The Tor developers will also release test rigs (libraries) in both Java

 and Python that demonstrate Tor's controller protocol. Code submissions

 may be able to save a lot of time by using this code as a skeleton. You

-can check out the <a href="https://www.torproject.org/svn/torctl/">development

+can check out the <a href="https://svn.torproject.org/svn/torctl/trunk/">development

 versions of these libraries</a> now. Let us know if you find bugs!

 </p>

@@ -22,7 +22,7 @@ the directory. TorDNSEL actively tests through these nodes to provide a more

 accurate list.</p> 

 <p>The full background and rationale for TorDNSEL is described in the official

-<a href="https://www.torproject.org/svn/trunk/doc/contrib/torel-design.txt">design

+<a href="<svnsandbox>doc/contrib/torel-design.txt">design

 document</a>. The current service only supports the first query type mentioned

 in that document.</p>