omnibus update of s/svnsandbox/gitweb links in all languages. still need to fix thandy links and githax which doesn't exist in gitweb yet. (f85239e9e)

omnibus update of s/svnsandbox/gitweb links in all languages. still need to fix thandy links and githax which doesn't exist in gitweb yet.

Parent 3f13af99c

Andrew Lewman commited on 2010-01-17 05:44:57
Zeige 97 geänderte Dateien mit 507 Einfügungen und 506 Löschungen.

cs/bridges.wml 8e53e1dcf..68a612be1
de/bridges.wml 7f9d0cca2..5e8d1b9cf
de/documentation.wml 51efb5724..2c2ad0c8b
de/download-unix.wml a688993dc..62f472c40
de/download.wml 065e9a00f..4afb885dd
de/hidden-services.wml 605885ca0..34f33e565
de/people.wml 85ac96376..221ac3b35
de/translation.wml c65dc842f..69afd4e2a
de/volunteer.wml fc8086985..421486f87
en/bridges.wml 7bbf21803..013b48d50
en/documentation.wml d1b9b0b2e..83db3a778
en/download-unix.wml 67679388a..1866c27b7
en/download.wml f82ae828a..0159cb844
en/faq.wml 0a652e572..b4fde036f
en/hidden-services.wml 049895bf5..58e846642
en/people.wml 3937acbee..f3a865f16
en/volunteer.wml 432cdce37..4e8cedd8c
es/bridges.wml 0da12baae..493b508aa
es/documentation.wml b01383888..bf8a085b7
es/download-unix.wml 45c3216ea..a295c65c8
es/download.wml c750823b4..4feab2233
es/faq-abuse.wml 3f47860b3..3392aa118
es/volunteer.wml e566b9767..60288b890
fdownload.wml 23bd439bb..4f36a03a4
fi/documentation.wml 20963841d..7b0cac846
fi/download-unix.wml c024bcae2..ba1aefb6c
fi/download.wml 50e1667f2..b1ebac425
fi/volunteer.wml 0a247ce81..06399a572
fr/bridges.wml 8cf0ffa77..6902cdb85
fr/documentation.wml 70da1b985..338c2bc93
fr/download-unix.wml 0f98bd1b1..fe45e351e
fr/download.wml fe7c3a3d7..8c9e84589
fr/faq-abuse.wml 99cc6fd00..05ba96719
fr/hidden-services.wml 1c553387d..afaade5bb
fr/volunteer.wml 7971f7bad..29f649c53
gui/en/technotes.wml 95d60aa1b..9f9fbe9ef
include/links.wmi 2037ba2f7..255c1c9da
it/bridges.wml da4cfd526..e4a6f7242
it/documentation.wml 27d3ffa7b..b8496d849
it/download-unix.wml 8b4502f13..c0570bb94
it/download.wml f9cea47fb..215842b87
it/faq.wml 2b2cc6224..8f2a43a3c
it/hidden-services.wml 103151d75..d4f2f6d8e
it/people.wml cee4de23c..7efdfd6c5
it/volunteer.wml 82b59cd91..2d5e13eea
jbridges.wml a5bdae804..3823a88a4
jdocumentation.wml 5700fe4a4..ec4dbdd31
jdownload-osx.wml 06cde4e98..14a917ab6
jdownload-unix.wml 1aa080bbc..c541248b9
jdownload-windows.wml 60b68324f..e157092f4
jdownload.wml ac14a3903..54614941f
jpeople.wml 9d41d08a8..b2e0b5231
jvolunteer.wml c66797301..adf8da759
ko/download.wml 9a869a53f..4fa356baa
nl/documentation.wml 38c4f6d5f..bf3edfc4e
nl/download-osx.wml e2ec24ee6..a286fa39a
nl/download-unix.wml 1e38d7a5f..430b302db
nl/download-windows.wml 36c4e110b..c89850c04
nl/download.wml 13a6e5122..775e8909d
nl/volunteer.wml 17c4e3717..bb52c9b3b
no/download-osx.wml 1c94caaf1..c9a5229a8
no/download-unix.wml 987423c52..a322e8383
no/download-windows.wml d5915824a..34857528b
no/download.wml 7da60fb20..6e6005c8e
pl/bridges.wml 52ae2eaf3..c377536ff
pl/documentation.wml 9db77b69c..5c6749b56
pl/download-unix.wml 47c99b943..ad4afe453
pl/download.wml ecafe81e8..0eefc4136
pl/faq.wml 3a3f36f7d..d179b011a
pl/hidden-services.wml cd2bb60dc..89120b2b1
pl/people.wml 72a16a30d..2c06579d4
pl/volunteer.wml 2c62e1ce3..9eb8389f1
pt/bridges.wml bfd00d866..450ff8148
pt/documentation.wml 24c1abbb3..7ceaf5c54
pt/download-unix.wml f66b36302..8f2db8fce
pt/download.wml 939ea2e49..45ef45f17
ru/documentation.wml c79dc7213..914f8d96f
ru/download-unix.wml 06982f5c0..4ab76d23b
ru/download.wml ca2a371b9..2c002f7c3
ru/people.wml 6f08b2560..a947a3ad9
se/documentation.wml d7de0d5f2..7d12bf172
se/download-osx.wml 42823df48..c2f40f969
se/download-unix.wml d129076bd..822d22292
se/download-windows.wml 7d29bf746..dbc638536
se/download.wml f70ebbbb9..1087fafcd
se/faq-abuse.wml b19f0fd64..99c488e9c
tordnsel/de/index.wml bcfba21ce..822133948
tordnsel/en/index.wml 6e9b5cee3..9a7551810
tordnsel/it/index.wml d5fb9c987..be70c77e8
tordnsel/pl/index.wml 63bc4408a..4bccc8317
tr/download.wml 04f35de27..89b29a9ff
zh-cn/bridges.wml 08a2a679a..7948cbf04
zh-cn/documentation.wml 4a09f55fe..58b6e42ff
zh-cn/download-unix.wml 2e68321e3..50d809a12
zh-cn/download.wml c9e40c85c..c8372fbde
zh-cn/people.wml 2a8cdee5d..74aad35cf
zh-cn/volunteer.wml 238bfa435..f47a50c73

cs/bridges.wml

Zeige Datei @ f85239e9e

@@ -163,7 +163,7 @@ v <tt>ORPort</tt> a "otisk" neboli fingerprint Vašeho serveru. Fingerprint by m
 
 <p>
 Chcete-li se dozvědět víc o přemosťovacích serverech (Bridge-serverech) z technického hlediska, prosím čtěte<a
-href="<svnsandbox>doc/spec/bridges-spec.txt">Tor bridges specification</a>. Máte-li zájem o zprovoznění 
+href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges specification</a>. Máte-li zájem o zprovoznění 
 privátního přemosťovacího serveru nebo jiných specifických použitích, prosím čtěte specifikaci.
 </p>
 

de/bridges.wml

Zeige Datei @ f85239e9e

@@ -157,7 +157,7 @@ oben</a> an. Den Fingerprint findest du in den Logdateien oder in <tt>
 /var/lib/tor/fingerprint</tt>, in Abhängigkeit von deiner Plattform. </p>
 
 <p>Falls du mehr über Brücken-Server aus einer technischen Perspektive lernen
-willst, lies bitte <a href="<svnsandbox>doc/spec/bridges-spec.txt">die
+willst, lies bitte <a href="<gitblob>doc/spec/bridges-spec.txt">die
 Spezifikation zu den Brücken-Servern</a>. Wenn du eine unveröffentlichte
 Brücke betreiben willst, schau bitte in die Spezifikation. </p>
 

de/documentation.wml

Zeige Datei @ f85239e9e

@@ -71,7 +71,7 @@ Spezifikationen im Stile von RFCs, die exakt beschreiben, wie Tor aufgebaut
 ist.</li>
 
 <li>Es gibt eine skelettartige <a
-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Liste von Einträgen,
+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Liste von Einträgen,
 die wir in Zukunft anpacken wollen</a>. Viele der Einträge müssen noch
 ausgearbeitet werden, bevor sie für andere Sinn ergeben. Du kannst jedoch eine
 generelle Idee bekommen, was als nächstes erledigt werden muss.</li>
@@ -86,7 +86,7 @@ Rogers Vortrag <q>blocking-resistance and circumvention</q> vom 23C3 im Dezember
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">Video</a>, <a
 href="http://freehaven.net/~arma/slides-23c3.pdf">Folien</a>, <a
 href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">Kurzdarstellung</a>,
-<a href="<svnsandbox>doc/design-paper/blocking.html">Designvorschlag</a>) und
+<a href="<gitblob>doc/design-paper/blocking.html">Designvorschlag</a>) und
 Rogers Vortrag <q>Current events in 2007</q> vom 24C3 aus dem Dezember 2007 (<a
 href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">Video</a>,
 <a href="http://freehaven.net/~arma/slides-24c3.pdf">Folien</a>, <a
@@ -105,11 +105,11 @@ href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>
 ein.</li>
 
 <li>Lerne über den <a
-href="<svnsandbox>doc/spec/proposals/001-process.txt">Prozess der Proposals, um
+href="<gitblob>doc/spec/proposals/001-process.txt">Prozess der Proposals, um
 das Design von Tor zu ändern</a> und schaue dir auch die <a
-href="<svnsandbox>doc/spec/proposals/">existierenden Proposals</a> an.</li>
+href="<gittree>doc/spec/proposals/">existierenden Proposals</a> an.</li>
 
-<li>Unsere <a href="<svnsandbox>doc/TODO">TODO-Datei für Entwickler</a> startet
+<li>Unsere <a href="<gitblob>doc/TODO">TODO-Datei für Entwickler</a> startet
 mit einer Zeitplanung für externe Versprechen &mdash; Dinge, für die <a
 href="<page sponsors>">unsere Sponsoren</a> bezahlt haben. Es listet auch
 weitere Themen und Aufgaben auf, die wir gern bearbeiten würden.</li>
@@ -153,13 +153,13 @@ ist das die Liste für dich.</li> </ul>
   <ul>
     <li>Das <b>Designdokument</b> (zur Usenix Security 2004 veröffentlicht)
       gibt dir unsere Einstellungen und Sicherheitsanalyse zum Tor-Design:
-      <a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF-Entwurf  (engl.)</a> und
-      <a href="<svnsandbox>doc/design-paper/tor-design.html">HTML-Entwurf (engl.)</a>
+      <a href="<gitblob>doc/design-paper/tor-design.pdf">PDF-Entwurf  (engl.)</a> und
+      <a href="<gitblob>doc/design-paper/tor-design.html">HTML-Entwurf (engl.)</a>
       stehen zur Verfügung.</li>
     <li>Das darauf folgende Papier mit dem Titel <q>challenges in low-latency
       anonymity</q> (noch im Entwurf) hat mehr Details über die letzten
       Erfahrungen und Richtungen: <a
-      href="<svnsandbox>doc/design-paper/challenges.pdf">PDF version
+      href="<gitblob>doc/design-paper/challenges.pdf">PDF version
       (engl.)</a>.</li>
       <li>Unsere Veröffentlichung bei der WEIS 2006 &mdash; <b>Anonymity Loves
       Company: Usability and the Network Effect</b> &mdash; erklärt, warum
@@ -169,7 +169,7 @@ ist das die Liste für dich.</li> </ul>
       <li>Unser vorläufiges Design, um Firewalls den Zugriff auf das
       Tornetzwerk zu erschweren, ist in <b>design of a blocking-resistant
       anonymity system</b> (<a
-      href="<svnsandbox>doc/design-paper/blocking.pdf">PDF-Entwurf</a>)
+      href="<gitblob>doc/design-paper/blocking.pdf">PDF-Entwurf</a>)
       beschrieben. Du kannst auch einen Blick auf die <a
       href="http://freehaven.net/~arma/slides-23c3.pdf">Vortragsunterlagen</a>
       oder das <a
@@ -180,25 +180,25 @@ ist das die Liste für dich.</li> </ul>
     <li>Die <b>Spezifikation</b> zielt darauf ab, Entwicklern genügend Information zu
       geben, um eine zu Tor kompatible Version zu schaffen:
       <ul>
-        <li><a href="<svnsandbox>doc/spec/tor-spec.txt">Main Tor
+        <li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor
 	specification (engl.)</a></li>
-    <li><a href="<svnsandbox>doc/spec/dir-spec.txt">Tor
+    <li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
     version 3 directory server specification</a> (und die ältere <a
-    href="<svnsandbox>doc/spec/dir-spec-v1.txt">Version 1</a> und <a
-    href="<svnsandbox>doc/spec/dir-spec-v2.txt">Version 2</a>
+    href="<gitblob>doc/spec/dir-spec-v1.txt">Version 1</a> und <a
+    href="<gitblob>doc/spec/dir-spec-v2.txt">Version 2</a>
     Verzeichnisspezifikationen)</li>
-    <li><a href="<svnsandbox>doc/spec/control-spec.txt">Tor control protocol
+    <li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
     specification</a></li>
-    <li><a href="<svnsandbox>doc/spec/rend-spec.txt">Tor rendezvous specification (engl.)</a></li>
-	<li><a href="<svnsandbox>doc/spec/path-spec.txt">Tor path selection
+    <li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous specification (engl.)</a></li>
+	<li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
 	specification</a></li>
-	<li><a href="<svnsandbox>doc/spec/address-spec.txt">Special
+	<li><a href="<gitblob>doc/spec/address-spec.txt">Special
 	hostnames in Tor</a></li>
-    <li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS
+    <li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS
     Unterstützung und Erweiterungen</a></li>
-	<li><a href="<svnsandbox>doc/spec/version-spec.txt">How Tor version
+	<li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version
     numbers work</a></li>
-    <li><a href="<svnsandbox>doc/spec/proposals/">Entwürfe neuer Spezifikationen
+    <li><a href="<gitblob>doc/spec/proposals/">Entwürfe neuer Spezifikationen
     und geplante Änderungen</a>.</li>
       </ul></li>
     <li>Wirf einen Blick auf die <a href="http://freehaven.net/~arma/wth1.pdf">Folien</a>
@@ -218,11 +218,11 @@ ist das die Liste für dich.</li> </ul>
     ein.</li>
 
     <li>Lerne mehr über <a
-    href="<svnsandbox>doc/spec/proposals/001-process.txt">den Prozess zur
+    href="<gitblob>doc/spec/proposals/001-process.txt">den Prozess zur
     Veränderung unseres Designs</a> und schaue durch die <a
-    href="<svnsandbox>doc/spec/proposals/">existierende Proposals</a>.</li>
+    href="<gittree>doc/spec/proposals/">existierende Proposals</a>.</li>
 
-    <li>Unsere <a href="<svnsandbox>doc/TODO">TODO-Datei</a> startet mit einer
+    <li>Unsere <a href="<gitblob>doc/TODO">TODO-Datei</a> startet mit einer
     Zeitleiste für externe Versprechungen &mdash; Dinge für die unsere <a
     href="<page sponsors>">Sponsoren</a> Geld gegeben haben. Es listet auch
     weitere Themen auf.</li>
@@ -261,7 +261,7 @@ ist das die Liste für dich.</li> </ul>
 <h2><a class="anchor" href="#Developers">Für Entwickler</a></h2>
   Durchsuche das Tor <b>Quellen Repository</b>:
   <ul>
-    <li><a href="<svnsandbox>">Durchsuche den Quellcode direkt.</a></li>
+    <li><a href="<gittree>">Durchsuche den Quellcode direkt.</a></li>
     <li>Nur Lesezugriff:
       <ul>
         <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>        

de/download-unix.wml

Zeige Datei @ f85239e9e

@@ -242,7 +242,7 @@ href="https://bugs.torproject.org/"> Fehler zu berichten</a>.</p> </div>
 <div class="underline"></div>
 <div class="nb">
 <p>Tor wird als <a href="http://www.fsf.org/">Freie Software</a> unter der
-<a href="<svnsandbox>LICENSE">3-clause-BSD-Lizenz</a> verteilt. Die Pakete
+<a href="<gitblob>LICENSE">3-clause-BSD-Lizenz</a> verteilt. Die Pakete
 schließen des Weiteren <a href="<page vidalia/index>">Vidalia</a>
 und <a href="http://www.privoxy.org/">Privoxy</a> ein. Diese werden unter der
 GNU GPL verteilt.</p>
@@ -347,9 +347,9 @@ spiegeln</a>.</p>
 <a id="Stable"></a>
 <a id="Testing"></a>
 <p>Eine Liste der Änderungen in jeder stabilen Tor-Version findest du in den <a
-href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Eine Liste der Änderungen in
+href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Eine Liste der Änderungen in
 der stabilen und der Entwicklerversion ist im <a
-href="<svnsandbox>ChangeLog">ChangeLog</a>.</p>
+href="<gitblob>ChangeLog">ChangeLog</a>.</p>
 </p>
 </div>
 </div><!-- #main -->

de/download.wml

Zeige Datei @ f85239e9e

@@ -149,7 +149,7 @@ Zuverlässigkeitsprobleme haben. Bitte hilf uns und <a
 href="https://bugs.torproject.org/">melde Fehler</a>. </p> </div>
 
 <div class="underline"></div> <div class="nb"> <p> Tor ist <a
-href="http://www.fsf.org/">Freie Software</a> unter der <a href="<svnsandbox>
+href="http://www.fsf.org/">Freie Software</a> unter der <a href="<gitblob>
 LICENSE">3-clause BSD Lizenz</a>. Die Bundles enthalten auch <a href="<page
 vidalia/index>">Vidalia</a> und <a href="http://www.privoxy.org/">Privoxy</a>,
 welche Hilfsprogramme unter der GNU GPL sind. </p> <p> There is no fee for
@@ -258,9 +258,9 @@ href="<page mirrors>">Liste von Spiegel-Seiten der Torhomepage</a>.
 
 <a id="ChangeLog"></a> <a id="Stable"></a> <a id="Testing"></a> <p> Wenn du
 wissen willst, was sich in den Stable-Versionen geändert hat, schau in die <a
-href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Für eine Liste der
+href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Für eine Liste der
 Änderungen in der Stable und in der Unstable Version schau in das <a
-href="<svnsandbox>ChangeLog">ChangeLog</a>. </p> </div> <div class="underline">
+href="<gitblob>ChangeLog">ChangeLog</a>. </p> </div> <div class="underline">
 </div>
 
 <a id="Dev"></a>

de/hidden-services.wml

Zeige Datei @ f85239e9e

@@ -140,10 +140,10 @@ Client und drei vom versteckten Dienst gewählt.
 <p>Es gibt detailliertere Beschreibungen zu dem Protokoll als diese
 Seite. Schaue dir hierzu die
 <a
-href="<svnsandbox>doc/design-paper/tor-design.pdf">Designbeschreibung
+href="<gitblob>doc/design-paper/tor-design.pdf">Designbeschreibung
 von Tor</a> und die
 <a
-href="<svnsandbox>doc/spec/rend-spec.txt">Rendezvous-Spezifikation</a>
+href="<gitblob>doc/spec/rend-spec.txt">Rendezvous-Spezifikation</a>
 an. Dort findest du genauere Informationen.
 </p>
 

de/people.wml

Zeige Datei @ f85239e9e

@@ -55,7 +55,7 @@ Linux Distributionen.</dd>
 
 <dt>Karsten Loesing (Entwickler)</dt>
 <dd>arbeitete an
-  der <a href="<svnsandbox>doc/spec/proposals/114-distributed-storage.txt">Verteilung
+  der <a href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">Verteilung
   und Absicherung der Veröffentlichung der Deskriptoren der
   versteckten Services</a>. Derzeit arbeitet er an der <a href="<page
   projects/hidserv>">Beschleunigung und stärkeren Vertrauenswürdigkeit der

de/translation.wml

Zeige Datei @ f85239e9e

@@ -34,14 +34,14 @@ Fehler, die du in den bestehenden Seiten findest.
 
 <ol>
 <li>Schaue im <a
