forked from I2P_Developers/i2p.www
Moved i2ptunnel and socks pages into docs/apis
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}i2ptunnel{% endblock %}
|
||||
{% block content %}Description of i2ptunnel and tunneling modes
|
||||
|
@@ -1,4 +1,4 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}SOCKS{% endblock %}
|
||||
{% block content %}
|
||||
<h2>SOCKS and SOCKS proxies</h2>
|
||||
@@ -10,7 +10,7 @@
|
||||
</p>
|
||||
<p>
|
||||
As it says on the
|
||||
<a href="faq.html#socks">FAQ</a>:
|
||||
<a href="{{ site_url('support/faq') }}#socks">FAQ</a>:
|
||||
<p>
|
||||
Many applications leak sensitive
|
||||
information that could identify you on the Internet. I2P only filters
|
||||
@@ -53,9 +53,9 @@ Outproxy selection by port number is stubbed out.
|
||||
<ul>
|
||||
<li>
|
||||
The notes for
|
||||
<a href="meeting81.html">Meeting 81</a>
|
||||
<a href="{{ url_for('meetings_show', id=81) }}">Meeting 81</a>
|
||||
and
|
||||
<a href="meeting82.html">Meeting 82</a>
|
||||
<a href="{{ url_for('meetings_show', id=82) }}">Meeting 82</a>
|
||||
in March 2004.
|
||||
<li>
|
||||
<a href="http://www.abenteuerland.at/onioncat/">Onioncat</a>
|
Reference in New Issue
Block a user