[or-cvs] r24212: {website} Use HTTPS when possible on the volunteer page (website/trunk/getinvolved/en)

[Robert Ransom]

Author: rransom
Date: 2011-02-11 22:15:50 +0000 (Fri, 11 Feb 2011)
New Revision: 24212

Modified:
   website/trunk/getinvolved/en/volunteer.wml
Log:
Use HTTPS when possible on the volunteer page

Modified: website/trunk/getinvolved/en/volunteer.wml
===================================================================
--- website/trunk/getinvolved/en/volunteer.wml	2011-02-11 15:31:17 UTC (rev 24211)
+++ website/trunk/getinvolved/en/volunteer.wml	2011-02-11 22:15:50 UTC (rev 24212)
@@ -156,7 +156,7 @@
     But Tor still needs better mechanisms for some parts of its
     anti-censorship design.</p>
     <p>One huge category of work is adding features to our <a
-    href="http://gitweb.torproject.org/bridgedb.git?a=tree">BridgeDB</a>
+    href="https://gitweb.torproject.org/bridgedb.git?a=tree">BridgeDB</a>
     service (Python). Tor aims to give out <a href="<page docs/bridges>">bridge
     relay addresses</a> to users that can't reach the Tor network
     directly, but there's an arms race between algorithms for distributing
@@ -490,7 +490,7 @@
     IRC clients, knows how to talk to IRC servers, and has an additional
     layer that requires the users to authenticate.  Some work on this has
     begun by other volunteers, see their progress at <a
-    href="http://github.com/anonirc/orc">http://github.com/anonirc/orc</a>.
+    href="https://github.com/anonirc/orc">https://github.com/anonirc/orc</a>.
     </p>
     </li>
     
@@ -505,8 +505,8 @@
     <br>
     Likely Mentors: <i>?</i>
     <p>
-    <a href="http://code.google.com/p/torsocks/">Torsocks</a> and <a
-    href="http://code.google.com/p/dsocks/">dsocks</a> are wrappers that will
+    <a href="https://code.google.com/p/torsocks/">Torsocks</a> and <a
+    href="https://code.google.com/p/dsocks/">dsocks</a> are wrappers that will
     run applications, intercept their outgoing network connections, and push
     those connections through Tor. The goal is to handle applications that
     don't support proxies (or don't supporting them well). To get it right,
@@ -617,7 +617,7 @@
     <p>Others are currently working on Tor clients for Java, Android, and Maemo
     environments.  The first step is to get a handle on the current state of
     the project in which you are interested in helping; <a
-    href="http://github.com/brl/JTor">Tor for Java</a>,
+    href="https://github.com/brl/JTor">Tor for Java</a>,
     <a href="https://svn.torproject.org/svn/projects/android/trunk/">Android/Orbot</a>,
      or <a href="<page docs/N900>">Tor for Maemo</a>. Check out the
     repository and familiarize yourself
@@ -684,7 +684,7 @@
     Tor if needed.</li>
     
     <li>Perform a security analysis of Tor with <a
-    href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determine
+    href="https://secure.wikimedia.org/wikipedia/en/wiki/Fuzz_testing">"fuzz"</a>. Determine
     if there are good fuzzing libraries out there for what we want. Win fame by
     getting credit when we put out a new release because of you!</li>