Browse code

cgit version of blob_plain/HEAD:/ and blob/HEAD:/

Matt Pagan authored on10/12/2014 15:56:08 • Sebastian Hahn committed on11/12/2014 12:26:17
Showing13 changed files
... ...
@@ -284,7 +284,7 @@
284 284
           <dt>Mike Perry, Tor Browser and Tor Performance
285 285
           Developer</dt> <dd>Lead developer on Tor Browser, developer
286 286
           of <a href="<page docs/torbutton/index>">Torbutton</a>, author of <a
287
-          href="https://gitweb.torproject.org/torflow.git/blob/HEAD:/README">TorFlow</a>.
287
+          href="https://gitweb.torproject.org/torflow.git/tree/README">TorFlow</a>.
288 288
           Runs one of the directory authorities.</dd>
289 289
 
290 290
           <dt>Sina Rabbani, Advocate</dt>
... ...
@@ -80,7 +80,7 @@ and scramble to implement last-minute anticensorship schemes, or to
80 80
 deploy urgent security updates. You'd also be reviewing other people's
81 81
 code and designs, and looking for ways to improve it. For an idea of
82 82
 the breadth and depth of the work you'd be doing, have a look at <a
83
-href="https://gitweb.torproject.org/tor.git/blob/HEAD:/ChangeLog">the
83
+href="https://gitweb.torproject.org/tor.git/tree/ChangeLog">the
84 84
 ChangeLog file from the Tor source distribution</a>.
85 85
 </p>
86 86
 
... ...
@@ -83,7 +83,7 @@ transports</a> and their
83 83
 
84 84
 <li>
85 85
 Have run the
86
-<a href="https://gitweb.torproject.org/flashproxy.git/blob/HEAD:/README">sample
86
+<a href="https://gitweb.torproject.org/flashproxy.git/tree/README">sample
87 87
 commands in the README</a>, and made notes about the process. One of
88 88
 your early tasks will be to do such testing so that the packages you
89 89
 make will be effectively usable.
... ...
@@ -1659,7 +1659,7 @@ href="http://www.crowdstrike.com/community-tools/index.html#tool-79">proposed
1659 1659
     <h3><a class="anchor" href="#TBBSourceCode">Where is the source code for the bundle? How do I verify a build?</a></h3>
1660 1660
 
1661 1661
     <p>
1662
-    Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build</a>.
1662
+    Start with <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">https://gitweb.torproject.org/builders/tor-browser-bundle.git</a> and <a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build">https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build</a>.
1663 1663
     </p>
1664 1664
 
1665 1665
 
... ...
@@ -2384,7 +2384,7 @@ too.
2384 2384
     Linux-based Tor nodes have another option at their disposal: they can
2385 2385
     prioritize Tor traffic below other traffic on their machine, so that
2386 2386
     their own personal traffic is not impacted by Tor load. A <a
2387
-    href="https://gitweb.torproject.org/tor.git/blob/HEAD:/contrib/operator-tools/linux-tor-prio.sh">script
2387
+    href="https://gitweb.torproject.org/tor.git/tree/contrib/operator-tools/linux-tor-prio.sh">script
2388 2388
     to do this</a> can be found in the Tor source distribution's contrib
2389 2389
     directory.
2390 2390
     </p>
... ...
@@ -3291,7 +3291,7 @@ diversity,
3291 3291
     testing network with about 10 instances of Tor. Every instance of Tor
3292 3292
     binds to one or two ports on localhost (127.0.0.1) and all Tor
3293 3293
     communication is done over the loopback interface. The <a
3294
-    href="https://gitweb.torproject.org/chutney.git/blob/HEAD:/README">Chutney
3294
+    href="https://gitweb.torproject.org/chutney.git/tree/README">Chutney
3295 3295
     README</a> is a good starting point for getting it up and running.
3296 3296
     </p>
3297 3297
     <p>
... ...
@@ -3755,7 +3755,7 @@ destination, rather than just one chance.
3755 3755
     </p>