-  href="<svnsandbox>website/en/">SVN-Verzeichnis der
+  href="<gitblob>website/en/">SVN-Verzeichnis der
   Webseite</a> nach den .wml-Dateien. Die wichtigsten sind dabei
   <code>index.wml</code>, <code>overview.wml</code>,
   <code>download*.wml</code>, <code>documentation.wml</code>,
   <code>foot.wmi</code> und <code>navigation.wmi</code>.
   Wir würden uns sehr freuen, wenn du diese
   oder auch mehr übersetzen könntest:  Übersetzungen von den ".wml" Dateien in
-  <a href="<svnsandbox>website/docs/en/"><svnsandbox>website/docs/en/</a>
+  <a href="<gitblob>website/docs/en/"><gitblob>website/docs/en/</a>
   wären als nächstes nütlich. Du kannst einen Blick auf das <a
   href="<svnwebsite>/de/">deutsche Archiv</a>
   werfen, um Beispiele für die gewünschten Formate zu erhalten.</li>

de/volunteer.wml

Zeige Datei @ f85239e9e

@@ -60,7 +60,7 @@
     herbeizuführen. Natürlich würde es durch Cron ausgeführt oder es
     schläft eine bestimmte Zeit und macht dann die Änderungen. Kann
     das jemand für uns schreiben und wir packen das dann
-    nach <a href="<svnsandbox>contrib/">contrib</a>? Das wäre
+    nach <a href="<gittree>contrib/">contrib</a>? Das wäre
   eine gute Möglichkeit für den <a href="<page gui/index>">Tor GUI
   Wettbewerb</a>.</li>
   <li>Wenn wir gerade bei Geolocation sind, wäre es schön, wenn
@@ -226,20 +226,20 @@ Skill Level: <i>High</i>
 Likely Mentors: <i>Nick, Roger, Steven</i>
 <br />
 The Tor 0.2.0.x series makes <a
-href="<svnsandbox>doc/design-paper/blocking.html">significant
+href="<gitblob>doc/design-paper/blocking.html">significant
 improvements</a> in resisting national and organizational censorship.
 But Tor still needs better mechanisms for some parts of its
 anti-censorship design.  For example, current Tors can only listen on a
 single address/port combination at a time.  There's
-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
 proposal to address this limitation</a> and allow clients to connect
 to any given Tor on multiple addresses and ports, but it needs more
 work.  Another anti-censorship project (far more difficult) is to try
 to make Tor more scanning-resistant.  Right now, an adversary can identify
-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
 just by trying to connect to them, following the Tor protocol, and
 seeing if they respond.  To solve this, bridges could
-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
 webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
 and not act like bridges until the user provides a bridge-specific key.
 <br />
@@ -416,7 +416,7 @@ project</a>, and make it run on <a
 href="http://code.google.com/android/">Android</a>. The first step
 would be to port the existing code and execute it in an Android
 environment. Next, the code should be updated to support the newer Tor
-protocol versions like the <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
+protocol versions like the <a href="<gitblob>doc/spec/dir-spec.txt">v3
 directory protocol</a>. Further, support for requesting or even
 providing Tor hidden services would be neat, but not required.
 <br />
@@ -653,9 +653,9 @@ and <a href="https://svn.torproject.org/svn/weather/trunk/TODO">TODO</a>.
 <b>Bring up new ideas!</b>
 <br />
 Don't like any of these? Look at the <a
-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
 roadmap</a> for more ideas.
-Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a>
+Some of the <a href="<gittree>doc/spec/proposals/">current proposals</a>
 might also be short on developers.
 </li>
 
@@ -695,7 +695,7 @@ currently does not exist and would need to be developed as well.
 Vidalia currently doesn't play nicely on Debian and Ubuntu with the
 default Tor packages. The current Tor packages automatically start Tor
 as a daemon running as the debian-tor user and (sensibly) do not have a
-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
 in the default torrc. Consequently, Vidalia will try
 to start its own Tor process since it could not connect to the existing
 Tor, and Vidalia's Tor process will then exit with an error message
@@ -790,7 +790,7 @@ to interact minimally with Tor to test their code.
 <br />
 If you want to make the project more exciting
 and involve more design and coding, take a look at <a
-href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
+href="<gitblob>doc/spec/proposals/131-verify-tor-usage.txt">proposal
 131-verify-tor-usage.txt</a>.
 </li>
 -->
@@ -803,7 +803,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="<svnsandbox>doc/contrib/torel-design.txt">exitlist
+href="<gitblob>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
@@ -1030,7 +1030,7 @@ it means we can only reasonably support TCP streams. We have a <a
 href="https://wiki.torproject.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="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
 for Tor and
 UDP</a> &mdash; please let us know what's wrong with it.</li>
 
@@ -1143,7 +1143,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="<svnsandbox>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
+href="<gitblob>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

en/bridges.wml

Zeige Datei @ f85239e9e

@@ -190,7 +190,7 @@ depending on your platform).
 <p>
 If you would like to learn more about our bridge
 design from a technical standpoint, please read the <a
-href="<svnsandbox>doc/spec/bridges-spec.txt">Tor bridges
+href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges
 specification</a>. If you're interested in running an unpublished bridge
 or other non-standard uses, please do read the specification.
 </p>

en/documentation.wml

Zeige Datei @ f85239e9e

@@ -97,7 +97,7 @@ how Tor is built.
 
 <li>
 There's a skeletal <a
-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">list of items
+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">list of items
 we'd like to tackle in the future</a>. Alas, many of those items need
 to be fleshed out more before they'll make sense to people who aren't
 Tor developers, but you can still get a general sense of what issues
@@ -114,7 +114,7 @@ and circumvention" talk from 23C3 in December 2006 (<a
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
 <a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
 <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
-<a href="<svnsandbox>doc/design-paper/blocking.html">design paper</a>),
+<a href="<gitblob>doc/design-paper/blocking.html">design paper</a>),
 and Roger's "Current events in 2007" talk from 24C3 in December
 2007 (<a
 href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
@@ -137,13 +137,13 @@ script collection.
 
 <li>
 Learn about the <a
-href="<svnsandbox>doc/spec/proposals/001-process.txt">Tor
+href="<gitblob>doc/spec/proposals/001-process.txt">Tor
 proposal process for changing our design</a>, and look over the <a
-href="<svnsandbox>doc/spec/proposals/">existing proposals</a>.
+href="<gittree>doc/spec/proposals/">existing proposals</a>.
 </li>
 
 <li>
-Our <a href="<svnsandbox>doc/TODO">developer TODO file</a> starts with a
+Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a
 timeline for external promises &mdash; things <a href="<page sponsors>">our
 sponsors</a> have paid to see done. It also lists many other tasks
 and topics we'd like to tackle next.
@@ -185,12 +185,12 @@ commits</a> 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="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> and
-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> and
+<a href="<gitblob>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="<svnsandbox>doc/design-paper/challenges.pdf">PDF
+<a href="<gitblob>doc/design-paper/challenges.pdf">PDF
 draft</a>.</li>
 <li>Our paper at WEIS 2006 &mdash; <b>Anonymity Loves Company:
 Usability and the Network Effect</b> &mdash; explains why usability in
@@ -199,31 +199,31 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
 <li>Our preliminary design to make it harder for large firewalls to
 prevent access to the Tor network is described in
 <b>design of a blocking-resistant anonymity system</b>:
-<a href="<svnsandbox>doc/design-paper/blocking.pdf">PDF draft</a> and
-<a href="<svnsandbox>doc/design-paper/blocking.html">HTML draft</a>.
+<a href="<gitblob>doc/design-paper/blocking.pdf">PDF draft</a> and
+<a href="<gitblob>doc/design-paper/blocking.html">HTML draft</a>.
 Want to <a href="<page volunteer>#Coding">help us build it</a>?</li>
 <li>The <b>specifications</b> aim to give
 developers enough information to build a compatible version of Tor:
 <ul>
-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Main Tor specification</a></li>
-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Tor
+<li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor specification</a></li>
+<li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
 version 3 directory server specification</a> (and older <a
-href="<svnsandbox>doc/spec/dir-spec-v1.txt">version 1</a> and <a
-href="<svnsandbox>doc/spec/dir-spec-v2.txt">version 2</a> directory
+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> and <a
+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> directory
 specifications)</li>
-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Tor control protocol
+<li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Tor rendezvous
+<li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Tor path selection
+<li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Special hostnames in
+<li><a href="<gitblob>doc/spec/address-spec.txt">Special hostnames in
 Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS support
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support
 and extensions</a></li>
-<li><a href="<svnsandbox>doc/spec/version-spec.txt">How Tor version numbers
+<li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version numbers
 work</a></li>
-<li><a href="<svnsandbox>doc/spec/proposals/">In-progress drafts of
+<li><a href="<gitblob>doc/spec/proposals/">In-progress drafts of
 new specifications and proposed changes</a></li>
 </ul></li>
 
@@ -258,7 +258,7 @@ of anonymous communication systems.</li>
 <h2><a class="anchor" href="#Developers">For Developers</a></h2>
   Browse the Tor <b>source repository</b>:
   <ul>
-    <li><a href="<svnsandbox>">Browse the repository's source tree directly</a></li>
+    <li><a href="<gittree>">Browse the repository's source tree directly</a></li>
     <li>Git and SVN access:
       <ul>
         <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>

en/download-unix.wml

Zeige Datei @ f85239e9e

@@ -233,7 +233,7 @@ serious reliability and security bugs in these downloads.  Please be prepared to
 <div class="nb">
 <p>
 Tor is distributed as <a href="http://www.fsf.org/">Free Software</a>
-under the <a href="<svnsandbox>LICENSE">3-clause BSD license</a>. The
+under the <a href="<gitblob>LICENSE">3-clause BSD license</a>. The
 bundles also include <a href="<page vidalia/index>">Vidalia</a>
 and <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>, which are supporting
 applications distributed under the GNU GPL.
@@ -368,9 +368,9 @@ href="<page mirrors>">list of sites mirroring the Tor site</a>.
 <a id="Testing"></a>
 <p>
 For a list of what has changed in each stable Tor release, see the
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. For a list of
+<a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. For a list of
 changes in both stable and development versions, see the
-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
+<a href="<gitblob>ChangeLog">ChangeLog</a>.
 </p>
 </div>
 </div><!-- #main -->

en/download.wml

Zeige Datei @ f85239e9e

@@ -150,7 +150,7 @@ serious reliability and security bugs in these downloads.  Please be prepared to
 <div class="nb">
 <p>
 Tor is distributed as <a href="http://www.fsf.org/">Free Software</a>
-under the <a href="<svnsandbox>LICENSE">3-clause BSD license</a>. The
+under the <a href="<gitblob>LICENSE">3-clause BSD license</a>. The
 bundles also include <a href="<page vidalia/index>">Vidalia</a>
 and <a href="http://www.privoxy.org/">Privoxy</a>, which are supporting
 applications distributed under the GNU GPL.
@@ -287,9 +287,9 @@ href="<page mirrors>">list of sites mirroring the Tor site</a>.
 <a id="Testing"></a>
 <p>
 For a list of what has changed in each stable Tor release, see the
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. For a list of
+<a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. For a list of
 changes in both stable and development versions, see the
-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
+<a href="<gitblob>ChangeLog">ChangeLog</a>.
 </p>
 </div>
 <div class="underline"></div>

en/faq.wml

Zeige Datei @ f85239e9e

@@ -251,7 +251,7 @@ ask us for specific permission.
 
 <p>
 However, if you want to redistribute the Tor software you must follow our
-<a href="<svnsandbox>LICENSE">LICENSE</a>.
+<a href="<gitblob>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>
@@ -590,7 +590,7 @@ Windows?</a></h3>
 
 <p>
 Try following the steps at <a
-href="<svnsandbox>doc/tor-win32-mingw-creation.txt"><svnsandbox>doc/tor-win32-mingw-creation.txt</a>.
+href="<gitblob>doc/tor-win32-mingw-creation.txt"><gitblob>doc/tor-win32-mingw-creation.txt</a>.
 </p>
 
 <p>
@@ -935,7 +935,7 @@ won't work.
 <b>Authentication</b>:
 Every Tor relay has a public decryption key called the "onion key".
 When the Tor client establishes circuits, at each step it <a
-href="<svnsandbox>doc/design-paper/tor-design.html#subsec:circuits">demands
+href="<gitblob>doc/design-paper/tor-design.html#subsec:circuits">demands
 that the Tor relay prove knowledge of its onion key</a>. That way
 the first node in the path can't just spoof the rest of the path.
 Each relay rotates its onion key once a week.
@@ -947,7 +947,7 @@ How do clients know what the relays are, and how do they know that they
 have the right keys for them? Each relay has a long-term public signing
 key called the "identity key". Each directory authority additionally has a
 "directory signing key". The directory authorities <a
-href="<svnsandbox>doc/spec/dir-spec.txt">provide a signed list</a>
+href="<gitblob>doc/spec/dir-spec.txt">provide a signed list</a>
 of all the known relays, and in that list are a set of certificates from
 each relay (self-signed by their identity key) specifying their keys,
 locations, exit policies, and so on. So unless the adversary can control
@@ -1034,7 +1034,7 @@ stop requiring that all Tor relays be able to connect to all Tor
 relays) and of the directory (how to stop requiring that all Tor
 users know about all Tor relays). Changes like this can have large
 impact on potential and actual anonymity. See Section 5 of the <a
-href="<svnsandbox>doc/design-paper/challenges.pdf">Challenges</a> paper
+href="<gitblob>doc/design-paper/challenges.pdf">Challenges</a> paper
 for details. Again, UDP transport would help here.
 </p>
 

en/hidden-services.wml

Zeige Datei @ f85239e9e

@@ -147,9 +147,9 @@ service.
 <p>
 There are more detailed descriptions about the hidden service protocol than
 this one. See the
-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">Tor design paper</a>
+<a href="<gitblob>doc/design-paper/tor-design.pdf">Tor design paper</a>
 for an in-depth design description and the
-<a href="<svnsandbox>doc/spec/rend-spec.txt">rendezvous specification</a>
+<a href="<gitblob>doc/spec/rend-spec.txt">rendezvous specification</a>
 for the message formats.
 </p>
 

en/people.wml

Zeige Datei @ f85239e9e

@@ -82,7 +82,7 @@ management, and general support.  General package hacker for Windows, OS
 X, and various linux distributions.</dd>
 <dt>Karsten Loesing (Developer)</dt><dd> Worked during the 2007 Google
 Summer of Code on <a
-href="<svnsandbox>doc/spec/proposals/114-distributed-storage.txt">distributing
+href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">distributing
 and securing the publishing and fetching of hidden service
 descriptors</a>. Currently working on <a href="<page
 projects/hidserv>">making hidden services faster and more

en/volunteer.wml

Zeige Datei @ f85239e9e

@@ -187,20 +187,20 @@ Skill Level: <i>High</i>
 Likely Mentors: <i>Nick, Roger, Steven</i>
 <br />
 The Tor 0.2.1.x series makes <a
-href="<svnsandbox>doc/design-paper/blocking.html">significant
+href="<gitblob>doc/design-paper/blocking.html">significant
 improvements</a> in resisting national and organizational censorship.
 But Tor still needs better mechanisms for some parts of its
 anti-censorship design.  For example, current Tors can only listen on a
 single address/port combination at a time.  There's
-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
 proposal to address this limitation</a> and allow clients to connect
 to any given Tor on multiple addresses and ports, but it needs more
 work.  Another anti-censorship project (far more difficult) is to try
 to make Tor more scanning-resistant.  Right now, an adversary can identify
-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
 just by trying to connect to them, following the Tor protocol, and
 seeing if they respond.  To solve this, bridges could
-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
 webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
 and not act like bridges until the user provides a bridge-specific key.
 <br />
@@ -560,9 +560,9 @@ and <a href="https://svn.torproject.org/svn/weather/trunk/TODO">TODO</a>.
 <b>Bring up new ideas!</b>
 <br />
 Don't like any of these? Look at the <a
-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
 roadmap</a> for more ideas.
-Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a>
+Some of the <a href="<gittree>doc/spec/proposals/">current proposals</a>
 might also be short on developers.
 </li>
 
@@ -572,7 +572,7 @@ might also be short on developers.
 Vidalia currently doesn't play nicely on Debian and Ubuntu with the
 default Tor packages. The current Tor packages automatically start Tor
 as a daemon running as the debian-tor user and (sensibly) do not have a
-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
 in the default torrc. Consequently, Vidalia will try
 to start its own Tor process since it could not connect to the existing
 Tor, and Vidalia's Tor process will then exit with an error message
@@ -737,7 +737,7 @@ it means we can only reasonably support TCP streams. We have a <a
 href="https://wiki.torproject.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="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
 for Tor and
 UDP</a> &mdash; please let us know what's wrong with it.</li>
 
@@ -850,7 +850,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="<svnsandbox>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
+href="<gitblob>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

es/bridges.wml

Zeige Datei @ f85239e9e

@@ -180,7 +180,7 @@ Tor o en <tt>/var/lib/tor/fingerprint</tt> dependiendo de su plataforma).
 <p>
 Si desea aprender más acerca de nuestro dise&ntilde;o
 de puentes desde un punto de vista técnico, lea las <a
-href="<svnsandbox>doc/spec/bridges-spec.txt">Especificaciones de puentes
+href="<gitblob>doc/spec/bridges-spec.txt">Especificaciones de puentes
 de Tor</a>. Si está interesado en la ejecución de un puente no publicado
 o en otros usos no estándar, lea la especificación.
 </p>

es/documentation.wml

Zeige Datei @ f85239e9e

@@ -83,12 +83,12 @@ es únicamente para desarrolladores y tiene muy poco tráfico.</li>
 <li>El <b>documento de dise&ntilde;o</b> (publicado en Usenix Security 2004)
 da nuestras justificaciones y análisis de seguridad para el dise&ntilde;o de Tor:
 versiones disponibles
-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> y
-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> y
+<a href="<gitblob>doc/design-paper/tor-design.html">HTML</a>
 .</li>
 <li>Nuestro documento de reafirmación en <b>desafíos en el anonimato de baja latencia</b>
 (todavía en forma de borrador) detalla experiencias y direcciones mas recientes:
-<a href="<svnsandbox>doc/design-paper/challenges.pdf">versión PDF</a>.</li>
+<a href="<gitblob>doc/design-paper/challenges.pdf">versión PDF</a>.</li>
 <li>Nuestro artículo en WEIS 2006 &mdash; <b>Anonymity Loves Company:
 Usability and the Network Effect (Al anonimato le encanta la compañía:
 Usabilidad y el efecto en red)</b> &mdash; explica porqué la usabilidad
@@ -97,8 +97,8 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
 <li>Nuestro diseño preliminar para hacer más difícil que cortafuegos grandes
 eviten el acceso a la red Tor se describe en 
 <b>el diseño de un sistema de anonimato resistente al bloqueo</b>:
-<a href="<svnsandbox>doc/design-paper/blocking.pdf">borrador PDF</a> y
-<a href="<svnsandbox>doc/design-paper/blocking.html">borrador HTML</a>.
+<a href="<gitblob>doc/design-paper/blocking.pdf">borrador PDF</a> y
+<a href="<gitblob>doc/design-paper/blocking.html">borrador HTML</a>.
 También puede ver <a
 href="http://freehaven.net/~arma/slides-23c3.pdf">transparencias</a> y <a
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">vídeo</a>
@@ -110,21 +110,21 @@ de Roger. ¿Quiere <a href="<page volunteer>#Coding">ayudarnos a construirla</a>
 desarrolladores la suficiente información para construir una versión compatible de Tor:
 <ul>
 
-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Especificación principal de Tor</a></li>
+<li><a href="<gitblob>doc/spec/tor-spec.txt">Especificación principal de Tor</a></li>
 
