Updated links to Tor Project site to HTTPS

i2p2www/pages/site/comparison/tor.html

@@ -3,7 +3,7 @@
 {% block content %}
 
 <h2>Tor / Onion Routing</h2>
-<i><a href="http://www.torproject.org/">[Tor]</a> 
+<i><a href="https://www.torproject.org/">[Tor]</a> 
    <a href="http://www.onion-router.net">[Onion Routing]</a></i>
 <p>{% trans netdb=site_url('docs/how/network-database'), peerselection=site_url('docs/how/peer-selection') -%}
 Tor and Onion Routing are both anonymizing proxy networks, 

i2p2www/pages/site/docs/discussions/tunnel.html

@@ -165,7 +165,7 @@ vulnerability to predecessor attacks.  While the endpoints and gateways of
 those tunnels will be randomly distributed across the network (perhaps even 
 including the tunnel creator in that set), another alternative is to use the
 tunnel pathways themselves to pass along the request and response, as is done
-in <a href="http://www.torproject.org/">Tor</a>.  This, however, may lead to leaks 
+in <a href="https://www.torproject.org/">Tor</a>.  This, however, may lead to leaks 
 during tunnel creation, allowing peers to discover how many hops there are later
 on in the tunnel by monitoring the timing or <a
 href="http://dev.i2p.net/pipermail/2005-October/001057.html">packet count</a> as

i2p2www/pages/site/docs/how/tech-intro.html

@@ -681,7 +681,7 @@ See also the <a href="{{ comparisons }}">Network Comparisons Page</a>.
 {%- endtrans %}</p>
 
   <h2 id="similar.tor">Tor</h2>
-  <p><i><a href="http://www.torproject.org/">{% trans %}website{% endtrans %}</a></i></p>
+  <p><i><a href="https://www.torproject.org/">{% trans %}website{% endtrans %}</a></i></p>
 
   <p>{% trans -%}
 At first glance, Tor and I2P have many functional and anonymity related 

i2p2www/pages/site/docs/how/threat-model.html

@@ -80,7 +80,7 @@ the current implementation does not.
 I2P design started in 2003, not long after the advent of
 <a href="http://www.onion-router.net">[Onion Routing]</a>,
 <a href="http://freenetproject.org/">[Freenet]</a>, and
-<a href="http://www.torproject.org/">[Tor]</a>.
+<a href="https://www.torproject.org/">[Tor]</a>.
 Our design benefits substantially from the research published around that time.
 I2P uses several onion routing techniques, so we continue to benefit
 from the significant academic interest in Tor.

i2p2www/pages/site/docs/tunnels/old-implementation.html

@@ -492,7 +492,7 @@ vulnerability to predecessor attacks.  While the endpoints and gateways of
 those tunnels will be randomly distributed across the network (perhaps even 
 including the tunnel creator in that set), another alternative is to use the
 tunnel pathways themselves to pass along the request and response, as is done
-in <a href="http://www.torproject.org/">TOR</a>.  This, however, may lead to leaks 
+in <a href="https://www.torproject.org/">TOR</a>.  This, however, may lead to leaks 
 during tunnel creation, allowing peers to discover how many hops there are later
 on in the tunnel by monitoring the timing or packet count as the tunnel is
 built.  Techniques could be used to minimize this issue, such as using each of 

i2p2www/pages/site/faq.html

@@ -272,7 +272,7 @@ The best way to stay "better-connected" to the network is to <a href="http://loc
 <h3 id="exit">{% trans %}Is my router an "exit node" to the regular Internet? I don't want it to be.{% endtrans %}
 <span class="permalink">(<a href="#exit">{{ _('link') }}</a>)</span></h3>
 <p>{% trans -%}
-No. Unlike <a href="http://www.torproject.org/">Tor</a>,
+No. Unlike <a href="https://www.torproject.org/">Tor</a>,
 "exit nodes" or "outproxies" are not an inherent part of the network.
 Only volunteers who set up and run separate applications will relay traffic to the regular Internet.
 There are very, very few of these.
@@ -290,7 +290,7 @@ and set your outproxy list to 'false.i2p' (only).
 Then stop and restart the eepProxy.
 If it doesn't work, the outproxy is not up. It is not I2P's fault.
 If your primary reason to use an anonymous network is to anonymously access sites
-on the regular Internet, you should probably try <a href="http://www.torproject.org/">Tor</a>.
+on the regular Internet, you should probably try <a href="https://www.torproject.org/">Tor</a>.
 {%- endtrans %}</p>
 
 <h3 id="https">{% trans %}I can't access https:// or ftp:// sites through I2P.{% endtrans %}
@@ -368,7 +368,7 @@ There is additional discussion about this on <a href="http://{{ zzz }}/topics/21
 <p>{% trans -%}
 Unless an outproxy has been set up for the service you want to connect to, this cannot be done.
 There are only three types of outproxies running right now: HTTP, HTTPS, and email. Note that there is not a SOCKS outproxy.
-If this type of service is required, try <a href="http://www.torproject.org/">Tor</a>.
+If this type of service is required, try <a href="https://www.torproject.org/">Tor</a>.
 {%- endtrans %}</p>
 
 <h3 id="down">{% trans %}Most of the eepsites within I2P are down?{% endtrans %}

i2p2www/pages/site/links.html

@@ -20,7 +20,7 @@ See also the page with
 <li><a href="http://www.pegasusnk.org/">The Pegasus Project</a></li>
 <!--<li><a href="http://www.thepegasuspress.com/">The Pegasus Press</a></li>-->
 <li><a href="http://telecomix.org/">Telecomix</a></li>
-<li><a href="http://www.torproject.org/">Tor</a></li>
+<li><a href="https://www.torproject.org/">Tor</a></li>
 <h4>{{ _('More Projects and Documentation') }}</h4>
 <li><a href="http://freehaven.net/anonbib/topic.html">Freehaven's Anonymity Bibliography</a></li>
 <li><a href="https://gnunet.org/links">GNUNet's related projects</a></li>