3756 3756
     <p>
3757 3757
 The actual content of these fixed size cells is
3758
-<a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/tor-spec.txt">
3758
+<a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">
3759 3759
 documented in the main Tor spec</a>, section 3.
3760 3760
     </p>
3761 3761
     <p>
... ...
@@ -28,7 +28,7 @@
28 28
     client and the bridge will see innocent-looking transformed traffic
29 29
     instead of the actual Tor traffic.
30 30
     External programs can talk to Tor clients and Tor bridges using the <a
31
-href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/pt-spec.txt">pluggable
31
+href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable
32 32
 transport API</a>, to make it easier to build interoperable programs.
33 33
     </p>
34 34
 
... ...
@@ -38,11 +38,11 @@ transport API</a>, to make it easier to build interoperable programs.
38 38
 
39 39
     <li><a href="<page projects/obfsproxy>"><b>Obfsproxy</b></a> is a Python framework for implementing new
40 40
     pluggable transports. It uses Twisted for its networking needs, and
41
-    <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/blob/HEAD:/README.rst">pyptlib</a>
41
+    <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/tree/README.rst">pyptlib</a>
42 42
     for some pluggable transport-related features. It supports the
43
-    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs2/obfs2-protocol-spec.txt">obfs2</a>
43
+    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs2/obfs2-protocol-spec.txt">obfs2</a>
44 44
     and
45
-    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
45
+    <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/obfs3/obfs3-protocol-spec.txt">obfs3</a>
46 46
     pluggable transports. Maintained by asn. <br>
47 47
     Status: <a href="#download">Deployed</a>
48 48
     </li>
... ...
@@ -87,7 +87,7 @@ transport API</a>, to make it easier to build interoperable programs.
87 87
     is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a>
88 88
     but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a>
89 89
     technique for public key obfuscation, and the
90
-    <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/216-ntor-handshake.txt">ntor protocol</a>
90
+    <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake.txt">ntor protocol</a>
91 91
     for one-way authentication. This results in a faster protocol. Written in Go.
92 92
     Maintained by Yawning Angel. <br>
93 93
     Status: <e>Coming soon</em>
... ...
@@ -81,7 +81,7 @@
81 81
     options are described in <a href="<page docs/faq>#LimitTotalBandwidth">these</a>
82 82
     <a href="<page docs/faq>#BandwidthShaping">FAQ entries</a>.</p>
83 83
 
84
-    <p>See the <a href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/src/config/torrc.sample.in">sample
84
+    <p>See the <a href="https://gitweb.torproject.org/tor.git/plain/src/config/torrc.sample.in">sample
85 85
     torrc file</a> and the <a
86 86
     href="<page docs/tor-manual>">man
87 87
     page</a> for other Tor options you may want to set.</p>
... ...
@@ -112,9 +112,9 @@
112 112
     <strong>Bug Reports:</strong> <a href="https://trac.torproject.org/projects/tor/report/14">Torproject Bug Tracker</a><br/>
113 113
     <strong>Documents:</strong> 
114 114
     <b>[</b> 
115
-    <a href="https://gitweb.torproject.org/torbutton.git/blob/HEAD:/src/CHANGELOG">changelog</a> <b>|</b>
116
-    <a href="https://gitweb.torproject.org/torbutton.git/blob/HEAD:/src/LICENSE">license</a> <b>|</b>
117
-    <a href="https://gitweb.torproject.org/torbutton.git/blob/HEAD:/src/CREDITS">credits</a> <b>]</b>
115
+    <a href="https://gitweb.torproject.org/torbutton.git/tree/src/CHANGELOG">changelog</a> <b>|</b>
116
+    <a href="https://gitweb.torproject.org/torbutton.git/tree/src/LICENSE">license</a> <b>|</b>
117
+    <a href="https://gitweb.torproject.org/torbutton.git/tree/src/CREDITS">credits</a> <b>]</b>
118 118
     
119 119
   </div>
120 120
   <!-- END MAINCOL -->