-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">
+<li><a href="<gitblob>doc/spec/dir-spec.txt">
 Especificación para el servidor de directorio Tor versión 3</a>
 (y las especificaciones de directorio más antiguas <a
-href="<svnsandbox>doc/spec/dir-spec-v1.txt">versión 1</a> y <a
-href="<svnsandbox>doc/spec/dir-spec-v2.txt">versión 2</a>)</li>
-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Especificación del protocolo de control de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Especificación de punto de encuentro de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Especificación para el servidor de directorio Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Especificación de selección de camino de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Nombres de host especiales de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Soporte SOCKS de Tor y extensiones</a></li>
-<li><a href="<svnsandbox>doc/spec/version-spec.txt">Cómo funcionan los números de versión de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/proposals/">Borradores en progreso de nuevas especificaciones y cambios propuestos</a></li>
+href="<gitblob>doc/spec/dir-spec-v1.txt">versión 1</a> y <a
+href="<gitblob>doc/spec/dir-spec-v2.txt">versión 2</a>)</li>
+<li><a href="<gitblob>doc/spec/control-spec.txt">Especificación del protocolo de control de Tor</a></li>
+<li><a href="<gitblob>doc/spec/rend-spec.txt">Especificación de punto de encuentro de Tor</a></li>
+<li><a href="<gitblob>doc/spec/dir-spec.txt">Especificación para el servidor de directorio Tor</a></li>
+<li><a href="<gitblob>doc/spec/path-spec.txt">Especificación de selección de camino de Tor</a></li>
+<li><a href="<gitblob>doc/spec/address-spec.txt">Nombres de host especiales de Tor</a></li>
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Soporte SOCKS de Tor y extensiones</a></li>
+<li><a href="<gitblob>doc/spec/version-spec.txt">Cómo funcionan los números de versión de Tor</a></li>
+<li><a href="<gittree>doc/spec/proposals/">Borradores en progreso de nuevas especificaciones y cambios propuestos</a></li>
 </ul></li>
 <li>Mira las <a href="http://freehaven.net/~arma/wth1.pdf">transparencias
 (PDF)</a> y <a
@@ -165,7 +165,7 @@ sistemas anónimos de comunicación.</li>
 <h2><a class="anchor" href="#Developers">Para desarrolladores</a></h2>
 Hojea el <b>repositorio de fuentes</b> de Tor: (que podría no funcionar ni tan siquiera compilar)
 <ul>
-<li><a href="<svnsandbox>">SVN sandbox actualizado periódicamente </a></li>
+<li><a href="<gittree>">SVN sandbox actualizado periódicamente </a></li>
 <li><a href="https://tor-svn.freehaven.net/svn/tor/trunk">Hojee el repositorio directamente</a></li>
 <li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/?root=Tor">VistaCVS</a></li>
 <li>acceso anónimo a <a href="http://subversion.tigris.org/">subversion</a>:</li>

es/download-unix.wml

Zeige Datei @ f85239e9e

@@ -223,7 +223,7 @@ incluyendo snapshots de desarrollo</a></li>
 
 <ul>
 <li>Tor se distribuye como <a href="http://www.fsf.org/">Software Libre</a>
-bajo la <a href="<svnsandbox>LICENSE">licencia BSD de tres cláusulas</a>.
+bajo la <a href="<gitblob>LICENSE">licencia BSD de tres cláusulas</a>.
 </li>
 <li>Si quieres que Tor sea más rápido y usable, por favor considera <a
 href="<page donate>">hacer una donacion al proyecto Tor</a>.

es/download.wml

Zeige Datei @ f85239e9e

@@ -122,7 +122,7 @@
 </p>
 <p>
 Tor se distribuye como <a href="http://www.fsf.org/">Software Libre</a>
-bajo la <a href="<svnsandbox>LICENSE">licencia BSD de tres cláusulas</a>.
+bajo la <a href="<gitblob>LICENSE">licencia BSD de tres cláusulas</a>.
 Los paquetes también incluyen <a href="<page vidalia/index>">Vidalia</a>
 y <a href="http://www.privoxy.org/">Privoxy</a>, que son aplicaciones de soporte
 distribuídas bajo la GNU GPL.
@@ -360,9 +360,9 @@ href="<page mirrors>">lista de sitios mirror del sitio Tor</a>.
 <a id="Testing"></a>
 <p>
 Para una lista de qué ha cambiado en cada versión estable de Tor, 
-véa las <a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Para una lista de
+véa las <a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Para una lista de
 cambios tanto de la versión estable como la de desarrollo, vea el
-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
+<a href="<gitblob>ChangeLog">ChangeLog</a>.
 </p>
 
 </div><!-- #main -->

es/faq-abuse.wml

Zeige Datei @ f85239e9e

@@ -295,7 +295,7 @@ en mente que las políticas de salida pueden cambiar (y también la
 lista de nodos completa de la red). </p>
 
 <p>Si realmente quiere hacer esto, damos un
-<a href="<svnsandbox>contrib/exitlist">script Python para leer el directorio 
+<a href="<gitblob>contrib/exitlist">script Python para leer el directorio 
 Tor</a>. Note que este script no le dará una lista perfecta de direcciones
 IP que puedan conectarse a usted usando Tor, ya que algunos servidores Tor
 pueden salir desde otras direcciones aparte de la que publican.

es/volunteer.wml

Zeige Datei @ f85239e9e

@@ -130,7 +130,7 @@ El interfaz DNSBL recibirá probablemente cientos de peticiones por minuto,
 así que se necesitan algoritmos inteligentes. Puntos de bonus si hace testing
 activo a cada nodo de salida para averigura de qué direcciones IP está 
 realmente saliendo.
-<a href="<svnsandbox>doc/contrib/torel-design.txt">Lea más aquí</a>.</li>
+<a href="<gitblob>doc/contrib/torel-design.txt">Lea más aquí</a>.</li>
 <li>Algunas veces los repetidores Tor se cuelgan, o a los ordenadores en los
 que están se les cae la red, u otros accidentes pasan. Algunos operadores Tor
 han expresado un interes en inscribirse en un servidio "de notificación"
@@ -225,13 +225,13 @@ permitir flujos TCP. Tenemos una <a
 href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">lista
 de razones por las que no hemos cambiado a transporte UDP</a>, pero sería excelente
 ver que esa lista se hace maś corta. También tenemos una propuesta de <a
-href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">especificación
+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">especificación
 para Tor y UDP</a> &mdash; por favor díganos qué problemas tiene.</li>
 <li>No estamos tan lejos de tener soporte IPv6 para las direcciones
 de destino (en los nodos de salida). Si le importa mucho IPv6, ése es
 probablemente el primer sitio para empezar.</li>
 <li>¿No le gusta ninguna de éstas? Mire el <a
-href="<svnsandbox>doc/design-paper/roadmap-2007.pdf">plan de desarrollo Tor</a> 
+href="<gitblob>doc/design-paper/roadmap-2007.pdf">plan de desarrollo Tor</a> 
 para más ideas.</li>
 <li>¿No ve su idea aquí? ¡Probablemente la necesitemos de todas formas! 
 Contáctenos y averígüelo.</li>

fdownload.wml

Zeige Datei @ f85239e9e

...	...	@@ -93,7 +93,7 @@
93	93	</p>
94	94
95	95	<p>
96		-Tor به عنوان يک <a href="http://www.fsf.org/">نرم افزار رايگان</a> تحت <a href="<svnsandbox>LICENSE">ليسانس 3-clause BSD </a> منتشر شده است. بسته نرم افزاری همچنين حاوی <a href="<page vidalia/index>">Vidalia</a> و <a href="http://www.privoxy.org/">Privoxy</a> است که برنامه های پشتيبان منتشر شده تحت GNU GPL می باشند.
	96	+Tor به عنوان يک <a href="http://www.fsf.org/">نرم افزار رايگان</a> تحت <a href="<gitblob>LICENSE">ليسانس 3-clause BSD </a> منتشر شده است. بسته نرم افزاری همچنين حاوی <a href="<page vidalia/index>">Vidalia</a> و <a href="http://www.privoxy.org/">Privoxy</a> است که برنامه های پشتيبان منتشر شده تحت GNU GPL می باشند.
97	97
98	98	</p>
99	99
...	...	@@ -297,7 +297,7 @@ Tor مبدأ ترافيک شما را بی نام می کند، و همه چيز
297	297
298	298	<a id="ChangeLog"></a> <a id="Stable"></a> <a id="Testing"></a>
299	299	<p>
300		-در خصوص ليستی از تغييرات ايجاد شده در هر نسخه پايدار Tor به <a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a> مراجعه کنيد. در خصوص ليستی از تغييرات ايجاد شده در نسخه های پايدار و پيشرفته، به <a href="<svnsandbox>ChangeLog">ChangeLog</a> مراجعه کنيد.
	300	+در خصوص ليستی از تغييرات ايجاد شده در هر نسخه پايدار Tor به <a href="<gitblob>ReleaseNotes">ReleaseNotes</a> مراجعه کنيد. در خصوص ليستی از تغييرات ايجاد شده در نسخه های پايدار و پيشرفته، به <a href="<gitblob>ChangeLog">ChangeLog</a> مراجعه کنيد.
301	301
302	302	</p>
303	303

fi/documentation.wml

Zeige Datei @ f85239e9e

@@ -119,7 +119,7 @@ how Tor is built.
 
 <li>
 There's a skeletal <a
-href="<svnsandbox>doc/design-paper/roadmap-future.pdf">list of items
+href="<gitblob>doc/design-paper/roadmap-future.pdf">list of items
 we'd like to tackle in the future</a>. Alas, many of those items need
 to be fleshed out more before they'll make sense to people who aren't
 Tor developers, but you can still get a general sense of what issues
@@ -136,7 +136,7 @@ and circumvention" talk from 23C3 in December 2006 (<a
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
 <a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
 <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
-<a href="<svnsandbox>doc/design-paper/blocking.html">design paper</a>),
+<a href="<gitblob>doc/design-paper/blocking.html">design paper</a>),
 and Roger's "Current events in 2007" talk from 24C3 in December
 2007 (<a
 href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
@@ -149,13 +149,13 @@ href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">video</a>,
 
 <li>
 Learn about the <a
-href="<svnsandbox>doc/spec/proposals/001-process.txt">Tor
+href="<gitblob>doc/spec/proposals/001-process.txt">Tor
 proposal process for changing our design</a>, and look over the <a
-href="<svnsandbox>doc/spec/proposals/">existing proposals</a>.
+href="<gittree>doc/spec/proposals/">existing proposals</a>.
 </li>
 
 <li>
-Our <a href="<svnsandbox>doc/TODO">developer TODO file</a> starts with a
+Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a
 timeline for external promises &mdash; things <a href="<page sponsors>">our
 sponsors</a> have paid to see done. It also lists many other tasks
 and topics we'd like to tackle next.
@@ -175,12 +175,12 @@ is where the less complex discussion happens.
 <ul>
 <li>The <b>design document</b> (published at Usenix Security 2004)
 gives our justifications and security analysis for the Tor design:
-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> and
-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> and
+<a href="<gitblob>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="<svnsandbox>doc/design-paper/challenges.pdf">PDF
+<a href="<gitblob>doc/design-paper/challenges.pdf">PDF
 draft</a>.</li>
 <li>Our paper at WEIS 2006 &mdash; <b>Anonymity Loves Company:
 Usability and the Network Effect</b> &mdash; explains why usability in
@@ -189,32 +189,32 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
 <li>Our preliminary design to make it harder for large firewalls to
 prevent access to the Tor network is described in
 <b>design of a blocking-resistant anonymity system</b>:
-<a href="<svnsandbox>doc/design-paper/blocking.pdf">PDF draft</a> and
-<a href="<svnsandbox>doc/design-paper/blocking.html">HTML draft</a>.
+<a href="<gitblob>doc/design-paper/blocking.pdf">PDF draft</a> and
+<a href="<gitblob>doc/design-paper/blocking.html">HTML draft</a>.
 Want to <a href="<page volunteer>#Coding">help us build it</a>?</li>
 <li>The <b>specifications</b> aim to give
 developers enough information to build a compatible version of Tor:
 <ul>
-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Main Tor
+<li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Tor
+<li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
 version 3 directory server specification</a> (and older <a
-href="<svnsandbox>doc/spec/dir-spec-v1.txt">version 1</a> and <a
-href="<svnsandbox>doc/spec/dir-spec-v2.txt">version 2</a> directory
+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> and <a
+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> directory
 specifications)</li>
-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Tor control protocol
+<li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Tor rendezvous
+<li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Tor path selection
+<li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
 specification</a></li>
-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Special hostnames in
+<li><a href="<gitblob>doc/spec/address-spec.txt">Special hostnames in
 Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS support
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support
 and extensions</a></li>
-<li><a href="<svnsandbox>doc/spec/version-spec.txt">How Tor version numbers
+<li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version numbers
 work</a></li>
-<li><a href="<svnsandbox>doc/spec/proposals/">In-progress drafts of
+<li><a href="<gittree>doc/spec/proposals/">In-progress drafts of
 new specifications and proposed changes</a></li>
 </ul></li>
 
@@ -250,7 +250,7 @@ of anonymous communication systems.</li>
 <h2><a class="anchor" href="#Developers">Kehittäjille</a></h2>
   Browse the Tor <b>source repository</b>: (which may not necessarily work or even compile)
   <ul>
-    <li><a href="<svnsandbox>">Regularly updated SVN sandbox</a></li>
+    <li><a href="<gittree>">Regularly updated SVN sandbox</a></li>
     <li><a href="https://svn.torproject.org/svn/tor/trunk">Browse the repository's source tree directly</a></li>
     <li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/tor/?root=Tor">ViewCVS</a></li>
     <li>anonymous <a href="http://subversion.tigris.org/">subversion</a> access:

fi/download-unix.wml

Zeige Datei @ f85239e9e

@@ -207,7 +207,7 @@ Mitä <a href="#packagediff">eroja on vakaalla &amp; epävakaalla</a>?
 </p>
 
 <p>Toria levitetään <a href="http://www.fsf.org/">vapaana ohjelmistona</a>
-<a href="<svnsandbox>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.</li> The
+<a href="<gitblob>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.</li> The
 bundles also include <a href="<page vidalia/index>">Vidalia</a>
 and <a href="http://www.privoxy.org/">Privoxy</a>, which are supporting
 applications distributed under the GNU GPL.
@@ -342,8 +342,8 @@ href="<page mirrors>">on lista palvelimista, jotka ovat kopioita Tor-sivustosta<
 <a id="Testing"></a>
 <p>
 Vakaan Tor-julkaisun muutoksia voi lukea englanninkielellä tiedostosta
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä  tiedostosta 
-<a href="<svnsandbox>ChangeLog">ChangeLog / Muutosloki</a>.
+<a href="<gitblob>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä  tiedostosta 
+<a href="<gitblob>ChangeLog">ChangeLog / Muutosloki</a>.
 </p>
 
 </div><!-- #main -->

fi/download.wml

Zeige Datei @ f85239e9e

@@ -121,7 +121,7 @@ Mitä <a href="#packagediff">eroja on vakaalla &amp; epävakaalla</a>?
 </p>
 
 <p>Toria levitetään <a href="http://www.fsf.org/">vapaana ohjelmistona</a>
-<a href="<svnsandbox>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.The
+<a href="<gitblob>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.The
 bundles also include <a href="<page vidalia/index>">Vidalia</a>
 and <a href="http://www.privoxy.org/">Privoxy</a>, which are supporting
 applications distributed under the GNU GPL.
@@ -359,8 +359,8 @@ href="<page mirrors>">on lista palvelimista, jotka ovat kopioita Tor-sivustosta<
 <a id="Testing"></a>
 <p>
 Vakaan Tor-julkaisun muutoksia voi lukea englanninkielellä tiedostosta
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä  tiedostosta 
-<a href="<svnsandbox>ChangeLog">ChangeLog / Muutosloki</a>.
+<a href="<gitblob>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä  tiedostosta 
+<a href="<gitblob>ChangeLog">ChangeLog / Muutosloki</a>.
 </p>
 
 </div><!-- #main -->

fi/volunteer.wml

Zeige Datei @ f85239e9e

@@ -105,7 +105,7 @@ with how useful it would be to the overall Tor project
 clue you should start with (skill level), and which of our <a href="<page
 people>#Core">core developers</a> would be good mentors. There are plenty
 of other good ideas to work on too &mdash; see for example the <a
-href="<svnsandbox>doc/spec/proposals/">current proposals</a> list, or
+href="<gittree>doc/spec/proposals/">current proposals</a> list, or
 just make up your own ideas.
 </p>
 
@@ -125,7 +125,7 @@ Likely Mentors: <i>Mike</i>
 Applications as of 1 Apr 00:00 UTC: <i>5</i>
 <br />
 The Tor exit node scanner 'SoaT', part of the <a
-href="<svnsandbox>torflow/">Torflow project</a>, makes connections out
+href="<gittree>torflow/">Torflow project</a>, makes connections out
 of each Tor exit node and compares the content it gets back with what it
 "should" get back. The goal is to notice misconfigured, broken, and even
 malicious exit relays. Alas, the code is
@@ -301,7 +301,7 @@ Applications as of 1 Apr 00:00 UTC: <i>1</i>
 Vidalia currently doesn't play nicely on Debian and Ubuntu with the
 default Tor packages. The current Tor packages automatically start Tor
 as a daemon running as the debian-tor user and (sensibly) do not have a
-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
 in the default torrc. Consequently, Vidalia will try
 to start its own Tor process since it could not connect to the existing
 Tor, and Vidalia's Tor process will then exit with an error message
@@ -351,20 +351,20 @@ Skill Level: <i>High</i>
 Likely Mentors: <i>Nick</i>
 <br />
 The Tor 0.2.0.x series makes <a
-href="<svnsandbox>doc/design-paper/blocking.html">significant
+href="<gitblob>doc/design-paper/blocking.html">significant
 improvements</a> in resisting national and organizational censorship.
 But Tor still needs better mechanisms for some parts of its
 anti-censorship design.  For example, current Tors can only listen on a
 single address/port combination at a time.  There's
-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
 proposal to address this limitation</a> and allow clients to connect
 to any given Tor on multiple addresses and ports, but it needs more
 work.  Another anti-censorship project (far more difficult) is to try
 to make Tor more scanning-resistant.  Right now, an adversary can identify
-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
 just by trying to connect to them, following the Tor protocol, and
 seeing if they respond.  To solve this, bridges could
-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
 webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
 and not act like bridges until the user provides a bridge-specific key.
 <br />
@@ -522,7 +522,7 @@ to interact minimally with Tor to test their code.
 <br />
 If you want to make the project more exciting
 and involve more design and coding, take a look at <a
-href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
+href="<gitblob>doc/spec/proposals/131-verify-tor-usage.txt">proposal
 131-verify-tor-usage.txt</a>.
 </li>
 
@@ -727,7 +727,7 @@ project</a>, and make it run on <a
 href="http://code.google.com/android/">Android</a>. The first step
 would be to port the existing code and execute it in an Android
 environment. Next, the code should be updated to support the newer Tor
-protocol versions like the <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
+protocol versions like the <a href="<gitblob>doc/spec/dir-spec.txt">v3
 directory protocol</a>. Further, support for requesting or even
 providing Tor hidden services would be neat, but not required.
 <br />
@@ -959,7 +959,7 @@ the core of the Blossom effort.
 <b>Bring up new ideas!</b>
 <br />
 Don't like any of these? Look at the <a
-href="<svnsandbox>doc/design-paper/roadmap-future.pdf">Tor development
+href="<gitblob>doc/design-paper/roadmap-future.pdf">Tor development
 roadmap</a> for more ideas.
 </li>
 
@@ -1007,7 +1007,7 @@ it means we can only reasonably support TCP streams. We have a <a
 href="https://wiki.torproject.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="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
 for Tor and
 UDP</a> &mdash; please let us know what's wrong with it.</li>
 <li>We're not that far from having IPv6 support for destination addresses

fr/bridges.wml

Zeige Datei @ f85239e9e

@@ -148,7 +148,7 @@ fonction de votre plateforme).
 <p>
 Si vous voulez en savoir plus sur le design des passerelles d'un point de vue plus technique,
 voyez les <a
-href="<svnsandbox>doc/spec/bridges-spec.txt">Spécifications 
+href="<gitblob>doc/spec/bridges-spec.txt">Spécifications 
 de passerelles Tor</a>. Si vous avez envie de faire tourner une passerelle non publié ou d'avoir 
 d'autres utilisations non standards, voyez les spécifications.
 </p>

fr/documentation.wml

Zeige Datei @ f85239e9e

@@ -96,7 +96,7 @@ comment Tor est conçu.
 
 <li>
 Il y a une liste squelettique d'<a
-href="<svnsandbox>doc/design-paper/2008-12-19-roadmap-full.pdf">éléments que nous
+href="<gitblob>doc/design-paper/2008-12-19-roadmap-full.pdf">éléments que nous
 souhaiterions aborder dans le futur</a>. Hélas, beaucoup de ces points devraient
 être approfondis avant qu'ils puissent avoir un sens pour des nons
 dévelopeurs Tor, mais vous pouvez tout de même avoir une idée des questions à
@@ -113,7 +113,7 @@ et contournement » d'une présentation de Roger au 23C3 en décembre 2006 (<a
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">vidéo</a>,
 <a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
 <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">résumé</a>,
-<a href="<svnsandbox>doc/design-paper/blocking.html">document d'architecture</a>),
+<a href="<gitblob>doc/design-paper/blocking.html">document d'architecture</a>),
 et la présentation des « Évènements courant en 2007 » de Roger au 24C3 en décembre
 2007 (<a
 href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">vidéo</a>,
@@ -135,13 +135,13 @@ href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>.
   	 
 <li>
 Étudiez les <a
-href="<svnsandbox>doc/spec/proposals/001-process.txt">propositions
+href="<gitblob>doc/spec/proposals/001-process.txt">propositions
 pour modifier notre conception</a>, et regardez les <a
-href="<svnsandbox>doc/spec/proposals/">propositions existantes</a>.
+href="<gittree>doc/spec/proposals/">propositions existantes</a>.
 </li>
 
 <li>
-Notre <a href="<svnsandbox>doc/TODO">fichier de développeur TODO</a> commence par
+Notre <a href="<gitblob>doc/TODO">fichier de développeur TODO</a> commence par
 un calendrier de promesses &mdash; choses que <a href="<page sponsors>">nos
 sponsors</a> ont payé pour voir achevées. Elle liste également d'autres tâches 
 et thèmes que nous aimerions attaquer prochainement.
@@ -191,24 +191,24 @@ De l'utilisation et de son effet sur le réseau</b> &mdash;
 explique en quoi l'utilisation des systèmes anonymes est importante pour leur sécurité <a
 href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
 <li>Notre architecture préliminaire visant à rendre plus difficile le blocage des firewalls pour l'accès au réseau Tor est décrit sur <b>Architecture d'un système résistant au blocage</b> :
-<a href="<svnsandbox>doc/design-paper/blocking.pdf">ébauche PDF</a> et
-<a href="<svnsandbox>doc/design-paper/blocking.html">l'ébauche HTML</a>. 
+<a href="<gitblob>doc/design-paper/blocking.pdf">ébauche PDF</a> et
+<a href="<gitblob>doc/design-paper/blocking.html">l'ébauche HTML</a>. 
 Vous êtes intéressé pour nous <a href="<page volunteer>#Coding">aider à le coder</a> ?</li>
 <li>Les <b>spécifications</b> visent à donner aux développeurs suffisamment d'informations
 pour créer une version compatible de Tor :
 <ul>
-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Spécifications principales de Tor </a></li>
-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Version 3 des spécifications de serveur d'annuaire</a> (anciennement les <a
-href="<svnsandbox>doc/spec/dir-spec-v1.txt">version 1</a> et <a
-href="<svnsandbox>doc/spec/dir-spec-v2.txt">version 2</a> des spécifications d'annuaire)</li>
-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Spécification de l'interface graphique
+<li><a href="<gitblob>doc/spec/tor-spec.txt">Spécifications principales de Tor </a></li>
+<li><a href="<gitblob>doc/spec/dir-spec.txt">Version 3 des spécifications de serveur d'annuaire</a> (anciennement les <a
+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> et <a
+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> des spécifications d'annuaire)</li>
+<li><a href="<gitblob>doc/spec/control-spec.txt">Spécification de l'interface graphique
 de contrôle de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Spécification du Tor « rendezvous »</a></li>
-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Spécification de la sélection de chemin de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Noms spéciaux de machines dans Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS support and extensions</a></li>
-<li><a href="<svnsandbox>doc/spec/version-spec.txt">Comment sont numérotés les versions de Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/proposals/">Travail en cours sur les nouvelles spécifications et les changements proposés</a></li>
+<li><a href="<gitblob>doc/spec/rend-spec.txt">Spécification du Tor « rendezvous »</a></li>
+<li><a href="<gitblob>doc/spec/path-spec.txt">Spécification de la sélection de chemin de Tor</a></li>
+<li><a href="<gitblob>doc/spec/address-spec.txt">Noms spéciaux de machines dans Tor</a></li>
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support and extensions</a></li>
+<li><a href="<gitblob>doc/spec/version-spec.txt">Comment sont numérotés les versions de Tor</a></li>
+<li><a href="<gittree>doc/spec/proposals/">Travail en cours sur les nouvelles spécifications et les changements proposés</a></li>
 </ul></li>
 </ul>
 
@@ -238,7 +238,7 @@ communications anonymes.</li>
 <h2><a class="anchor" href="#Developers">Pour les développeurs</a></h2>
 Parcourez le <b>dépôt SVN</b> :
 <ul>
-  <li><a href="<svnsandbox>">Parcourir le répertoire du dépôt SVN directement</a></li>
+  <li><a href="<gittree>">Parcourir le répertoire du dépôt SVN directement</a></li>
   <li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/?root=Tor">Voir le CVS</a></li>
   <li>Accès Lecture-Seule :
   	       <ul>

fr/download-unix.wml

Zeige Datei @ f85239e9e

@@ -226,7 +226,7 @@ Quel est la <a href="#packagediff">différence entre Stable &amp; Non-stable</a>
   	 
 <p>
 Tor est distribué en tant que <a href="http://www.fsf.org/">Logiciel Libre</a>
-sous la <a href="<svnsandbox>LICENSE">licence 3-clause BSD</a>. Le
+sous la <a href="<gitblob>LICENSE">licence 3-clause BSD</a>. Le
 « tout en un » apporte également <a href="<page vidalia/index>">Vidalia</a>
 et <a href="http://www.privoxy.org/">Privoxy</a>, qui sont des applications
 contributives distribuées sous licence GNU GPL.
@@ -362,9 +362,9 @@ href="<page mirrors>">liste de sites miroir du site Tor</a>.
 <a id="Testing"></a>
 <p>
 Pour une liste de ce qui a changé dans chaque version stable de Tor, voyez les
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes (ndt : notes de version)</a>. Pour une liste des
+<a href="<gitblob>ReleaseNotes">ReleaseNotes (ndt : notes de version)</a>. Pour une liste des
 changements à la fois dans les versions stable et développement, voyez le
-<a href="<svnsandbox>ChangeLog">ChangeLog (ntd : trace de changement)</a>.
+<a href="<gitblob>ChangeLog">ChangeLog (ntd : trace de changement)</a>.
 </p>
 
   </div><!-- #main -->

fr/download.wml

Zeige Datei @ f85239e9e

@@ -152,7 +152,7 @@ href="https://bugs.torproject.org/">rapporter des bugs</a>.
 <div class="nb">
 <p>
 Tor est distribué en tant que <a href="http://www.fsf.org/">Logiciel Libre</a>
-sous la <a href="<svnsandbox>LICENSE">licence 3-clause BSD</a>. Le
+sous la <a href="<gitblob>LICENSE">licence 3-clause BSD</a>. Le
 « tout en un » inclu également <a href="<page vidalia/index>">Vidalia</a>
 et <a href="http://www.privoxy.org/">Privoxy</a>, qui sont des applications
 complémentaires distribuées sous licence GNU GPL.
@@ -274,9 +274,9 @@ href="<page mirrors>">liste de sites miroir du site Tor</a>.
 
 <p>
 Pour une liste de ce qui a changé dans chaque version stable de Tor, voyez le
-<a href="<svnsandbox>ReleaseNotes">fichier ReleaseNotes</a>. Pour la liste des
+<a href="<gitblob>ReleaseNotes">fichier ReleaseNotes</a>. Pour la liste des
 changements contenant à la fois les versions stables et développement, voyez le
-<a href="<svnsandbox>ChangeLog">fichier ChangeLog</a>.
+<a href="<gitblob>ChangeLog">fichier ChangeLog</a>.
 </p>
 </div>
 <div class="underline"></div>

fr/faq-abuse.wml

Zeige Datei @ f85239e9e

@@ -127,7 +127,7 @@ a connu un problème avec un groupe organisé d'utilisateurs malveillants qui jo
 href="#ExitPolicies">stratégies de sortie individuelles</a>. Beaucoup de relais Tor n'autorisent aucune sortie de connexion. Parmi ceux qui effectivement autorisent des sorties de connexion, beaucoup peuvent déjà ne pas autoriser l'accès à votre service. Lorsque vous procédez au bannissement des nœuds, vous devriez sélectionner selon les stratégies de sortie et ne bannir que ceux qui autorisent ces connexions. Et souvenez-vous que les stratégies de sortie peuvent changer (ainsi que plus globalement, la liste des nœuds sur le réseau).</p>
 
 <p>Si vraiment bannir les nœuds est ce que vous souhaitez, nous pouvons fournir un
-<a href="<svnsandbox>contrib/exitlist">script en Python pour extraire le répertoire Tor</a>. Notez que ce script ne vous donnera pas une liste absolument parfaite des adresses IP qui se connecteraient à votre service via Tor, car certains relais Tor peuvent sortir en utilisant une adresse IP différente de celle qu'ils publient.
+<a href="<gitblob>contrib/exitlist">script en Python pour extraire le répertoire Tor</a>. Notez que ce script ne vous donnera pas une liste absolument parfaite des adresses IP qui se connecteraient à votre service via Tor, car certains relais Tor peuvent sortir en utilisant une adresse IP différente de celle qu'ils publient.
 Pour une approche plus poussée (avec probablement une interface plus facile pour 
 vous), consultez le <a href="http://exitlist.torproject.org/">service 
 TorDNSEL</a>.

fr/hidden-services.wml

Zeige Datei @ f85239e9e

@@ -66,7 +66,7 @@ En général, la connexion complète entre le client et le service caché est co
 <img alt="Tor services cachés étape six" src="$(IMGROOT)/THS-6.png" />
 
 <p>
-Il existe davantage de documentations détaillées sur le protocole de service caché que celle-ci. Voir le <a href="<svnsandbox>doc/design-paper/tor-design.pdf">document de spécification de Tor</a> pour une description plus approfondie ainsi que la <a href="<svnsandbox>doc/spec/rend-spec.txt">spécification rendez-vous</a> pour le format de messages.
+Il existe davantage de documentations détaillées sur le protocole de service caché que celle-ci. Voir le <a href="<gitblob>doc/design-paper/tor-design.pdf">document de spécification de Tor</a> pour une description plus approfondie ainsi que la <a href="<gitblob>doc/spec/rend-spec.txt">spécification rendez-vous</a> pour le format de messages.
 </p>
 
   </div><!-- #main -->

fr/volunteer.wml

Zeige Datei @ f85239e9e

@@ -98,7 +98,7 @@ traduire en Arabe ou en Persan pour les utilisateurs Tor situés dans les zones
 <p>Vous pouvez trouver que certains de ces projets sont de bonnes idées pour le <a href="<page
   	 gsoc>">Google Summer of Code 2008</a>. Nous avons marqué chaque idée en fonction de l'utilité qu'il apporte à l'ensemble du projet Tor (priorité), de la quantité de travail que nous estimons (niveau d'effort), du l'expérience que vous devriez avoir pour commencer (niveau de qualification), et qui de <a href="<page
   	 people>#Core">nos principaux développeurs</a> pourrait être de bons tuteurs. Il ya plein d'autres bonnes idées pour travailler - voir par exemple la liste des <a
-  	 href="<svnsandbox>doc/spec/proposals/">propositions actuelles</a>, ou tout simplement vos propres idées.</p>
+  	 href="<gittree>doc/spec/proposals/">propositions actuelles</a>, ou tout simplement vos propres idées.</p>
 <ol>
 
 <li>
@@ -116,7 +116,7 @@ Demandes au premier Avril 00:00 UTC: <i>5</i>
 <br />
 
 Le scanner des nœuds de sortie Tor 'SoaT', partie du <a
-href="<svnsandbox>../torflow/">projet Torflow</a>, est
+href="<gittree>../torflow/">projet Torflow</a>, est
 pour l'instant écrit dans un perl plutôt bancal et s'appuie sur des MD5sums de
 documents entiers dans le but de savoir si un nœud de sortie modifie les contenus. 
 The problem with this is threefold: 1) Perl sucks at life.
@@ -290,7 +290,7 @@ Demandes au premier Avril 00:00 UTC: <i>1</i>
 Vidalia currently doesn't play nicely on Debian and Ubuntu with the
 default Tor packages. The current Tor packages automatically start Tor
 as a daemon running as the debian-tor user and (sensibly) do not have a
-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
 in the default torrc. Consequently, Vidalia will try
 to start its own Tor process since it could not connect to the existing
 Tor, and Vidalia's Tor process will then exit with an error message
@@ -340,20 +340,20 @@ Niveau de difficulté : <i>élevé</i>
 Mentors supposés : <i>Nick</i>
 <br />
 The Tor 0.2.0.x series makes <a
-href="<svnsandbox>doc/design-paper/blocking.html">significant
+href="<gitblob>doc/design-paper/blocking.html">significant
 improvements</a> in resisting national and organizational censorship.
 But Tor still needs better mechanisms for some parts of its
 anti-censorship design.  For example, current Tors can only listen on a
 single address/port combination at a time.  There's
-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
 proposal to address this limitation</a> and allow clients to connect
 to any given Tor on multiple addresses and ports, but it needs more
 work.  Another anti-censorship project (far more difficult) is to try
 to make Tor more scanning-resistant.  Right now, an adversary can identify
-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
 just by trying to connect to them, following the Tor protocol, and
 seeing if they respond.  To solve this, bridges could
-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
 webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
 and not act like bridges until the user provides a bridge-specific key.
 <br />
@@ -511,7 +511,7 @@ Tor pour tester leur code.
 <br />
 If you want to make the project more exciting
 and involve more design and coding, take a look at <a
-href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
+href="<gitblob>doc/spec/proposals/131-verify-tor-usage.txt">proposal
 131-verify-tor-usage.txt</a>.
 </li>
 
@@ -713,7 +713,7 @@ OnionCoffee</a>, et le faire tourner sur <a
 href="http://code.google.com/android/">Android</a>. La première étape
 pourrait être de porter le code existant et l'exécuter dans un environnement
 Android. Ensuite, le code pourrait être mis à jour pour supporter les nouvelles
-version de protocole comme la <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
+version de protocole comme la <a href="<gitblob>doc/spec/dir-spec.txt">v3
 des protocole d'annuaire</a>. Ensuite, le support pour les requêtes ou même
 apporter des services cachés serait sympa, mais non requis. L'étudiant
 devrait être capable de comprendre et écrire du code Java, comprenant
@@ -945,7 +945,7 @@ the core of the Blossom effort.
 <b>Proposer de nouvelles idées !</b>
 <br />
 Vous n'aimez aucune de celles-ci ? Regardez la <a
-href="<svnsandbox>doc/design-paper/roadmap-future.pdf">
+href="<gitblob>doc/design-paper/roadmap-future.pdf">
 feuille de développement de Tor</a> pour plus d'idées.
 </li>
 
@@ -991,7 +991,7 @@ cela signifie que seuls des flux TCP peuvent être raisonnablement supportés. N
 href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP"> liste 
 de raisons pour lesquelles nous n'avons pas bifurqué vers le transport par UDP</a>, mais ce serait 
 bien de voir cette liste se raccourcir. Nous avons aussi proposé <a 
-href="<svnsandbox>tor/doc/100-tor-spec-udp.txt">une spécification pour Tor et 
+href="<gitblob>tor/doc/100-tor-spec-udp.txt">une spécification pour Tor et 
 UDP</a> &mdash; lisez-la et faites-nous part de vos remarques et critiques, s'il-vous-plaît.</li>
 <li>Nous ne sommes plus très loin d'avoir le support pour IPV6 entre les serveurs de sorties 
 et les adresses finales. Si IPV6 vous tient à cœur, partir de là est sans doute 

gui/en/technotes.wml

Zeige Datei @ f85239e9e

@@ -49,7 +49,7 @@ 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
+<p>You may find the <a href="<gitblob>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.

include/links.wmi

Zeige Datei @ f85239e9e

@@ -1,6 +1,7 @@
 #!wml
 
-<define-tag svnsandbox whitespace=delete>http://gitweb.torproject.org/tor/tor.git/blob/HEAD:/</define-tag>
+<define-tag gitblob whitespace=delete>http://gitweb.torproject.org/tor/tor.git/blob/HEAD:/</define-tag>
+<define-tag gittree whitespace=delete>http://gitweb.torproject.org/tor/tor.git/tree/HEAD:/</define-tag>
 <define-tag svnwebsite whitespace=delete>https://svn.torproject.org/svn/website/trunk/</define-tag>
 
 #  Xinclude "locallinks.wmi"

it/bridges.wml

Zeige Datei @ f85239e9e

@@ -182,7 +182,7 @@ a seconda della tua piattaforma).
 <p>
 Se ti interessa saperne di pi&ugrave; sui bridge da un punto di vista tecnico,
 leggi la <a
-href="<svnsandbox>doc/spec/bridges-spec.txt">Tor
+href="<gitblob>doc/spec/bridges-spec.txt">Tor
 bridges specification</a>. Se vuoi gestire un bridge privato o usarlo
 in altri modi particolari, leggi le specifiche.
 </p>

it/documentation.wml

Zeige Datei @ f85239e9e

@@ -98,7 +98,7 @@ come viene realizzato Tor.
 
 <li>
 C'&egrave; una succinta <a
-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">lista di cose
+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">lista di cose
 che vorremmo fare in futuro</a>. Anche se molte di queste cose sono 
 un po' troppo oscure per venir comprese da chi non sia un
 programmatore di Tor, puoi senz'altro avere un'idea generale dei prossimi
@@ -115,7 +115,7 @@ and circumvention" dal 23C3 nel Dicembre 2006 (<a
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
 <a href="http://freehaven.net/~arma/slides-23c3.pdf">slide</a>,
 <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