... ...
@@ -154,7 +154,7 @@ relay:</p>
154 154
 <li>Set up a reverse DNS name for the IP address that makes clear that
155 155
 the computer is an exit relay.</li>
156 156
 <li>Set up a notice like <a
157
-href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/operator-tools/tor-exit-notice.html">this</a>
157
+href="https://gitweb.torproject.org/tor.git/plain/contrib/operator-tools/tor-exit-notice.html">this</a>
158 158
 to explain that you're running an exit relay that's part of the Tor
159 159
 network.</li>
160 160
 <li>If possible, get an <a href="https://www.arin.net/">ARIN</a>
... ...
@@ -892,7 +892,7 @@ meetings around the world.</li>
892 892
       href="https://stem.torproject.org/tutorials.html">stem's tutorial
893 893
       page</a> demonstrating cross txtorcon/stem usage.</li>
894 894
       <li>Expand the txtorcon API to include functionality of <a
895
-      href="https://gitweb.torproject.org/stem.git/blob/HEAD:/stem/control.py">stem's
895
+      href="https://gitweb.torproject.org/stem.git/tree/stem/control.py">stem's
896 896
       controller</a> that would be of interest to twisted users. All additions
897 897
       should include tests!</li>
898 898
       <li>Come up with some ideas of your own! We'd love to discuss them with
... ...
@@ -43,7 +43,7 @@
43 43
     <p>
44 44
     Even though obfsproxy is a separate application, completely
45 45
     independent from tor, it speaks to tor using an <a
46
-    href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/pt-spec.txt">internal
46
+    href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">internal
47 47
     protocol</a> to minimize necessary end-user configuration.
48 48
     </p>
49 49
 
... ...
@@ -606,7 +606,7 @@
606 606
       document</a>, the <a
607 607
       href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/refs/heads/maint-3.6:/Bundle-Data/Docs/ChangeLog.txt">ChangeLog
608 608
       for the 3.6 branch</a>, and the <a
609
-      href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/Bundle-Data/Docs/ChangeLog.txt">ChangeLog
609
+      href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-Data/Docs/ChangeLog.txt">ChangeLog
610 610
       for the alpha branch</a>.
611 611
       </p>
612 612
       <p><strong><em>How can I make my own bundle?</em></strong>
... ...
@@ -616,7 +616,7 @@ to ensure that byte-for-byte reproducible packages can be built from our
616 616
 source repository by anyone. To rebuild the bundle, check out the <a
617 617
 href="https://gitweb.torproject.org/builders/tor-browser-bundle.git">Tor
618 618
 Browser builder repository</a> and see the <a
619
-href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build">README.build</a>
619
+href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/README.build">README.build</a>
620 620
 for instructions. You may also find the <a
621 621
 href="https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking">Tor
622 622
 Browser Hacking</a> intro document useful for learning about the build system
... ...
@@ -27,7 +27,7 @@
27 27
     accurate list.</p>
28 28
 
29 29
     <p>The full background and rationale for TorDNSEL is described in the official
30
-    <a href="https://gitweb.torproject.org/tordnsel.git/blob/HEAD:/doc/torel-design.txt">design
30
+    <a href="https://gitweb.torproject.org/tordnsel.git/tree/doc/torel-design.txt">design
31 31
     document</a>. The current service only supports the first query type mentioned
32 32
     in that document.</p>
33 33
 
... ...
@@ -97,7 +97,7 @@ href="/dist/vidalia/vidalia-<version-vidalia-alpha>.tar.gz.asc">sig</a>
97 97
 
98 98
     <p>
99 99
     If you intend to start coding already, please read and follow the
100
-    <a href="https://gitweb.torproject.org/vidalia.git/blob/HEAD:/HACKING">HACKING
100
+    <a href="https://gitweb.torproject.org/vidalia.git/tree/HACKING">HACKING
101 101
     guide</a>.
102 102
     If you have a patch for a feature or a bug fix, first check the
103 103
     <a href="https://trac.torproject.org/projects/tor/report/27">tickets that