-<a href="<svnsandbox>doc/design-paper/blocking.html">design paper</a>),
+<a href="<gitblob>doc/design-paper/blocking.html">design paper</a>),
 e la presentazione "Current events in 2007" sempre di Roger al 24C3 nel Dicembre
 2007 (<a
 href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
@@ -137,13 +137,13 @@ href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>.
 
 <li>
 Studiati il <a
-href="<svnsandbox>doc/spec/proposals/001-process.txt">processo per la proposta
+href="<gitblob>doc/spec/proposals/001-process.txt">processo per la proposta
 di modifiche al design di Tor</a>, e dai un'occhiata alle <a
-href="<svnsandbox>doc/spec/proposals/">proposte fatte finora</a>.
+href="<gittree>doc/spec/proposals/">proposte fatte finora</a>.
 </li>
 
 <li>
-Il nostro <a href="<svnsandbox>doc/TODO">developer TODO file</a> inizia con una serie di
+Il nostro <a href="<gitblob>doc/TODO">developer TODO file</a> inizia con una serie di
 scadenze temporali per gi impegni esterni &mdash; le cose che <a href="<page sponsors>">i nostri
 sponsor</a> hanno pagato per vedere realizzate. Sono elencate anche molte
 altre attivit&agrave; e problemi che ci piacerebbe affrontare.
@@ -185,12 +185,12 @@ href="http://archives.seul.org/or/cvs/">commit svn e git</a>.</li>
 <li>I <b>documenti di design</b> (pubblicati alla Usenix Security 2004)
 forniscono i fondamenti e le analisi di sicurezza di Tor:
 in versione
-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> e
-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>.
+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> e
+<a href="<gitblob>doc/design-paper/tor-design.html">HTML</a>.
 </li>
 <li>Il nostro studio successivo sulle <b>sfide nell'anonimato a bassa latenza</b>
 (ancora in versione di bozza) descrive nel dettaglio esperienze e direzioni di sviluppo recenti:
-<a href="<svnsandbox>doc/design-paper/challenges.pdf">bozza
+<a href="<gitblob>doc/design-paper/challenges.pdf">bozza
 PDF</a>.</li>
 <li>Il nostro paper al WEIS 2006 &mdash; <b>Anonymity Loves Company:
 Usability and the Network Effect</b> &mdash; spiega perch&eacute; l'usabilit&agrave; nei
@@ -199,8 +199,8 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
 <li>Il nostro progetto preliminare per impedire ai firewall di
 bloccare l'accesso alla rete Tor &egrave; descritto in
 <b>design of a blocking-resistant anonymity system</b>:
-<a href="<svnsandbox>doc/design-paper/blocking.pdf">bozza PDF</a> e
-<a href="<svnsandbox>doc/design-paper/blocking.html">bozza HTML</a>.
+<a href="<gitblob>doc/design-paper/blocking.pdf">bozza PDF</a> e
+<a href="<gitblob>doc/design-paper/blocking.html">bozza HTML</a>.
 Vedi anche le <a
 href="http://freehaven.net/~arma/slides-23c3.pdf">diapositive</a> e il<a
 href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>
@@ -211,25 +211,25 @@ dell'<a href="http://events.ccc.de/congress/2006/Home">intervento al 23C3
 <li> Le <b>specifiche</b> intendono fornire agli sviluppatori le informazioni 
 sufficienti per realizzare una versione compatibile di Tor:
 <ul>
-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">le specifiche principali di Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">specifiche Tor
+<li><a href="<gitblob>doc/spec/tor-spec.txt">le specifiche principali di Tor</a></li>
+<li><a href="<gitblob>doc/spec/dir-spec.txt">specifiche Tor
 version 3 directory server</a> (e le pi&ugrave; vecchie directory specification <a
-href="<svnsandbox>doc/spec/dir-spec-v1.txt">versione 1</a> e <a
-href="<svnsandbox>doc/spec/dir-spec-v2.txt">versione 2</a>)
+href="<gitblob>doc/spec/dir-spec-v1.txt">versione 1</a> e <a
+href="<gitblob>doc/spec/dir-spec-v2.txt">versione 2</a>)
 </li>
-<li><a href="<svnsandbox>doc/spec/control-spec.txt">specifiche del protocollo di controllo
+<li><a href="<gitblob>doc/spec/control-spec.txt">specifiche del protocollo di controllo
 Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">le specifiche del Tor rendezvous
+<li><a href="<gitblob>doc/spec/rend-spec.txt">le specifiche del Tor rendezvous
 </a></li>
-<li><a href="<svnsandbox>doc/spec/path-spec.txt">specifiche per Tor path selection
+<li><a href="<gitblob>doc/spec/path-spec.txt">specifiche per Tor path selection
 </a></li>
-<li><a href="<svnsandbox>doc/spec/address-spec.txt">nomi host speciali in
+<li><a href="<gitblob>doc/spec/address-spec.txt">nomi host speciali in
 Tor</a></li>
-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">supporto SOCKS in Tor
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">supporto SOCKS in Tor
 ed estensioni</a></li>
-<li><a href="<svnsandbox>doc/spec/version-spec.txt">come funzionano i numeri di versione di Tor
+<li><a href="<gitblob>doc/spec/version-spec.txt">come funzionano i numeri di versione di Tor
 </a></li>
-<li><a href="<svnsandbox>doc/spec/proposals/">bozze in divenire delle
+<li><a href="<gittree>doc/spec/proposals/">bozze in divenire delle
 nuove specifiche e dei cambiamenti proposti</a></li>
 </ul></li>
 
@@ -261,7 +261,7 @@ href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">questi
 <h2><a class="anchor" href="#Developers">Per gli Sviluppatori</a></h2>
 Consulta il <b>repository dei sorgenti</b> di Tor:
   <ul>
-    <li><a href="<svnsandbox>">Consulta direttamente l'albero dei sorgenti nel repository</a></li>
+    <li><a href="<gittree>">Consulta direttamente l'albero dei sorgenti nel repository</a></li>
     <li>Accesso in sola lettura
       <ul>
         <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>

it/download-unix.wml

Zeige Datei @ f85239e9e

@@ -245,7 +245,7 @@ grossi bachi di sicurezza ed affidabilit&agrave;. Tenetevi pronti a <a href="htt
 <div class="nb">
 <p>
 Tor viene distribuito come <a href="http://www.fsf.org/">Free Software</a>
-sotto le <a href="<svnsandbox>LICENSE">3-clausole della licenza BSD</a>. I
+sotto le <a href="<gitblob>LICENSE">3-clausole della licenza BSD</a>. I
 pacchetti includono anche <a href="<page vidalia/index>">Vidalia</a>
 e <a href="http://www.privoxy.org/">Privoxy</a>, che sono programmi
 di supporto distribuiti sotto la licenza GNU GPL.
@@ -387,9 +387,9 @@ href="<page mirrors>">lista dei mirror del sito Tor</a>.
 <a id="Testing"></a>
 <p>
 Per  avere una lista dei cambiamenti in ciascuna versione stabile di Tor, vedi le
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Per una lista dei
+<a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Per una lista dei
 cambiamenti nella stabile e nella versione di sviluppo, vedi il
-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
+<a href="<gitblob>ChangeLog">ChangeLog</a>.
 </p>
 </div>
   </div><!-- #main -->

it/download.wml

Zeige Datei @ f85239e9e

@@ -147,7 +147,7 @@ gravi bachi nel funzionamento, nell'affidabilit&agrave; e nella sicurezza. Prepa
 <div class="nb">
 <p>
 Tor viene distribuito come <a href="http://www.fsf.org/">Free Software</a>
-sotto le <a href="<svnsandbox>LICENSE">3-clausole della licenza BSD</a>. I
+sotto le <a href="<gitblob>LICENSE">3-clausole della licenza BSD</a>. I
 pacchetti includono anche <a href="<page vidalia/index>">Vidalia</a>
 e <a href="http://www.privoxy.org/">Privoxy</a>, che sono programmi
 di supporto distribuiti sotto la licenza GNU GPL.
@@ -284,9 +284,9 @@ href="<page mirrors>">lista dei siti mirror del sito Tor</a>.
 <a id="Testing"></a>
 <p>
 Per una lista dei cambiamenti in ogni release stabile di Tor, leggi le
-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Per una lista
+<a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Per una lista
 delle modifiche nelle versioni sia stabili sia di sviluppo, vai al
-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
+<a href="<gitblob>ChangeLog">ChangeLog</a>.
 </p>
 
 <a id="Dev"></a>

it/faq.wml

Zeige Datei @ f85239e9e

@@ -252,7 +252,7 @@ un permesso speciale.
 
 <p>
 Se per&ograve; vuoi redistribuire il software Tor devi rispettare la nostra
-<a href="<svnsandbox>LICENSE">LICENZA</a>.
+<a href="<gitblob>LICENSE">LICENZA</a>.
 In sotanza significa che devi includere il nostro file LICENSE insieme
 alle parti del software Tor che distribuisci.
 </p>
@@ -586,7 +586,7 @@ delle firme</a> per ulteriosi dettagli.
 
 <p>
 Prova questa procedura: <a
-href="<svnsandbox>doc/tor-win32-mingw-creation.txt"><svnsandbox>doc/tor-win32-mingw-creation.txt</a>.
+href="<gitblob>doc/tor-win32-mingw-creation.txt"><gitblob>doc/tor-win32-mingw-creation.txt</a>.
 </p>
 
 <p>
@@ -931,7 +931,7 @@ non serve a nulla.
 <b>Autenticazione</b>:
 Ogni relay Tor ha una chiave pubblica di decifratura detta "onion key".
 Quanto il client Tor stabilisce dei circuiti, ad ogni passaggio <a
-href="<svnsandbox>doc/design-paper/tor-design.html#subsec:circuits">richiede
+href="<gitblob>doc/design-paper/tor-design.html#subsec:circuits">richiede
 che il relay Tor dimostri di conoscere la sua onion key</a>. In questo modo
 il primo nodo del percorso non pu&ograve; semplicemente falsificare il resto del percorso.
 Ogni relay ruota la sua onion key ogni settimana.
@@ -943,7 +943,7 @@ In che modo i client scoprono quali sono i relay, e come sanno quali sono le
 chiavi giuste per essi? Ogni relay ha una chiave pubblica di lungo periodo per la firma (long-term signing key)
 detta "identity key". Ogni directory authority inolre ha una
 "directory signing key". Le directory authority <a
-href="<svnsandbox>doc/spec/dir-spec.txt">forniscono una lista firmata</a>
+href="<gitblob>doc/spec/dir-spec.txt">forniscono una lista firmata</a>
 di tutti i relay noti, lista che contiene un set di certificati da ciascun
 relay (self-signed con la loro identity key) che ne indica le chiavi,
 l'indirizzo, exit policy eccetera. Un avversario non pu&ograve; quindi ingannare
@@ -1030,7 +1030,7 @@ vitare che tutti i relay debbano potersi connettere a tutti i relay
 Tor) sia della directory (smettere di obbligare tutti gli utenti Tor
 a sapere quali sono tutti i relay Tor). Simili cabiamenti potrebbero avere
 un impatto enorme sull'anonimato potenziale e reale. Vedi la sezione 5 del paper <a
-href="<svnsandbox>doc/design-paper/challenges.pdf">Challenges</a>
+href="<gitblob>doc/design-paper/challenges.pdf">Challenges</a>
 per maggiori informazioni. Ancora, il trasporto UDP potrebbe essere molto utile qui.
 </p>
 

it/hidden-services.wml

Zeige Datei @ f85239e9e

@@ -145,9 +145,9 @@ service.
 <p>
 Ci sono descrizioni del protocollo hidden service pi&ugrave; approfondite 
 di questa. Vedi il
-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">Tor design paper</a>
+<a href="<gitblob>doc/design-paper/tor-design.pdf">Tor design paper</a>
 per una descrizione dettagliata e la
-<a href="<svnsandbox>doc/spec/rend-spec.txt">rendezvous specification</a>
+<a href="<gitblob>doc/spec/rend-spec.txt">rendezvous specification</a>
 per il formato dei messaggi.
 </p>
 

it/people.wml

Zeige Datei @ f85239e9e

...	...	@@ -52,7 +52,7 @@ management e supporto generale. Hacker di pacchetti per Windows, OS
52	52	X, e varie distribuzioni Linux. </dd>
53	53	<dt>Karsten Loesing (Developer)</dt><dd> Durante il Google

...	...	@@ -163,7 +163,7 @@ v <tt>ORPort</tt> a "otisk" neboli fingerprint Vašeho serveru. Fingerprint by m
163	163
164	164	<p>
165	165	Chcete-li se dozvědět víc o přemosťovacích serverech (Bridge-serverech) z technického hlediska, prosím čtěte<a
166		-href="<svnsandbox>doc/spec/bridges-spec.txt">Tor bridges specification</a>. Máte-li zájem o zprovoznění
	166	+href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges specification</a>. Máte-li zájem o zprovoznění
167	167	privátního přemosťovacího serveru nebo jiných specifických použitích, prosím čtěte specifikaci.
168	168	</p>
169	169

...	...	@@ -157,7 +157,7 @@ oben</a> an. Den Fingerprint findest du in den Logdateien oder in <tt>
157	157	/var/lib/tor/fingerprint</tt>, in Abhängigkeit von deiner Plattform. </p>
158	158
159	159	<p>Falls du mehr über Brücken-Server aus einer technischen Perspektive lernen
160		-willst, lies bitte <a href="<svnsandbox>doc/spec/bridges-spec.txt">die
	160	+willst, lies bitte <a href="<gitblob>doc/spec/bridges-spec.txt">die
161	161	Spezifikation zu den Brücken-Servern</a>. Wenn du eine unveröffentlichte
162	162	Brücke betreiben willst, schau bitte in die Spezifikation. </p>
163	163

...	...	@@ -71,7 +71,7 @@ Spezifikationen im Stile von RFCs, die exakt beschreiben, wie Tor aufgebaut
71	71	ist.</li>
72	72
73	73	<li>Es gibt eine skelettartige <a
74		-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Liste von Einträgen,
	74	+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Liste von Einträgen,
75	75	die wir in Zukunft anpacken wollen</a>. Viele der Einträge müssen noch
76	76	ausgearbeitet werden, bevor sie für andere Sinn ergeben. Du kannst jedoch eine
77	77	generelle Idee bekommen, was als nächstes erledigt werden muss.</li>
...	...	@@ -86,7 +86,7 @@ Rogers Vortrag <q>blocking-resistance and circumvention</q> vom 23C3 im Dezember
86	86	href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">Video</a>, <a
87	87	href="http://freehaven.net/~arma/slides-23c3.pdf">Folien</a>, <a
88	88	href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">Kurzdarstellung</a>,
89		-<a href="<svnsandbox>doc/design-paper/blocking.html">Designvorschlag</a>) und
	89	+<a href="<gitblob>doc/design-paper/blocking.html">Designvorschlag</a>) und
90	90	Rogers Vortrag <q>Current events in 2007</q> vom 24C3 aus dem Dezember 2007 (<a
91	91	href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">Video</a>,
92	92	<a href="http://freehaven.net/~arma/slides-24c3.pdf">Folien</a>, <a
...	...	@@ -105,11 +105,11 @@ href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>
105	105	ein.</li>
106	106
107	107	<li>Lerne über den <a
108		-href="<svnsandbox>doc/spec/proposals/001-process.txt">Prozess der Proposals, um
	108	+href="<gitblob>doc/spec/proposals/001-process.txt">Prozess der Proposals, um
109	109	das Design von Tor zu ändern</a> und schaue dir auch die <a
110		-href="<svnsandbox>doc/spec/proposals/">existierenden Proposals</a> an.</li>
	110	+href="<gittree>doc/spec/proposals/">existierenden Proposals</a> an.</li>
111	111
112		-<li>Unsere <a href="<svnsandbox>doc/TODO">TODO-Datei für Entwickler</a> startet
	112	+<li>Unsere <a href="<gitblob>doc/TODO">TODO-Datei für Entwickler</a> startet
113	113	mit einer Zeitplanung für externe Versprechen — Dinge, für die <a
114	114	href="<page sponsors>">unsere Sponsoren</a> bezahlt haben. Es listet auch
115	115	weitere Themen und Aufgaben auf, die wir gern bearbeiten würden.</li>
...	...	@@ -153,13 +153,13 @@ ist das die Liste für dich.</li> </ul>
153	153	<ul>
154	154	<li>Das <b>Designdokument</b> (zur Usenix Security 2004 veröffentlicht)
155	155	gibt dir unsere Einstellungen und Sicherheitsanalyse zum Tor-Design:
156		- <a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF-Entwurf (engl.)</a> und
157		- <a href="<svnsandbox>doc/design-paper/tor-design.html">HTML-Entwurf (engl.)</a>
	156	+ <a href="<gitblob>doc/design-paper/tor-design.pdf">PDF-Entwurf (engl.)</a> und
	157	+ <a href="<gitblob>doc/design-paper/tor-design.html">HTML-Entwurf (engl.)</a>
158	158	stehen zur Verfügung.</li>
159	159	<li>Das darauf folgende Papier mit dem Titel <q>challenges in low-latency
160	160	anonymity</q> (noch im Entwurf) hat mehr Details über die letzten
161	161	Erfahrungen und Richtungen: <a
162		- href="<svnsandbox>doc/design-paper/challenges.pdf">PDF version
	162	+ href="<gitblob>doc/design-paper/challenges.pdf">PDF version
163	163	(engl.)</a>.</li>
164	164	<li>Unsere Veröffentlichung bei der WEIS 2006 — <b>Anonymity Loves
165	165	Company: Usability and the Network Effect</b> — erklärt, warum
...	...	@@ -169,7 +169,7 @@ ist das die Liste für dich.</li> </ul>
169	169	<li>Unser vorläufiges Design, um Firewalls den Zugriff auf das
170	170	Tornetzwerk zu erschweren, ist in <b>design of a blocking-resistant
171	171	anonymity system</b> (<a
172		- href="<svnsandbox>doc/design-paper/blocking.pdf">PDF-Entwurf</a>)
	172	+ href="<gitblob>doc/design-paper/blocking.pdf">PDF-Entwurf</a>)
173	173	beschrieben. Du kannst auch einen Blick auf die <a
174	174	href="http://freehaven.net/~arma/slides-23c3.pdf">Vortragsunterlagen</a>
175	175	oder das <a
...	...	@@ -180,25 +180,25 @@ ist das die Liste für dich.</li> </ul>
180	180	<li>Die <b>Spezifikation</b> zielt darauf ab, Entwicklern genügend Information zu
181	181	geben, um eine zu Tor kompatible Version zu schaffen:
182	182	<ul>
183		- <li><a href="<svnsandbox>doc/spec/tor-spec.txt">Main Tor
	183	+ <li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor
184	184	specification (engl.)</a></li>
185		- <li><a href="<svnsandbox>doc/spec/dir-spec.txt">Tor
	185	+ <li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
186	186	version 3 directory server specification</a> (und die ältere <a
187		- href="<svnsandbox>doc/spec/dir-spec-v1.txt">Version 1</a> und <a
188		- href="<svnsandbox>doc/spec/dir-spec-v2.txt">Version 2</a>
	187	+ href="<gitblob>doc/spec/dir-spec-v1.txt">Version 1</a> und <a
	188	+ href="<gitblob>doc/spec/dir-spec-v2.txt">Version 2</a>
189	189	Verzeichnisspezifikationen)</li>
190		- <li><a href="<svnsandbox>doc/spec/control-spec.txt">Tor control protocol
	190	+ <li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
191	191	specification</a></li>
192		- <li><a href="<svnsandbox>doc/spec/rend-spec.txt">Tor rendezvous specification (engl.)</a></li>
193		- <li><a href="<svnsandbox>doc/spec/path-spec.txt">Tor path selection
	192	+ <li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous specification (engl.)</a></li>
	193	+ <li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
194	194	specification</a></li>
195		- <li><a href="<svnsandbox>doc/spec/address-spec.txt">Special
	195	+ <li><a href="<gitblob>doc/spec/address-spec.txt">Special
196	196	hostnames in Tor</a></li>
197		- <li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS
	197	+ <li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS
198	198	Unterstützung und Erweiterungen</a></li>
199		- <li><a href="<svnsandbox>doc/spec/version-spec.txt">How Tor version
	199	+ <li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version
200	200	numbers work</a></li>
201		- <li><a href="<svnsandbox>doc/spec/proposals/">Entwürfe neuer Spezifikationen
	201	+ <li><a href="<gitblob>doc/spec/proposals/">Entwürfe neuer Spezifikationen
202	202	und geplante Änderungen</a>.</li>
203	203	</ul></li>
204	204	<li>Wirf einen Blick auf die <a href="http://freehaven.net/~arma/wth1.pdf">Folien</a>
...	...	@@ -218,11 +218,11 @@ ist das die Liste für dich.</li> </ul>
218	218	ein.</li>
219	219
220	220	<li>Lerne mehr über <a
221		- href="<svnsandbox>doc/spec/proposals/001-process.txt">den Prozess zur
	221	+ href="<gitblob>doc/spec/proposals/001-process.txt">den Prozess zur
222	222	Veränderung unseres Designs</a> und schaue durch die <a
223		- href="<svnsandbox>doc/spec/proposals/">existierende Proposals</a>.</li>
	223	+ href="<gittree>doc/spec/proposals/">existierende Proposals</a>.</li>
224	224
225		- <li>Unsere <a href="<svnsandbox>doc/TODO">TODO-Datei</a> startet mit einer
	225	+ <li>Unsere <a href="<gitblob>doc/TODO">TODO-Datei</a> startet mit einer
226	226	Zeitleiste für externe Versprechungen — Dinge für die unsere <a
227	227	href="<page sponsors>">Sponsoren</a> Geld gegeben haben. Es listet auch
228	228	weitere Themen auf.</li>
...	...	@@ -261,7 +261,7 @@ ist das die Liste für dich.</li> </ul>
261	261	<h2><a class="anchor" href="#Developers">Für Entwickler</a></h2>
262	262	Durchsuche das Tor <b>Quellen Repository</b>:
263	263	<ul>
264		- <li><a href="<svnsandbox>">Durchsuche den Quellcode direkt.</a></li>
	264	+ <li><a href="<gittree>">Durchsuche den Quellcode direkt.</a></li>
265	265	<li>Nur Lesezugriff:
266	266	<ul>
267	267	<li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>

...	...	@@ -242,7 +242,7 @@ href="https://bugs.torproject.org/"> Fehler zu berichten</a>.</p> </div>
242	242	<div class="underline"></div>
243	243	<div class="nb">
244	244	<p>Tor wird als <a href="http://www.fsf.org/">Freie Software</a> unter der
245		-<a href="<svnsandbox>LICENSE">3-clause-BSD-Lizenz</a> verteilt. Die Pakete
	245	+<a href="<gitblob>LICENSE">3-clause-BSD-Lizenz</a> verteilt. Die Pakete
246	246	schließen des Weiteren <a href="<page vidalia/index>">Vidalia</a>
247	247	und <a href="http://www.privoxy.org/">Privoxy</a> ein. Diese werden unter der
248	248	GNU GPL verteilt.</p>
...	...	@@ -347,9 +347,9 @@ spiegeln</a>.</p>
347	347	<a id="Stable"></a>
348	348	<a id="Testing"></a>
349	349	<p>Eine Liste der Änderungen in jeder stabilen Tor-Version findest du in den <a
350		-href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Eine Liste der Änderungen in
	350	+href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Eine Liste der Änderungen in
351	351	der stabilen und der Entwicklerversion ist im <a
352		-href="<svnsandbox>ChangeLog">ChangeLog</a>.</p>
	352	+href="<gitblob>ChangeLog">ChangeLog</a>.</p>
353	353	</p>
354	354	</div>
355	355	</div><!-- #main -->

...	...	@@ -149,7 +149,7 @@ Zuverlässigkeitsprobleme haben. Bitte hilf uns und <a
149	149	href="https://bugs.torproject.org/">melde Fehler</a>. </p> </div>
150	150
151	151	<div class="underline"></div> <div class="nb"> <p> Tor ist <a
152		-href="http://www.fsf.org/">Freie Software</a> unter der <a href="<svnsandbox>
	152	+href="http://www.fsf.org/">Freie Software</a> unter der <a href="<gitblob>
153	153	LICENSE">3-clause BSD Lizenz</a>. Die Bundles enthalten auch <a href="<page
154	154	vidalia/index>">Vidalia</a> und <a href="http://www.privoxy.org/">Privoxy</a>,
155	155	welche Hilfsprogramme unter der GNU GPL sind. </p> <p> There is no fee for
...	...	@@ -258,9 +258,9 @@ href="<page mirrors>">Liste von Spiegel-Seiten der Torhomepage</a>.
258	258
259	259	<a id="ChangeLog"></a> <a id="Stable"></a> <a id="Testing"></a> <p> Wenn du
260	260	wissen willst, was sich in den Stable-Versionen geändert hat, schau in die <a
261		-href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Für eine Liste der
	261	+href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Für eine Liste der
262	262	Änderungen in der Stable und in der Unstable Version schau in das <a
263		-href="<svnsandbox>ChangeLog">ChangeLog</a>. </p> </div> <div class="underline">
	263	+href="<gitblob>ChangeLog">ChangeLog</a>. </p> </div> <div class="underline">
264	264	</div>
265	265
266	266	<a id="Dev"></a>

...	...	@@ -140,10 +140,10 @@ Client und drei vom versteckten Dienst gewählt.
140	140	<p>Es gibt detailliertere Beschreibungen zu dem Protokoll als diese
141	141	Seite. Schaue dir hierzu die
142	142	<a
143		-href="<svnsandbox>doc/design-paper/tor-design.pdf">Designbeschreibung
	143	+href="<gitblob>doc/design-paper/tor-design.pdf">Designbeschreibung
144	144	von Tor</a> und die
145	145	<a
146		-href="<svnsandbox>doc/spec/rend-spec.txt">Rendezvous-Spezifikation</a>
	146	+href="<gitblob>doc/spec/rend-spec.txt">Rendezvous-Spezifikation</a>
147	147	an. Dort findest du genauere Informationen.
148	148	</p>
149	149

...	...	@@ -55,7 +55,7 @@ Linux Distributionen.</dd>
55	55
56	56	<dt>Karsten Loesing (Entwickler)</dt>
57	57	<dd>arbeitete an
58		- der <a href="<svnsandbox>doc/spec/proposals/114-distributed-storage.txt">Verteilung
	58	+ der <a href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">Verteilung
59	59	und Absicherung der Veröffentlichung der Deskriptoren der
60	60	versteckten Services</a>. Derzeit arbeitet er an der <a href="<page
61	61	projects/hidserv>">Beschleunigung und stärkeren Vertrauenswürdigkeit der

...	...	@@ -34,14 +34,14 @@ Fehler, die du in den bestehenden Seiten findest.
34	34
35	35	<ol>
36	36	<li>Schaue im <a
37		- href="<svnsandbox>website/en/">SVN-Verzeichnis der
	37	+ href="<gitblob>website/en/">SVN-Verzeichnis der
38	38	Webseite</a> nach den .wml-Dateien. Die wichtigsten sind dabei
39	39	<code>index.wml</code>, <code>overview.wml</code>,
40	40	<code>download*.wml</code>, <code>documentation.wml</code>,
41	41	<code>foot.wmi</code> und <code>navigation.wmi</code>.
42	42	Wir würden uns sehr freuen, wenn du diese
43	43	oder auch mehr übersetzen könntest: Übersetzungen von den ".wml" Dateien in
44		- <a href="<svnsandbox>website/docs/en/"><svnsandbox>website/docs/en/</a>
	44	+ <a href="<gitblob>website/docs/en/"><gitblob>website/docs/en/</a>
45	45	wären als nächstes nütlich. Du kannst einen Blick auf das <a
46	46	href="<svnwebsite>/de/">deutsche Archiv</a>
47	47	werfen, um Beispiele für die gewünschten Formate zu erhalten.</li>

...	...	@@ -60,7 +60,7 @@
60	60	herbeizuführen. Natürlich würde es durch Cron ausgeführt oder es
61	61	schläft eine bestimmte Zeit und macht dann die Änderungen. Kann
62	62	das jemand für uns schreiben und wir packen das dann
63		- nach <a href="<svnsandbox>contrib/">contrib</a>? Das wäre
	63	+ nach <a href="<gittree>contrib/">contrib</a>? Das wäre
64	64	eine gute Möglichkeit für den <a href="<page gui/index>">Tor GUI
65	65	Wettbewerb</a>.</li>
66	66	<li>Wenn wir gerade bei Geolocation sind, wäre es schön, wenn
...	...	@@ -226,20 +226,20 @@ Skill Level: <i>High</i>
226	226	Likely Mentors: <i>Nick, Roger, Steven</i>
227	227	<br />
228	228	The Tor 0.2.0.x series makes <a
229		-href="<svnsandbox>doc/design-paper/blocking.html">significant
	229	+href="<gitblob>doc/design-paper/blocking.html">significant
230	230	improvements</a> in resisting national and organizational censorship.
231	231	But Tor still needs better mechanisms for some parts of its
232	232	anti-censorship design. For example, current Tors can only listen on a
233	233	single address/port combination at a time. There's
234		-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
	234	+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
235	235	proposal to address this limitation</a> and allow clients to connect
236	236	to any given Tor on multiple addresses and ports, but it needs more
237	237	work. Another anti-censorship project (far more difficult) is to try
238	238	to make Tor more scanning-resistant. Right now, an adversary can identify
239		-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
	239	+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
240	240	just by trying to connect to them, following the Tor protocol, and
241	241	seeing if they respond. To solve this, bridges could
242		-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
	242	+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
243	243	webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
244	244	and not act like bridges until the user provides a bridge-specific key.
245	245	<br />
...	...	@@ -416,7 +416,7 @@ project</a>, and make it run on <a
416	416	href="http://code.google.com/android/">Android</a>. The first step
417	417	would be to port the existing code and execute it in an Android
418	418	environment. Next, the code should be updated to support the newer Tor
419		-protocol versions like the <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
	419	+protocol versions like the <a href="<gitblob>doc/spec/dir-spec.txt">v3
420	420	directory protocol</a>. Further, support for requesting or even
421	421	providing Tor hidden services would be neat, but not required.
422	422	<br />
...	...	@@ -653,9 +653,9 @@ and <a href="https://svn.torproject.org/svn/weather/trunk/TODO">TODO</a>.
653	653	<b>Bring up new ideas!</b>
654	654	<br />
655	655	Don't like any of these? Look at the <a
656		-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
	656	+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
657	657	roadmap</a> for more ideas.
658		-Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a>
	658	+Some of the <a href="<gittree>doc/spec/proposals/">current proposals</a>
659	659	might also be short on developers.
660	660	</li>
661	661
...	...	@@ -695,7 +695,7 @@ currently does not exist and would need to be developed as well.
695	695	Vidalia currently doesn't play nicely on Debian and Ubuntu with the
696	696	default Tor packages. The current Tor packages automatically start Tor
697	697	as a daemon running as the debian-tor user and (sensibly) do not have a
698		-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
	698	+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
699	699	in the default torrc. Consequently, Vidalia will try
700	700	to start its own Tor process since it could not connect to the existing
701	701	Tor, and Vidalia's Tor process will then exit with an error message
...	...	@@ -790,7 +790,7 @@ to interact minimally with Tor to test their code.
790	790	<br />
791	791	If you want to make the project more exciting
792	792	and involve more design and coding, take a look at <a
793		-href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
	793	+href="<gitblob>doc/spec/proposals/131-verify-tor-usage.txt">proposal
794	794	131-verify-tor-usage.txt</a>.
795	795	</li>
796	796	-->
...	...	@@ -803,7 +803,7 @@ href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
803	803	The <a href="http://p56soo2ibjkx23xo.onion/">exitlist software</a>
804	804	is written by our fabulous anonymous
805	805	contributer Tup. It's a DNS server written in Haskell that supports part of our <a
806		-href="<svnsandbox>doc/contrib/torel-design.txt">exitlist
	806	+href="<gitblob>doc/contrib/torel-design.txt">exitlist
807	807	design document</a>. Currently, it is functional and it is used by
808	808	check.torproject.org and other users. The issues that are outstanding
809	809	are mostly aesthetic. This wonderful service could use a much better
...	...	@@ -1030,7 +1030,7 @@ it means we can only reasonably support TCP streams. We have a <a
1030	1030	href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list
1031	1031	of reasons why we haven't shifted to UDP transport</a>, but it would
1032	1032	be great to see that list get shorter. We also have a proposed <a
1033		-href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
	1033	+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
1034	1034	for Tor and
1035	1035	UDP</a> — please let us know what's wrong with it.</li>
1036	1036
...	...	@@ -1143,7 +1143,7 @@ throughput experiment</a>. We'll need to measure and tweak, and maybe
1143	1143	overhaul if the results are good.</li>
1144	1144	<li>Our censorship-resistance goals include preventing
1145	1145	an attacker who's looking at Tor traffic on the wire from <a
1146		-href="<svnsandbox>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
	1146	+href="<gitblob>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
1147	1147	it from normal SSL traffic</a>. Obviously we can't achieve perfect
1148	1148	steganography and still remain usable, but for a first step we'd like to
1149	1149	block any attacks that can win by observing only a few packets. One of

...	...	@@ -190,7 +190,7 @@ depending on your platform).
190	190	<p>
191	191	If you would like to learn more about our bridge
192	192	design from a technical standpoint, please read the <a
193		-href="<svnsandbox>doc/spec/bridges-spec.txt">Tor bridges
	193	+href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges
194	194	specification</a>. If you're interested in running an unpublished bridge
195	195	or other non-standard uses, please do read the specification.
196	196	</p>

...	...	@@ -97,7 +97,7 @@ how Tor is built.
97	97
98	98	<li>
99	99	There's a skeletal <a
100		-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">list of items
	100	+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">list of items
101	101	we'd like to tackle in the future</a>. Alas, many of those items need
102	102	to be fleshed out more before they'll make sense to people who aren't
103	103	Tor developers, but you can still get a general sense of what issues
...	...	@@ -114,7 +114,7 @@ and circumvention" talk from 23C3 in December 2006 (<a
114	114	href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
115	115	<a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
116	116	<a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
117		-<a href="<svnsandbox>doc/design-paper/blocking.html">design paper</a>),
	117	+<a href="<gitblob>doc/design-paper/blocking.html">design paper</a>),
118	118	and Roger's "Current events in 2007" talk from 24C3 in December
119	119	2007 (<a
120	120	href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
...	...	@@ -137,13 +137,13 @@ script collection.
137	137
138	138	<li>
139	139	Learn about the <a
140		-href="<svnsandbox>doc/spec/proposals/001-process.txt">Tor
	140	+href="<gitblob>doc/spec/proposals/001-process.txt">Tor
141	141	proposal process for changing our design</a>, and look over the <a
142		-href="<svnsandbox>doc/spec/proposals/">existing proposals</a>.
	142	+href="<gittree>doc/spec/proposals/">existing proposals</a>.
143	143	</li>
144	144
145	145	<li>
146		-Our <a href="<svnsandbox>doc/TODO">developer TODO file</a> starts with a
	146	+Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a
147	147	timeline for external promises — things <a href="<page sponsors>">our
148	148	sponsors</a> have paid to see done. It also lists many other tasks
149	149	and topics we'd like to tackle next.
...	...	@@ -185,12 +185,12 @@ commits</a> may be interesting for developers.</li>
185	185	<ul>
186	186	<li>The <b>design document</b> (published at Usenix Security 2004)
187	187	gives our justifications and security analysis for the Tor design:
188		-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> and
189		-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
	188	+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> and
	189	+<a href="<gitblob>doc/design-paper/tor-design.html">HTML</a>
190	190	versions available.</li>
191	191	<li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
192	192	(still in draft form) details more recent experiences and directions:
193		-<a href="<svnsandbox>doc/design-paper/challenges.pdf">PDF
	193	+<a href="<gitblob>doc/design-paper/challenges.pdf">PDF
194	194	draft</a>.</li>
195	195	<li>Our paper at WEIS 2006 — <b>Anonymity Loves Company:
196	196	Usability and the Network Effect</b> — explains why usability in
...	...	@@ -199,31 +199,31 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
199	199	<li>Our preliminary design to make it harder for large firewalls to
200	200	prevent access to the Tor network is described in
201	201	<b>design of a blocking-resistant anonymity system</b>:
202		-<a href="<svnsandbox>doc/design-paper/blocking.pdf">PDF draft</a> and
203		-<a href="<svnsandbox>doc/design-paper/blocking.html">HTML draft</a>.
	202	+<a href="<gitblob>doc/design-paper/blocking.pdf">PDF draft</a> and
	203	+<a href="<gitblob>doc/design-paper/blocking.html">HTML draft</a>.
204	204	Want to <a href="<page volunteer>#Coding">help us build it</a>?</li>
205	205	<li>The <b>specifications</b> aim to give
206	206	developers enough information to build a compatible version of Tor:
207	207	<ul>
208		-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Main Tor specification</a></li>
209		-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Tor
	208	+<li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor specification</a></li>
	209	+<li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
210	210	version 3 directory server specification</a> (and older <a
211		-href="<svnsandbox>doc/spec/dir-spec-v1.txt">version 1</a> and <a
212		-href="<svnsandbox>doc/spec/dir-spec-v2.txt">version 2</a> directory
	211	+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> and <a
	212	+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> directory
213	213	specifications)</li>
214		-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Tor control protocol
	214	+<li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
215	215	specification</a></li>
216		-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Tor rendezvous
	216	+<li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous
217	217	specification</a></li>
218		-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Tor path selection
	218	+<li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
219	219	specification</a></li>
220		-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Special hostnames in
	220	+<li><a href="<gitblob>doc/spec/address-spec.txt">Special hostnames in
221	221	Tor</a></li>
222		-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS support
	222	+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support
223	223	and extensions</a></li>
224		-<li><a href="<svnsandbox>doc/spec/version-spec.txt">How Tor version numbers
	224	+<li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version numbers
225	225	work</a></li>
226		-<li><a href="<svnsandbox>doc/spec/proposals/">In-progress drafts of
	226	+<li><a href="<gitblob>doc/spec/proposals/">In-progress drafts of
227	227	new specifications and proposed changes</a></li>
228	228	</ul></li>
229	229
...	...	@@ -258,7 +258,7 @@ of anonymous communication systems.</li>
258	258	<h2><a class="anchor" href="#Developers">For Developers</a></h2>
259	259	Browse the Tor <b>source repository</b>:
260	260	<ul>
261		- <li><a href="<svnsandbox>">Browse the repository's source tree directly</a></li>
	261	+ <li><a href="<gittree>">Browse the repository's source tree directly</a></li>
262	262	<li>Git and SVN access:
263	263	<ul>
264	264	<li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>

...	...	@@ -233,7 +233,7 @@ serious reliability and security bugs in these downloads. Please be prepared to
233	233	<div class="nb">
234	234	<p>
235	235	Tor is distributed as <a href="http://www.fsf.org/">Free Software</a>
236		-under the <a href="<svnsandbox>LICENSE">3-clause BSD license</a>. The
	236	+under the <a href="<gitblob>LICENSE">3-clause BSD license</a>. The
237	237	bundles also include <a href="<page vidalia/index>">Vidalia</a>
238	238	and <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>, which are supporting
239	239	applications distributed under the GNU GPL.
...	...	@@ -368,9 +368,9 @@ href="<page mirrors>">list of sites mirroring the Tor site</a>.
368	368	<a id="Testing"></a>
369	369	<p>
370	370	For a list of what has changed in each stable Tor release, see the
371		-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. For a list of
	371	+<a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. For a list of
372	372	changes in both stable and development versions, see the
373		-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
	373	+<a href="<gitblob>ChangeLog">ChangeLog</a>.
374	374	</p>
375	375	</div>
376	376	</div><!-- #main -->

...	...	@@ -150,7 +150,7 @@ serious reliability and security bugs in these downloads. Please be prepared to
150	150	<div class="nb">
151	151	<p>
152	152	Tor is distributed as <a href="http://www.fsf.org/">Free Software</a>
153		-under the <a href="<svnsandbox>LICENSE">3-clause BSD license</a>. The
	153	+under the <a href="<gitblob>LICENSE">3-clause BSD license</a>. The
154	154	bundles also include <a href="<page vidalia/index>">Vidalia</a>
155	155	and <a href="http://www.privoxy.org/">Privoxy</a>, which are supporting
156	156	applications distributed under the GNU GPL.
...	...	@@ -287,9 +287,9 @@ href="<page mirrors>">list of sites mirroring the Tor site</a>.
287	287	<a id="Testing"></a>
288	288	<p>
289	289	For a list of what has changed in each stable Tor release, see the
290		-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. For a list of
	290	+<a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. For a list of
291	291	changes in both stable and development versions, see the
292		-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
	292	+<a href="<gitblob>ChangeLog">ChangeLog</a>.
293	293	</p>
294	294	</div>
295	295	<div class="underline"></div>

...	...	@@ -251,7 +251,7 @@ ask us for specific permission.
251	251
252	252	<p>
253	253	However, if you want to redistribute the Tor software you must follow our
254		-<a href="<svnsandbox>LICENSE">LICENSE</a>.
	254	+<a href="<gitblob>LICENSE">LICENSE</a>.
255	255	Essentially this means that you need to include our LICENSE file along
256	256	with whatever part of the Tor software you're distributing.
257	257	</p>
...	...	@@ -590,7 +590,7 @@ Windows?</a></h3>
590	590
591	591	<p>
592	592	Try following the steps at <a
593		-href="<svnsandbox>doc/tor-win32-mingw-creation.txt"><svnsandbox>doc/tor-win32-mingw-creation.txt</a>.
	593	+href="<gitblob>doc/tor-win32-mingw-creation.txt"><gitblob>doc/tor-win32-mingw-creation.txt</a>.
594	594	</p>
595	595
596	596	<p>
...	...	@@ -935,7 +935,7 @@ won't work.
935	935	<b>Authentication</b>:
936	936	Every Tor relay has a public decryption key called the "onion key".
937	937	When the Tor client establishes circuits, at each step it <a
938		-href="<svnsandbox>doc/design-paper/tor-design.html#subsec:circuits">demands
	938	+href="<gitblob>doc/design-paper/tor-design.html#subsec:circuits">demands
939	939	that the Tor relay prove knowledge of its onion key</a>. That way
940	940	the first node in the path can't just spoof the rest of the path.
941	941	Each relay rotates its onion key once a week.
...	...	@@ -947,7 +947,7 @@ How do clients know what the relays are, and how do they know that they
947	947	have the right keys for them? Each relay has a long-term public signing
948	948	key called the "identity key". Each directory authority additionally has a
949	949	"directory signing key". The directory authorities <a
950		-href="<svnsandbox>doc/spec/dir-spec.txt">provide a signed list</a>
	950	+href="<gitblob>doc/spec/dir-spec.txt">provide a signed list</a>
951	951	of all the known relays, and in that list are a set of certificates from
952	952	each relay (self-signed by their identity key) specifying their keys,
953	953	locations, exit policies, and so on. So unless the adversary can control
...	...	@@ -1034,7 +1034,7 @@ stop requiring that all Tor relays be able to connect to all Tor
1034	1034	relays) and of the directory (how to stop requiring that all Tor
1035	1035	users know about all Tor relays). Changes like this can have large
1036	1036	impact on potential and actual anonymity. See Section 5 of the <a
1037		-href="<svnsandbox>doc/design-paper/challenges.pdf">Challenges</a> paper
	1037	+href="<gitblob>doc/design-paper/challenges.pdf">Challenges</a> paper
1038	1038	for details. Again, UDP transport would help here.
1039	1039	</p>
1040	1040

...	...	@@ -147,9 +147,9 @@ service.
147	147	<p>
148	148	There are more detailed descriptions about the hidden service protocol than
149	149	this one. See the
150		-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">Tor design paper</a>
	150	+<a href="<gitblob>doc/design-paper/tor-design.pdf">Tor design paper</a>
151	151	for an in-depth design description and the
152		-<a href="<svnsandbox>doc/spec/rend-spec.txt">rendezvous specification</a>
	152	+<a href="<gitblob>doc/spec/rend-spec.txt">rendezvous specification</a>
153	153	for the message formats.
154	154	</p>
155	155

...	...	@@ -82,7 +82,7 @@ management, and general support. General package hacker for Windows, OS
82	82	X, and various linux distributions.</dd>
83	83	<dt>Karsten Loesing (Developer)</dt><dd> Worked during the 2007 Google
84	84	Summer of Code on <a
85		-href="<svnsandbox>doc/spec/proposals/114-distributed-storage.txt">distributing
	85	+href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">distributing
86	86	and securing the publishing and fetching of hidden service
87	87	descriptors</a>. Currently working on <a href="<page
88	88	projects/hidserv>">making hidden services faster and more

...	...	@@ -187,20 +187,20 @@ Skill Level: <i>High</i>
187	187	Likely Mentors: <i>Nick, Roger, Steven</i>
188	188	<br />
189	189	The Tor 0.2.1.x series makes <a
190		-href="<svnsandbox>doc/design-paper/blocking.html">significant
	190	+href="<gitblob>doc/design-paper/blocking.html">significant
191	191	improvements</a> in resisting national and organizational censorship.
192	192	But Tor still needs better mechanisms for some parts of its
193	193	anti-censorship design. For example, current Tors can only listen on a
194	194	single address/port combination at a time. There's
195		-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
	195	+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
196	196	proposal to address this limitation</a> and allow clients to connect
197	197	to any given Tor on multiple addresses and ports, but it needs more
198	198	work. Another anti-censorship project (far more difficult) is to try
199	199	to make Tor more scanning-resistant. Right now, an adversary can identify
200		-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
	200	+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
201	201	just by trying to connect to them, following the Tor protocol, and
202	202	seeing if they respond. To solve this, bridges could
203		-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
	203	+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
204	204	webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
205	205	and not act like bridges until the user provides a bridge-specific key.
206	206	<br />
...	...	@@ -560,9 +560,9 @@ and <a href="https://svn.torproject.org/svn/weather/trunk/TODO">TODO</a>.
560	560	<b>Bring up new ideas!</b>
561	561	<br />
562	562	Don't like any of these? Look at the <a
563		-href="<svnsandbox>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
	563	+href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
564	564	roadmap</a> for more ideas.
565		-Some of the <a href="<svnsandbox>doc/spec/proposals/">current proposals</a>
	565	+Some of the <a href="<gittree>doc/spec/proposals/">current proposals</a>
566	566	might also be short on developers.
567	567	</li>
568	568
...	...	@@ -572,7 +572,7 @@ might also be short on developers.
572	572	Vidalia currently doesn't play nicely on Debian and Ubuntu with the
573	573	default Tor packages. The current Tor packages automatically start Tor
574	574	as a daemon running as the debian-tor user and (sensibly) do not have a
575		-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
	575	+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
576	576	in the default torrc. Consequently, Vidalia will try
577	577	to start its own Tor process since it could not connect to the existing
578	578	Tor, and Vidalia's Tor process will then exit with an error message
...	...	@@ -737,7 +737,7 @@ it means we can only reasonably support TCP streams. We have a <a
737	737	href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list
738	738	of reasons why we haven't shifted to UDP transport</a>, but it would
739	739	be great to see that list get shorter. We also have a proposed <a
740		-href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
	740	+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
741	741	for Tor and
742	742	UDP</a> — please let us know what's wrong with it.</li>
743	743
...	...	@@ -850,7 +850,7 @@ throughput experiment</a>. We'll need to measure and tweak, and maybe
850	850	overhaul if the results are good.</li>
851	851	<li>Our censorship-resistance goals include preventing
852	852	an attacker who's looking at Tor traffic on the wire from <a
853		-href="<svnsandbox>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
	853	+href="<gitblob>doc/design-paper/blocking.html#sec:network-fingerprint">distinguishing
854	854	it from normal SSL traffic</a>. Obviously we can't achieve perfect
855	855	steganography and still remain usable, but for a first step we'd like to
856	856	block any attacks that can win by observing only a few packets. One of

...	...	@@ -180,7 +180,7 @@ Tor o en <tt>/var/lib/tor/fingerprint</tt> dependiendo de su plataforma).
180	180	<p>
181	181	Si desea aprender más acerca de nuestro diseño
182	182	de puentes desde un punto de vista técnico, lea las <a
183		-href="<svnsandbox>doc/spec/bridges-spec.txt">Especificaciones de puentes
	183	+href="<gitblob>doc/spec/bridges-spec.txt">Especificaciones de puentes
184	184	de Tor</a>. Si está interesado en la ejecución de un puente no publicado
185	185	o en otros usos no estándar, lea la especificación.
186	186	</p>

...	...	@@ -83,12 +83,12 @@ es únicamente para desarrolladores y tiene muy poco tráfico.</li>
83	83	<li>El <b>documento de diseño</b> (publicado en Usenix Security 2004)
84	84	da nuestras justificaciones y análisis de seguridad para el diseño de Tor:
85	85	versiones disponibles
86		-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> y
87		-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
	86	+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> y
	87	+<a href="<gitblob>doc/design-paper/tor-design.html">HTML</a>
88	88	.</li>
89	89	<li>Nuestro documento de reafirmación en <b>desafíos en el anonimato de baja latencia</b>
90	90	(todavía en forma de borrador) detalla experiencias y direcciones mas recientes:
91		-<a href="<svnsandbox>doc/design-paper/challenges.pdf">versión PDF</a>.</li>
	91	+<a href="<gitblob>doc/design-paper/challenges.pdf">versión PDF</a>.</li>
92	92	<li>Nuestro artículo en WEIS 2006 — <b>Anonymity Loves Company:
93	93	Usability and the Network Effect (Al anonimato le encanta la compañía:
94	94	Usabilidad y el efecto en red)</b> — explica porqué la usabilidad
...	...	@@ -97,8 +97,8 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
97	97	<li>Nuestro diseño preliminar para hacer más difícil que cortafuegos grandes
98	98	eviten el acceso a la red Tor se describe en
99	99	<b>el diseño de un sistema de anonimato resistente al bloqueo</b>:
100		-<a href="<svnsandbox>doc/design-paper/blocking.pdf">borrador PDF</a> y
101		-<a href="<svnsandbox>doc/design-paper/blocking.html">borrador HTML</a>.
	100	+<a href="<gitblob>doc/design-paper/blocking.pdf">borrador PDF</a> y
	101	+<a href="<gitblob>doc/design-paper/blocking.html">borrador HTML</a>.
102	102	También puede ver <a
103	103	href="http://freehaven.net/~arma/slides-23c3.pdf">transparencias</a> y <a
104	104	href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">vídeo</a>
...	...	@@ -110,21 +110,21 @@ de Roger. ¿Quiere <a href="<page volunteer>#Coding">ayudarnos a construirla</a>
110	110	desarrolladores la suficiente información para construir una versión compatible de Tor:
111	111	<ul>
112	112
113		-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Especificación principal de Tor</a></li>
	113	+<li><a href="<gitblob>doc/spec/tor-spec.txt">Especificación principal de Tor</a></li>
114	114
115		-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">
	115	+<li><a href="<gitblob>doc/spec/dir-spec.txt">
116	116	Especificación para el servidor de directorio Tor versión 3</a>
117	117	(y las especificaciones de directorio más antiguas <a
118		-href="<svnsandbox>doc/spec/dir-spec-v1.txt">versión 1</a> y <a
119		-href="<svnsandbox>doc/spec/dir-spec-v2.txt">versión 2</a>)</li>
120		-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Especificación del protocolo de control de Tor</a></li>
121		-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Especificación de punto de encuentro de Tor</a></li>
122		-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Especificación para el servidor de directorio Tor</a></li>
123		-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Especificación de selección de camino de Tor</a></li>
124		-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Nombres de host especiales de Tor</a></li>
125		-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Soporte SOCKS de Tor y extensiones</a></li>
126		-<li><a href="<svnsandbox>doc/spec/version-spec.txt">Cómo funcionan los números de versión de Tor</a></li>
127		-<li><a href="<svnsandbox>doc/spec/proposals/">Borradores en progreso de nuevas especificaciones y cambios propuestos</a></li>
	118	+href="<gitblob>doc/spec/dir-spec-v1.txt">versión 1</a> y <a
	119	+href="<gitblob>doc/spec/dir-spec-v2.txt">versión 2</a>)</li>
	120	+<li><a href="<gitblob>doc/spec/control-spec.txt">Especificación del protocolo de control de Tor</a></li>
	121	+<li><a href="<gitblob>doc/spec/rend-spec.txt">Especificación de punto de encuentro de Tor</a></li>
	122	+<li><a href="<gitblob>doc/spec/dir-spec.txt">Especificación para el servidor de directorio Tor</a></li>
	123	+<li><a href="<gitblob>doc/spec/path-spec.txt">Especificación de selección de camino de Tor</a></li>
	124	+<li><a href="<gitblob>doc/spec/address-spec.txt">Nombres de host especiales de Tor</a></li>
	125	+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Soporte SOCKS de Tor y extensiones</a></li>
	126	+<li><a href="<gitblob>doc/spec/version-spec.txt">Cómo funcionan los números de versión de Tor</a></li>
	127	+<li><a href="<gittree>doc/spec/proposals/">Borradores en progreso de nuevas especificaciones y cambios propuestos</a></li>
128	128	</ul></li>
129	129	<li>Mira las <a href="http://freehaven.net/~arma/wth1.pdf">transparencias
130	130	(PDF)</a> y <a
...	...	@@ -165,7 +165,7 @@ sistemas anónimos de comunicación.</li>
165	165	<h2><a class="anchor" href="#Developers">Para desarrolladores</a></h2>
166	166	Hojea el <b>repositorio de fuentes</b> de Tor: (que podría no funcionar ni tan siquiera compilar)
167	167	<ul>
168		-<li><a href="<svnsandbox>">SVN sandbox actualizado periódicamente </a></li>
	168	+<li><a href="<gittree>">SVN sandbox actualizado periódicamente </a></li>
169	169	<li><a href="https://tor-svn.freehaven.net/svn/tor/trunk">Hojee el repositorio directamente</a></li>
170	170	<li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/?root=Tor">VistaCVS</a></li>
171	171	<li>acceso anónimo a <a href="http://subversion.tigris.org/">subversion</a>:</li>

...	...	@@ -223,7 +223,7 @@ incluyendo snapshots de desarrollo</a></li>
223	223
224	224	<ul>
225	225	<li>Tor se distribuye como <a href="http://www.fsf.org/">Software Libre</a>
226		-bajo la <a href="<svnsandbox>LICENSE">licencia BSD de tres cláusulas</a>.
	226	+bajo la <a href="<gitblob>LICENSE">licencia BSD de tres cláusulas</a>.
227	227	</li>
228	228	<li>Si quieres que Tor sea más rápido y usable, por favor considera <a
229	229	href="<page donate>">hacer una donacion al proyecto Tor</a>.

tor-webwml.git

...	...	@@ -122,7 +122,7 @@
122	122	</p>
123	123	<p>
124	124	Tor se distribuye como <a href="http://www.fsf.org/">Software Libre</a>
125		-bajo la <a href="<svnsandbox>LICENSE">licencia BSD de tres cláusulas</a>.
	125	+bajo la <a href="<gitblob>LICENSE">licencia BSD de tres cláusulas</a>.
126	126	Los paquetes también incluyen <a href="<page vidalia/index>">Vidalia</a>
127	127	y <a href="http://www.privoxy.org/">Privoxy</a>, que son aplicaciones de soporte
128	128	distribuídas bajo la GNU GPL.
...	...	@@ -360,9 +360,9 @@ href="<page mirrors>">lista de sitios mirror del sitio Tor</a>.
360	360	<a id="Testing"></a>
361	361	<p>
362	362	Para una lista de qué ha cambiado en cada versión estable de Tor,
363		-véa las <a href="<svnsandbox>ReleaseNotes">ReleaseNotes</a>. Para una lista de
	363	+véa las <a href="<gitblob>ReleaseNotes">ReleaseNotes</a>. Para una lista de
364	364	cambios tanto de la versión estable como la de desarrollo, vea el
365		-<a href="<svnsandbox>ChangeLog">ChangeLog</a>.
	365	+<a href="<gitblob>ChangeLog">ChangeLog</a>.
366	366	</p>
367	367
368	368	</div><!-- #main -->

...	...	@@ -295,7 +295,7 @@ en mente que las políticas de salida pueden cambiar (y también la
295	295	lista de nodos completa de la red). </p>
296	296
297	297	<p>Si realmente quiere hacer esto, damos un
298		-<a href="<svnsandbox>contrib/exitlist">script Python para leer el directorio
	298	+<a href="<gitblob>contrib/exitlist">script Python para leer el directorio
299	299	Tor</a>. Note que este script no le dará una lista perfecta de direcciones
300	300	IP que puedan conectarse a usted usando Tor, ya que algunos servidores Tor
301	301	pueden salir desde otras direcciones aparte de la que publican.

...	...	@@ -130,7 +130,7 @@ El interfaz DNSBL recibirá probablemente cientos de peticiones por minuto,
130	130	así que se necesitan algoritmos inteligentes. Puntos de bonus si hace testing
131	131	activo a cada nodo de salida para averigura de qué direcciones IP está
132	132	realmente saliendo.
133		-<a href="<svnsandbox>doc/contrib/torel-design.txt">Lea más aquí</a>.</li>
	133	+<a href="<gitblob>doc/contrib/torel-design.txt">Lea más aquí</a>.</li>
134	134	<li>Algunas veces los repetidores Tor se cuelgan, o a los ordenadores en los
135	135	que están se les cae la red, u otros accidentes pasan. Algunos operadores Tor
136	136	han expresado un interes en inscribirse en un servidio "de notificación"
...	...	@@ -225,13 +225,13 @@ permitir flujos TCP. Tenemos una <a
225	225	href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">lista
226	226	de razones por las que no hemos cambiado a transporte UDP</a>, pero sería excelente
227	227	ver que esa lista se hace maś corta. También tenemos una propuesta de <a
228		-href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">especificación
	228	+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">especificación
229	229	para Tor y UDP</a> — por favor díganos qué problemas tiene.</li>
230	230	<li>No estamos tan lejos de tener soporte IPv6 para las direcciones
231	231	de destino (en los nodos de salida). Si le importa mucho IPv6, ése es
232	232	probablemente el primer sitio para empezar.</li>
233	233	<li>¿No le gusta ninguna de éstas? Mire el <a
234		-href="<svnsandbox>doc/design-paper/roadmap-2007.pdf">plan de desarrollo Tor</a>
	234	+href="<gitblob>doc/design-paper/roadmap-2007.pdf">plan de desarrollo Tor</a>
235	235	para más ideas.</li>
236	236	<li>¿No ve su idea aquí? ¡Probablemente la necesitemos de todas formas!
237	237	Contáctenos y averígüelo.</li>

...	...	@@ -119,7 +119,7 @@ how Tor is built.
119	119
120	120	<li>
121	121	There's a skeletal <a
122		-href="<svnsandbox>doc/design-paper/roadmap-future.pdf">list of items
	122	+href="<gitblob>doc/design-paper/roadmap-future.pdf">list of items
123	123	we'd like to tackle in the future</a>. Alas, many of those items need
124	124	to be fleshed out more before they'll make sense to people who aren't
125	125	Tor developers, but you can still get a general sense of what issues
...	...	@@ -136,7 +136,7 @@ and circumvention" talk from 23C3 in December 2006 (<a
136	136	href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
137	137	<a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
138	138	<a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
139		-<a href="<svnsandbox>doc/design-paper/blocking.html">design paper</a>),
	139	+<a href="<gitblob>doc/design-paper/blocking.html">design paper</a>),
140	140	and Roger's "Current events in 2007" talk from 24C3 in December
141	141	2007 (<a
142	142	href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
...	...	@@ -149,13 +149,13 @@ href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">video</a>,
149	149
150	150	<li>
151	151	Learn about the <a
152		-href="<svnsandbox>doc/spec/proposals/001-process.txt">Tor
	152	+href="<gitblob>doc/spec/proposals/001-process.txt">Tor
153	153	proposal process for changing our design</a>, and look over the <a
154		-href="<svnsandbox>doc/spec/proposals/">existing proposals</a>.
	154	+href="<gittree>doc/spec/proposals/">existing proposals</a>.
155	155	</li>
156	156
157	157	<li>
158		-Our <a href="<svnsandbox>doc/TODO">developer TODO file</a> starts with a
	158	+Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a
159	159	timeline for external promises — things <a href="<page sponsors>">our
160	160	sponsors</a> have paid to see done. It also lists many other tasks
161	161	and topics we'd like to tackle next.
...	...	@@ -175,12 +175,12 @@ is where the less complex discussion happens.
175	175	<ul>
176	176	<li>The <b>design document</b> (published at Usenix Security 2004)
177	177	gives our justifications and security analysis for the Tor design:
178		-<a href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> and
179		-<a href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>
	178	+<a href="<gitblob>doc/design-paper/tor-design.pdf">PDF</a> and
	179	+<a href="<gitblob>doc/design-paper/tor-design.html">HTML</a>
180	180	versions available.</li>
181	181	<li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
182	182	(still in draft form) details more recent experiences and directions:
183		-<a href="<svnsandbox>doc/design-paper/challenges.pdf">PDF
	183	+<a href="<gitblob>doc/design-paper/challenges.pdf">PDF
184	184	draft</a>.</li>
185	185	<li>Our paper at WEIS 2006 — <b>Anonymity Loves Company:
186	186	Usability and the Network Effect</b> — explains why usability in
...	...	@@ -189,32 +189,32 @@ href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
189	189	<li>Our preliminary design to make it harder for large firewalls to
190	190	prevent access to the Tor network is described in
191	191	<b>design of a blocking-resistant anonymity system</b>:
192		-<a href="<svnsandbox>doc/design-paper/blocking.pdf">PDF draft</a> and
193		-<a href="<svnsandbox>doc/design-paper/blocking.html">HTML draft</a>.
	192	+<a href="<gitblob>doc/design-paper/blocking.pdf">PDF draft</a> and
	193	+<a href="<gitblob>doc/design-paper/blocking.html">HTML draft</a>.
194	194	Want to <a href="<page volunteer>#Coding">help us build it</a>?</li>
195	195	<li>The <b>specifications</b> aim to give
196	196	developers enough information to build a compatible version of Tor:
197	197	<ul>
198		-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Main Tor
	198	+<li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor
199	199	specification</a></li>
200		-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Tor
	200	+<li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
201	201	version 3 directory server specification</a> (and older <a
202		-href="<svnsandbox>doc/spec/dir-spec-v1.txt">version 1</a> and <a
203		-href="<svnsandbox>doc/spec/dir-spec-v2.txt">version 2</a> directory
	202	+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> and <a
	203	+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> directory
204	204	specifications)</li>
205		-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Tor control protocol
	205	+<li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
206	206	specification</a></li>
207		-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Tor rendezvous
	207	+<li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous
208	208	specification</a></li>
209		-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Tor path selection
	209	+<li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
210	210	specification</a></li>
211		-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Special hostnames in
	211	+<li><a href="<gitblob>doc/spec/address-spec.txt">Special hostnames in
212	212	Tor</a></li>
213		-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS support
	213	+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support
214	214	and extensions</a></li>
215		-<li><a href="<svnsandbox>doc/spec/version-spec.txt">How Tor version numbers
	215	+<li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version numbers
216	216	work</a></li>
217		-<li><a href="<svnsandbox>doc/spec/proposals/">In-progress drafts of
	217	+<li><a href="<gittree>doc/spec/proposals/">In-progress drafts of
218	218	new specifications and proposed changes</a></li>
219	219	</ul></li>
220	220
...	...	@@ -250,7 +250,7 @@ of anonymous communication systems.</li>
250	250	<h2><a class="anchor" href="#Developers">Kehittäjille</a></h2>
251	251	Browse the Tor <b>source repository</b>: (which may not necessarily work or even compile)
252	252	<ul>
253		- <li><a href="<svnsandbox>">Regularly updated SVN sandbox</a></li>
	253	+ <li><a href="<gittree>">Regularly updated SVN sandbox</a></li>
254	254	<li><a href="https://svn.torproject.org/svn/tor/trunk">Browse the repository's source tree directly</a></li>
255	255	<li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/tor/?root=Tor">ViewCVS</a></li>
256	256	<li>anonymous <a href="http://subversion.tigris.org/">subversion</a> access:

...	...	@@ -207,7 +207,7 @@ Mitä <a href="#packagediff">eroja on vakaalla & epävakaalla</a>?
207	207	</p>
208	208
209	209	<p>Toria levitetään <a href="http://www.fsf.org/">vapaana ohjelmistona</a>
210		-<a href="<svnsandbox>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.</li> The
	210	+<a href="<gitblob>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.</li> The
211	211	bundles also include <a href="<page vidalia/index>">Vidalia</a>
212	212	and <a href="http://www.privoxy.org/">Privoxy</a>, which are supporting
213	213	applications distributed under the GNU GPL.
...	...	@@ -342,8 +342,8 @@ href="<page mirrors>">on lista palvelimista, jotka ovat kopioita Tor-sivustosta<
342	342	<a id="Testing"></a>
343	343	<p>
344	344	Vakaan Tor-julkaisun muutoksia voi lukea englanninkielellä tiedostosta
345		-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä tiedostosta
346		-<a href="<svnsandbox>ChangeLog">ChangeLog / Muutosloki</a>.
	345	+<a href="<gitblob>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä tiedostosta
	346	+<a href="<gitblob>ChangeLog">ChangeLog / Muutosloki</a>.
347	347	</p>
348	348
349	349	</div><!-- #main -->

...	...	@@ -121,7 +121,7 @@ Mitä <a href="#packagediff">eroja on vakaalla & epävakaalla</a>?
121	121	</p>
122	122
123	123	<p>Toria levitetään <a href="http://www.fsf.org/">vapaana ohjelmistona</a>
124		-<a href="<svnsandbox>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.The
	124	+<a href="<gitblob>LICENSE">kolmiehtoisen BSD-lisenssin</a> alaisena.The
125	125	bundles also include <a href="<page vidalia/index>">Vidalia</a>
126	126	and <a href="http://www.privoxy.org/">Privoxy</a>, which are supporting
127	127	applications distributed under the GNU GPL.
...	...	@@ -359,8 +359,8 @@ href="<page mirrors>">on lista palvelimista, jotka ovat kopioita Tor-sivustosta<
359	359	<a id="Testing"></a>
360	360	<p>
361	361	Vakaan Tor-julkaisun muutoksia voi lukea englanninkielellä tiedostosta
362		-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä tiedostosta
363		-<a href="<svnsandbox>ChangeLog">ChangeLog / Muutosloki</a>.
	362	+<a href="<gitblob>ReleaseNotes">ReleaseNotes / Julkaisutiedot</a>. Muutokset sekä vakaissa ja kehitysversioissa voi lukea englanninkielellä tiedostosta
	363	+<a href="<gitblob>ChangeLog">ChangeLog / Muutosloki</a>.
364	364	</p>
365	365
366	366	</div><!-- #main -->

...	...	@@ -105,7 +105,7 @@ with how useful it would be to the overall Tor project
105	105	clue you should start with (skill level), and which of our <a href="<page
106	106	people>#Core">core developers</a> would be good mentors. There are plenty
107	107	of other good ideas to work on too — see for example the <a
108		-href="<svnsandbox>doc/spec/proposals/">current proposals</a> list, or
	108	+href="<gittree>doc/spec/proposals/">current proposals</a> list, or
109	109	just make up your own ideas.
110	110	</p>
111	111
...	...	@@ -125,7 +125,7 @@ Likely Mentors: <i>Mike</i>
125	125	Applications as of 1 Apr 00:00 UTC: <i>5</i>
126	126	<br />
127	127	The Tor exit node scanner 'SoaT', part of the <a
128		-href="<svnsandbox>torflow/">Torflow project</a>, makes connections out
	128	+href="<gittree>torflow/">Torflow project</a>, makes connections out
129	129	of each Tor exit node and compares the content it gets back with what it
130	130	"should" get back. The goal is to notice misconfigured, broken, and even
131	131	malicious exit relays. Alas, the code is
...	...	@@ -301,7 +301,7 @@ Applications as of 1 Apr 00:00 UTC: <i>1</i>
301	301	Vidalia currently doesn't play nicely on Debian and Ubuntu with the
302	302	default Tor packages. The current Tor packages automatically start Tor
303	303	as a daemon running as the debian-tor user and (sensibly) do not have a
304		-<a href="<svnsandbox>doc/spec/control-spec.txt">ControlPort</a> defined
	304	+<a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a> defined
305	305	in the default torrc. Consequently, Vidalia will try
306	306	to start its own Tor process since it could not connect to the existing
307	307	Tor, and Vidalia's Tor process will then exit with an error message
...	...	@@ -351,20 +351,20 @@ Skill Level: <i>High</i>
351	351	Likely Mentors: <i>Nick</i>
352	352	<br />
353	353	The Tor 0.2.0.x series makes <a
354		-href="<svnsandbox>doc/design-paper/blocking.html">significant
	354	+href="<gitblob>doc/design-paper/blocking.html">significant
355	355	improvements</a> in resisting national and organizational censorship.
356	356	But Tor still needs better mechanisms for some parts of its
357	357	anti-censorship design. For example, current Tors can only listen on a
358	358	single address/port combination at a time. There's
359		-<a href="<svnsandbox>doc/spec/proposals/118-multiple-orports.txt">a
	359	+<a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
360	360	proposal to address this limitation</a> and allow clients to connect
361	361	to any given Tor on multiple addresses and ports, but it needs more
362	362	work. Another anti-censorship project (far more difficult) is to try
363	363	to make Tor more scanning-resistant. Right now, an adversary can identify
364		-<a href="<svnsandbox>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
	364	+<a href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
365	365	just by trying to connect to them, following the Tor protocol, and
366	366	seeing if they respond. To solve this, bridges could
367		-<a href="<svnsandbox>doc/design-paper/blocking.html#tth_sEc9.3">act like
	367	+<a href="<gitblob>doc/design-paper/blocking.html#tth_sEc9.3">act like
368	368	webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
369	369	and not act like bridges until the user provides a bridge-specific key.
370	370	<br />
...	...	@@ -522,7 +522,7 @@ to interact minimally with Tor to test their code.
522	522	<br />
523	523	If you want to make the project more exciting
524	524	and involve more design and coding, take a look at <a
525		-href="<svnsandbox>doc/spec/proposals/131-verify-tor-usage.txt">proposal
	525	+href="<gitblob>doc/spec/proposals/131-verify-tor-usage.txt">proposal
526	526	131-verify-tor-usage.txt</a>.
527	527	</li>
528	528
...	...	@@ -727,7 +727,7 @@ project</a>, and make it run on <a
727	727	href="http://code.google.com/android/">Android</a>. The first step
728	728	would be to port the existing code and execute it in an Android
729	729	environment. Next, the code should be updated to support the newer Tor
730		-protocol versions like the <a href="<svnsandbox>doc/spec/dir-spec.txt">v3
	730	+protocol versions like the <a href="<gitblob>doc/spec/dir-spec.txt">v3
731	731	directory protocol</a>. Further, support for requesting or even
732	732	providing Tor hidden services would be neat, but not required.
733	733	<br />
...	...	@@ -959,7 +959,7 @@ the core of the Blossom effort.
959	959	<b>Bring up new ideas!</b>
960	960	<br />
961	961	Don't like any of these? Look at the <a
962		-href="<svnsandbox>doc/design-paper/roadmap-future.pdf">Tor development
	962	+href="<gitblob>doc/design-paper/roadmap-future.pdf">Tor development
963	963	roadmap</a> for more ideas.
964	964	</li>
965	965
...	...	@@ -1007,7 +1007,7 @@ it means we can only reasonably support TCP streams. We have a <a
1007	1007	href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#TransportIPnotTCP">list
1008	1008	of reasons why we haven't shifted to UDP transport</a>, but it would
1009	1009	be great to see that list get shorter. We also have a proposed <a
1010		-href="<svnsandbox>doc/spec/proposals/100-tor-spec-udp.txt">specification
	1010	+href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
1011	1011	for Tor and
1012	1012	UDP</a> — please let us know what's wrong with it.</li>
1013	1013	<li>We're not that far from having IPv6 support for destination addresses

...	...	@@ -148,7 +148,7 @@ fonction de votre plateforme).
148	148	<p>
149	149	Si vous voulez en savoir plus sur le design des passerelles d'un point de vue plus technique,
150	150	voyez les <a
151		-href="<svnsandbox>doc/spec/bridges-spec.txt">Spécifications
	151	+href="<gitblob>doc/spec/bridges-spec.txt">Spécifications
152	152	de passerelles Tor</a>. Si vous avez envie de faire tourner une passerelle non publié ou d'avoir
153	153	d'autres utilisations non standards, voyez les spécifications.
154	154	</p>

...	...	@@ -96,7 +96,7 @@ comment Tor est conçu.
96	96
97	97	<li>
98	98	Il y a une liste squelettique d'<a
99		-href="<svnsandbox>doc/design-paper/2008-12-19-roadmap-full.pdf">éléments que nous
	99	+href="<gitblob>doc/design-paper/2008-12-19-roadmap-full.pdf">éléments que nous
100	100	souhaiterions aborder dans le futur</a>. Hélas, beaucoup de ces points devraient
101	101	être approfondis avant qu'ils puissent avoir un sens pour des nons
102	102	dévelopeurs Tor, mais vous pouvez tout de même avoir une idée des questions à
...	...	@@ -113,7 +113,7 @@ et contournement » d'une présentation de Roger au 23C3 en décembre 2006 (<a
113	113	href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">vidéo</a>,
114	114	<a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
115	115	<a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">résumé</a>,
116		-<a href="<svnsandbox>doc/design-paper/blocking.html">document d'architecture</a>),
	116	+<a href="<gitblob>doc/design-paper/blocking.html">document d'architecture</a>),
117	117	et la présentation des « Évènements courant en 2007 » de Roger au 24C3 en décembre
118	118	2007 (<a
119	119	href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">vidéo</a>,
...	...	@@ -135,13 +135,13 @@ href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>.
135	135
136	136	<li>
137	137	Étudiez les <a
138		-href="<svnsandbox>doc/spec/proposals/001-process.txt">propositions
	138	+href="<gitblob>doc/spec/proposals/001-process.txt">propositions
139	139	pour modifier notre conception</a>, et regardez les <a
140		-href="<svnsandbox>doc/spec/proposals/">propositions existantes</a>.
	140	+href="<gittree>doc/spec/proposals/">propositions existantes</a>.
141	141	</li>
142	142
143	143	<li>
144		-Notre <a href="<svnsandbox>doc/TODO">fichier de développeur TODO</a> commence par
	144	+Notre <a href="<gitblob>doc/TODO">fichier de développeur TODO</a> commence par
145	145	un calendrier de promesses — choses que <a href="<page sponsors>">nos
146	146	sponsors</a> ont payé pour voir achevées. Elle liste également d'autres tâches
147	147	et thèmes que nous aimerions attaquer prochainement.
...	...	@@ -191,24 +191,24 @@ De l'utilisation et de son effet sur le réseau</b> —
191	191	explique en quoi l'utilisation des systèmes anonymes est importante pour leur sécurité <a
192	192	href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
193	193	<li>Notre architecture préliminaire visant à rendre plus difficile le blocage des firewalls pour l'accès au réseau Tor est décrit sur <b>Architecture d'un système résistant au blocage</b> :
194		-<a href="<svnsandbox>doc/design-paper/blocking.pdf">ébauche PDF</a> et
195		-<a href="<svnsandbox>doc/design-paper/blocking.html">l'ébauche HTML</a>.
	194	+<a href="<gitblob>doc/design-paper/blocking.pdf">ébauche PDF</a> et
	195	+<a href="<gitblob>doc/design-paper/blocking.html">l'ébauche HTML</a>.
196	196	Vous êtes intéressé pour nous <a href="<page volunteer>#Coding">aider à le coder</a> ?</li>
197	197	<li>Les <b>spécifications</b> visent à donner aux développeurs suffisamment d'informations
198	198	pour créer une version compatible de Tor :
199	199	<ul>
200		-<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Spécifications principales de Tor </a></li>
201		-<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Version 3 des spécifications de serveur d'annuaire</a> (anciennement les <a
202		-href="<svnsandbox>doc/spec/dir-spec-v1.txt">version 1</a> et <a
203		-href="<svnsandbox>doc/spec/dir-spec-v2.txt">version 2</a> des spécifications d'annuaire)</li>
204		-<li><a href="<svnsandbox>doc/spec/control-spec.txt">Spécification de l'interface graphique
	200	+<li><a href="<gitblob>doc/spec/tor-spec.txt">Spécifications principales de Tor </a></li>
	201	+<li><a href="<gitblob>doc/spec/dir-spec.txt">Version 3 des spécifications de serveur d'annuaire</a> (anciennement les <a
	202	+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> et <a
	203	+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> des spécifications d'annuaire)</li>
	204	+<li><a href="<gitblob>doc/spec/control-spec.txt">Spécification de l'interface graphique
205	205	de contrôle de Tor</a></li>
206		-<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Spécification du Tor « rendezvous »</a></li>
207		-<li><a href="<svnsandbox>doc/spec/path-spec.txt">Spécification de la sélection de chemin de Tor</a></li>
208		-<li><a href="<svnsandbox>doc/spec/address-spec.txt">Noms spéciaux de machines dans Tor</a></li>
209		-<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Tor's SOCKS support and extensions</a></li>
210		-<li><a href="<svnsandbox>doc/spec/version-spec.txt">Comment sont numérotés les versions de Tor</a></li>
211		-<li><a href="<svnsandbox>doc/spec/proposals/">Travail en cours sur les nouvelles spécifications et les changements proposés</a></li>
	206	+<li><a href="<gitblob>doc/spec/rend-spec.txt">Spécification du Tor « rendezvous »</a></li>
	207	+<li><a href="<gitblob>doc/spec/path-spec.txt">Spécification de la sélection de chemin de Tor</a></li>
	208	+<li><a href="<gitblob>doc/spec/address-spec.txt">Noms spéciaux de machines dans Tor</a></li>
	209	+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support and extensions</a></li>
	210	+<li><a href="<gitblob>doc/spec/version-spec.txt">Comment sont numérotés les versions de Tor</a></li>
	211	+<li><a href="<gittree>doc/spec/proposals/">Travail en cours sur les nouvelles spécifications et les changements proposés</a></li>
212	212	</ul></li>
213	213	</ul>
214	214
...	...	@@ -238,7 +238,7 @@ communications anonymes.</li>
238	238	<h2><a class="anchor" href="#Developers">Pour les développeurs</a></h2>
239	239	Parcourez le <b>dépôt SVN</b> :
240	240	<ul>
241		- <li><a href="<svnsandbox>">Parcourir le répertoire du dépôt SVN directement</a></li>
	241	+ <li><a href="<gittree>">Parcourir le répertoire du dépôt SVN directement</a></li>
242	242	<li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/?root=Tor">Voir le CVS</a></li>
243	243	<li>Accès Lecture-Seule :
244	244	<ul>

...	...	@@ -226,7 +226,7 @@ Quel est la <a href="#packagediff">différence entre Stable & Non-stable</a>
226	226
227	227	<p>
228	228	Tor est distribué en tant que <a href="http://www.fsf.org/">Logiciel Libre</a>
229		-sous la <a href="<svnsandbox>LICENSE">licence 3-clause BSD</a>. Le
	229	+sous la <a href="<gitblob>LICENSE">licence 3-clause BSD</a>. Le
230	230	« tout en un » apporte également <a href="<page vidalia/index>">Vidalia</a>
231	231	et <a href="http://www.privoxy.org/">Privoxy</a>, qui sont des applications
232	232	contributives distribuées sous licence GNU GPL.
...	...	@@ -362,9 +362,9 @@ href="<page mirrors>">liste de sites miroir du site Tor</a>.
362	362	<a id="Testing"></a>
363	363	<p>
364	364	Pour une liste de ce qui a changé dans chaque version stable de Tor, voyez les
365		-<a href="<svnsandbox>ReleaseNotes">ReleaseNotes (ndt : notes de version)</a>. Pour une liste des
	365	+<a href="<gitblob>ReleaseNotes">ReleaseNotes (ndt : notes de version)</a>. Pour une liste des
366	366	changements à la fois dans les versions stable et développement, voyez le
367		-<a href="<svnsandbox>ChangeLog">ChangeLog (ntd : trace de changement)</a>.
	367	+<a href="<gitblob>ChangeLog">ChangeLog (ntd : trace de changement)</a>.
368	368	</p>
369	369
370	370	</div><!-- #main -->