propagate from branch 'i2p.www' (head 58b6b0589b4b5e4a45b1be2ac97bba8d253e9368)
to branch 'i2p.www.str4d' (head 2ab3bce2634e8d1dcbf7f2bf89c310c5ae3a7eb6)
This commit is contained in:
@@ -23,7 +23,7 @@ either protocol may be carried by either transport.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2>{% trans %}Application Guide{% endtrans %}</h2>
|
||||
<p>{% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/client/datagram/package-summary.html',
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/datagram/package-summary.html',
|
||||
sam= site_url('docs/api/sam'),
|
||||
socks=site_url('docs/api/socks') -%}
|
||||
Applications written in Java may use the
|
||||
@@ -70,7 +70,7 @@ Applications may add 'from' and 'to' ports to the I2CP (gzip) header as describe
|
||||
the <a href="{{ i2cp }}#format">I2CP page</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2psession='http://docs.i2p-projekt.de/javadoc/net/i2p/client/I2PSession.html' -%}
|
||||
<p>{% trans i2psession='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSession.html' -%}
|
||||
There is no method within the datagram API to specify whether it is non-repliable (raw)
|
||||
or repliable. The application should be designed to expect the appropriate type.
|
||||
The I2CP protocol number or port should be used by the application to
|
||||
@@ -82,8 +82,8 @@ use signed datagrams for a request which includes a nonce, and use a raw datagra
|
||||
for the reply, returning the nonce from the request.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2psession='http://docs.i2p-projekt.de/javadoc/net/i2p/client/I2PSession.html',
|
||||
i2psessionmuxed='http://docs.i2p-projekt.de/javadoc/net/i2p/client/I2PSessionMuxedImpl.html' -%}
|
||||
<p>{% trans i2psession='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSession.html',
|
||||
i2psessionmuxed='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSessionMuxedImpl.html' -%}
|
||||
The protocols and ports may be set in I2CP's
|
||||
<a href="{{ i2psession }}">I2PSession API</a>,
|
||||
as implemented in
|
||||
|
@@ -204,6 +204,19 @@ Parameters are only provided in a named way (maps).
|
||||
<li>RestartNeeded – [boolean] {% trans %}Is a restart needed for the new settings to be used.{% endtrans %}</li>
|
||||
</ul>
|
||||
</ul>
|
||||
<ul>AdvancedSettings – {% trans %}Allows for manipulation of advanced i2p settings{% endtrans %}
|
||||
<ul>{{ _('Set:') }} – {% trans %}Set the sent key-value pairs{% endtrans %}
|
||||
<li>{"setting-key": "setting-value", ...} – [Map<String, String>]</li>
|
||||
</ul>
|
||||
<ul>{{ _('SetAll:') }} – {% trans %}Set the sent key-value pairs, remove everything else{% endtrans %}
|
||||
<li>{"setting-key": "setting-value", ...} – [Map<String, String>]</li>
|
||||
</ul>
|
||||
<ul>{{ _('Get:') }} – {% trans %}Set the sent key-value pairs, remove everything else{% endtrans %}
|
||||
<li>"setting-key" – [String]</li>
|
||||
</ul>
|
||||
<ul>{{ _('GetAall:') }}
|
||||
</ul>
|
||||
</ul>
|
||||
<p>* {% trans %}denotes an optional value.{% endtrans %}</p>
|
||||
<p>** {% trans %}denotes a possibly occuring return value{% endtrans %}</p>
|
||||
|
||||
|
@@ -1,12 +1,8 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}I2PTunnel{% endblock %}
|
||||
{% block lastupdated %}January 2016{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block content %}
|
||||
<!--Description of i2ptunnel and tunneling modes
|
||||
|
||||
default services
|
||||
client modes
|
||||
server modes
|
||||
-->
|
||||
|
||||
<h2 id="overview">{% trans %}Overview{% endtrans %}</h2>
|
||||
<p>{% trans naming=site_url('docs/naming') -%}
|
||||
@@ -69,20 +65,28 @@ in a HTTP request. Supports proxying onto internet if an outproxy is provided. S
|
||||
{%- endtrans %}</p>
|
||||
<ul>
|
||||
<li>{% trans -%}
|
||||
<b>Accept, Accept-Charset, Accept-Encoding, Accept-Language
|
||||
<b>Accept, Accept-Charset, Accept-Language
|
||||
and Accept-Ranges</b> as they vary greatly between browsers and can be used as an identifier.
|
||||
{%- endtrans %}</li>
|
||||
<li><b>Referer:</b></li>
|
||||
<li><b>Via:</b></li>
|
||||
<li><b>From:</b></li>
|
||||
</ul>
|
||||
<p>{% trans -%}
|
||||
HTTP client/server tunnels are via I2Ptunnel force-enabling compression via the following http headers:
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>
|
||||
The i2ptunnel compression is requested with the HTTP header:
|
||||
</p>
|
||||
<ul>
|
||||
<li><b>Accept-Encoding: </b></li>
|
||||
<li><b>X-Accept-Encoding: </b> x-i2p-gzip;q=1.0, identity;q=0.5, deflate;q=0, gzip;q=0, *;q=0</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
The response indicating i2ptunnel compression contains the following HTTP header:
|
||||
</p>
|
||||
<ul>
|
||||
<li><b>Content-Encoding: </b> x-i2p-gzip</li>
|
||||
</ul>
|
||||
|
||||
<p>{% trans -%}
|
||||
Depending on if the tunnel is using an outproxy or not it will append the following User-Agent:
|
||||
{%- endtrans %}</p>
|
||||
@@ -92,23 +96,43 @@ Depending on if the tunnel is using an outproxy or not it will append the follow
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
<h3 id="client-mode-irc">IRC</h3>
|
||||
<h3 id="client-mode-irc">IRC Client</h3>
|
||||
<p>{% trans -%}
|
||||
Creates a connection to a random IRC server specified by the comma seprated (", ")
|
||||
list of destinations. Only a whitelisted subset of IRC commands are allowed due to anonymity concerns.
|
||||
{%- endtrans %}
|
||||
The following whitelist is for commands inbound from the IRC server to the IRC client.
|
||||
<br>{% trans %}Whitelist:{% endtrans %}</p>
|
||||
<ul>
|
||||
<li>MODE</li>
|
||||
<li>JOIN</li>
|
||||
<li>NICK</li>
|
||||
<li>QUIT</li>
|
||||
<li>PART</li>
|
||||
<li>WALLOPS</li>
|
||||
<li>AUTHENTICATE</li>
|
||||
<li>CAP</li>
|
||||
<li>ERROR</li>
|
||||
<li>KICK</li>
|
||||
<li>H</li>
|
||||
<li>JOIN</li>
|
||||
<li>KICK</li>
|
||||
<li>MODE</li>
|
||||
<li>NICK</li>
|
||||
<li>PART</li>
|
||||
<li>PING</li>
|
||||
<li>PROTOCTL</li>
|
||||
<li>QUIT</li>
|
||||
<li>TOPIC</li>
|
||||
<li>WALLOPS</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
There is also a whitelist is for commands outbound from the IRC client to the IRC server.
|
||||
It is quite large due to the number of IRC administrative commands.
|
||||
See the IRCFilter.java source for details.
|
||||
The outbound filter also modifies the following commands to strip identifying information:
|
||||
</p>
|
||||
<ul>
|
||||
<li>NOTICE</li>
|
||||
<li>PART</li>
|
||||
<li>PING</li>
|
||||
<li>PRIVMSG</li>
|
||||
<li>QUIT</li>
|
||||
<li>USER</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="client-mode-socks">SOCKS 4/4a/5</h3>
|
||||
@@ -156,7 +180,7 @@ capabilities. An example application would be a web application that does client
|
||||
requests, or loopback-testing an eepsite as a diagnostic tool.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h3 id="server-mode-irc">IRC</h3>
|
||||
<h3 id="server-mode-irc">IRC Server</h3>
|
||||
<p>{% trans -%}
|
||||
Creates a destination that filters the reqistration sequence of a client and passes
|
||||
the clients destination key as a hostname to the IRC-server.
|
||||
|
@@ -4,7 +4,7 @@
|
||||
|
||||
<h2>{% trans %}Note{% endtrans %}</h2>
|
||||
|
||||
<p>{% trans streaming=site_url('docs/api/streaming'), api='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/package-summary.html' -%}
|
||||
<p>{% trans streaming=site_url('docs/api/streaming'), api='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
The ministreaming library has been enhanced and extended by the
|
||||
"full" <a href="{{ streaming }}">streaming library</a>.
|
||||
Ministreaming is deprecated and is incompatible with today's applications.
|
||||
@@ -42,7 +42,7 @@ messages sent (or include any application level ACK or SACK), so it must wait
|
||||
on average twice the time it takes to send a message before sending another.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans api='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/package-summary.html',
|
||||
<p>{% trans api='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/package-summary.html',
|
||||
samv3=site_url('docs/api/samv3') -%}
|
||||
Even with those issues, the ministreaming library performs quite well in many
|
||||
situations, and its <a href="{{ api }}">API</a>
|
||||
|
@@ -389,7 +389,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
RESULT values
|
||||
|
@@ -446,7 +446,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
RESULT values
|
||||
|
File diff suppressed because it is too large
Load Diff
@@ -65,11 +65,11 @@ streaming library, to be interpreted by I2CP.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2cp=site_url('docs/protocol/i2cp'),
|
||||
i2psktmf='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocketManagerFactory.html',
|
||||
i2psktm='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocketManager.html',
|
||||
i2psess='http://docs.i2p-projekt.de/javadoc/net/i2p/client/I2PSession.html',
|
||||
i2pskt='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocket.html',
|
||||
i2psskt='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PServerSocket.html' -%}
|
||||
i2psktmf='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html',
|
||||
i2psktm='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocketManager.html',
|
||||
i2psess='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSession.html',
|
||||
i2pskt='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocket.html',
|
||||
i2psskt='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PServerSocket.html' -%}
|
||||
The standard interface to the streaming lib is for the application to use the
|
||||
<a href="{{ i2psktmf }}">I2PSocketManagerFactory</a> to create an
|
||||
<a href="{{ i2psktm }}">I2PSocketManager</a>. The application then asks the
|
||||
@@ -79,7 +79,7 @@ can then setup connections with an <a href="{{ i2pskt }}">I2PSocket</a> or
|
||||
receive connections with an <a href="{{ i2psskt }}">I2PServerSocket</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/package-summary.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
Here are the <a href="{{ url }}">full streaming library Javadocs</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
@@ -89,7 +89,7 @@ For a good example of usage, see the i2psnark code.
|
||||
|
||||
|
||||
<h3 id="options">{% trans %}Options and Defaults{% endtrans %}</h3>
|
||||
<p>{% trans i2psktmf='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocketManagerFactory.html' -%}
|
||||
<p>{% trans i2psktmf='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html' -%}
|
||||
The options and current default values are listed below.
|
||||
Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a
|
||||
per-connection basis.
|
||||
|
@@ -336,7 +336,7 @@ as is done in our Java packages.
|
||||
As always, state management is the difficult part.
|
||||
{%- endtrans %}</p>
|
||||
<p>
|
||||
See also: <a href="http://docs.i2p-projekt.de/javadoc/net/i2p/router/Router.html">the Router javadocs</a>.
|
||||
See also: <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/Router.html">the Router javadocs</a>.
|
||||
</p>
|
||||
|
||||
{% endblock %}
|
||||
|
@@ -1,10 +1,6 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Supported Applications{% endtrans %}{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<h1 class="title">{% trans %}Supported Applications{% endtrans %}</h1>
|
||||
|
||||
<div id="TOC">
|
||||
{% block content_nav %}
|
||||
<ul>
|
||||
<li><a href="#blogging-and-forums">{% trans %}Blogging, Forums, and Wikis{% endtrans %}</a></li>
|
||||
|
||||
@@ -80,8 +76,9 @@
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
||||
{% block content %}
|
||||
<p>{% trans trac='https://trac.i2p2.de/report/1' -%}
|
||||
This is intended to be a comprehensive listing of applications used with
|
||||
I2P. If you know of something that's missing please submit a ticket on
|
||||
|
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}ElGamal/AES + SessionTag Encryption{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}March 2014{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.12{% endblock %}
|
||||
{% block lastupdated %}{% trans %}January 2016{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block content %}
|
||||
<h2>{% trans %}Overview{% endtrans %}</h2>
|
||||
<p>{% trans -%}
|
||||
@@ -180,7 +180,8 @@ and the encrypted block is 514 bytes long.
|
||||
<p>{% trans -%}
|
||||
The unencrypted data in the AES block contains the following:
|
||||
{%- endtrans %}</p>
|
||||
<pre>
|
||||
|
||||
{% highlight lang='dataspec' %}
|
||||
+----+----+----+----+----+----+----+----+
|
||||
|tag count| |
|
||||
+----+----+ +
|
||||
@@ -220,42 +221,38 @@ The unencrypted data in the AES block contains the following:
|
||||
+----+----+----//---+----+ +
|
||||
| Padding to 16 bytes |
|
||||
+----+----+----+----+----+----+----+----+
|
||||
{% endhighlight %}
|
||||
|
||||
tag count: {% trans commonstructures=site_url('docs/spec/common-structures') -%}
|
||||
2-byte <a href="{{ commonstructures }}#type_Integer">Integer</a>, 0-200
|
||||
{%- endtrans %}
|
||||
<h4>Definition</h4>
|
||||
{% highlight lang='dataspec' %}
|
||||
tag count:
|
||||
2-byte `Integer`, 0-200
|
||||
|
||||
Session Tags: {% trans commonstructures=site_url('docs/spec/common-structures') -%}
|
||||
That many 32-byte <a href="{{ commonstructures }}#type_SessionTag">Session Tags</a>
|
||||
{%- endtrans %}
|
||||
Session Tags:
|
||||
That many 32-byte `SessionTag`s
|
||||
|
||||
payload size: {% trans commonstructures=site_url('docs/spec/common-structures') -%}
|
||||
4-byte <a href="{{ commonstructures }}#type_Integer">Integer</a>
|
||||
{%- endtrans %}
|
||||
payload size:
|
||||
4-byte `Integer`
|
||||
|
||||
Payload Hash: {% trans commonstructures=site_url('docs/spec/common-structures') -%}
|
||||
The 32-byte <a href="{{ commonstructures }}#type_Hash">SHA256 Hash</a> of the payload
|
||||
{%- endtrans %}
|
||||
Payload Hash:
|
||||
The 32-byte SHA256 `Hash` of the payload
|
||||
|
||||
flag: {% trans -%}
|
||||
flag:
|
||||
A one-byte value. Normally == 0. If == 0x01, a Session Key follows
|
||||
{%- endtrans %}
|
||||
|
||||
New Session Key: {% trans commonstructures=site_url('docs/spec/common-structures') -%}
|
||||
A 32-byte <a href="{{ commonstructures }}#type_SessionKey">Session Key</a>,
|
||||
New Session Key:
|
||||
A 32-byte `SessionKey`,
|
||||
to replace the old key, and is only present if preceding flag is 0x01
|
||||
{%- endtrans %}
|
||||
|
||||
Payload: {% trans %}the data{% endtrans %}
|
||||
Payload: the data
|
||||
|
||||
Padding: {% trans -%}
|
||||
Padding:
|
||||
Random data to a multiple of 16 bytes for the total length.
|
||||
May contain more than the minimum required padding.
|
||||
{%- endtrans %}
|
||||
{% endhighlight %}
|
||||
|
||||
{% trans %}Minimum length: 48 bytes{% endtrans %}
|
||||
|
||||
</pre>
|
||||
|
||||
<p>{% trans cryptography=site_url('docs/how/cryptography') -%}
|
||||
The data is then <a href="{{ cryptography }}">AES Encrypted</a>,
|
||||
@@ -287,7 +284,8 @@ ElGamal block.
|
||||
The existing session message is
|
||||
as follows:
|
||||
{%- endtrans %}</p>
|
||||
<pre>
|
||||
|
||||
{% highlight lang='dataspec' %}
|
||||
+----+----+----+----+----+----+----+----+
|
||||
| |
|
||||
+ +
|
||||
@@ -305,15 +303,17 @@ as follows:
|
||||
+ +
|
||||
| |
|
||||
+----+----+----+----+----+----+----+----+
|
||||
{% endhighlight %}
|
||||
|
||||
Session Tag: {% trans commonstructures=site_url('docs/spec/common-structures') -%}
|
||||
A 32-byte <a href="{{ commonstructures }}#type_SessionTag">Session Tag</a>
|
||||
<h4>Definition</h4>
|
||||
{% highlight lang='dataspec' %}
|
||||
Session Tag:
|
||||
A 32-byte `SessionTag`
|
||||
previously delivered in an AES block
|
||||
{%- endtrans %}
|
||||
|
||||
AES Encrypyted Block: {% trans %}As specified <a href="#aes">above</a>.{% endtrans %}
|
||||
AES Encrypyted Block: As specified above.
|
||||
{% endhighlight %}
|
||||
|
||||
</pre>
|
||||
|
||||
<p>{% trans -%}
|
||||
The session tag also serves as
|
||||
|
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}The Network Database{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}Nov. 2015{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.23{% endblock %}
|
||||
{% block lastupdated %}{% trans %}February 2016{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block content %}
|
||||
<h2>{% trans %}Overview{% endtrans %}</h2>
|
||||
|
||||
@@ -36,6 +36,8 @@ as the key. The structure itself contains:
|
||||
<li>{% trans %}The signature of the above, generated by the identity's signing key{% endtrans %}</li>
|
||||
</ul>
|
||||
|
||||
<h3>{% trans %}Expected Options{% endtrans %}</h3>
|
||||
|
||||
<p>{% trans -%}
|
||||
The following text options, while not strictly required, are expected
|
||||
to be present:
|
||||
@@ -62,7 +64,7 @@ For compatibility with older routers, a router may publish multiple bandwidth le
|
||||
</li>
|
||||
<li><b>coreVersion</b>
|
||||
({% trans %}The core library version, always the same as the router version{% endtrans %})
|
||||
(Unused, scheduled to be removed soon)
|
||||
(Never used, scheduled to be removed in release 0.9.24)
|
||||
</li>
|
||||
<li><b>netId</b> = 2
|
||||
({% trans %}Basic network compatibility - A router will refuse to communicate with a peer having a different netId{% endtrans %})
|
||||
@@ -72,8 +74,8 @@ For compatibility with older routers, a router may publish multiple bandwidth le
|
||||
</li>
|
||||
<li><b>stat_uptime</b> = 90m
|
||||
({% trans %}Always sent as 90m, for compatibility with an older scheme where routers published their actual uptime,
|
||||
and only sent tunnel requests to peers whose was more than 60m{% endtrans %})
|
||||
(Unused, scheduled to be removed soon)
|
||||
and only sent tunnel requests to peers whose uptime was more than 60m{% endtrans %})
|
||||
(Unused since version 0.7.9, scheduled to be removed in release 0.9.24)
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -86,6 +88,7 @@ Above the minimum threshold, the advertised bandwidth is not used or trusted any
|
||||
in the router, except for display in the user interface and for debugging and network analysis.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h3>{% trans %}Additional Options{% endtrans %}</h3>
|
||||
|
||||
<p>{% trans stats=i2pconv('stats.i2p') -%}
|
||||
Additional text options include
|
||||
@@ -113,12 +116,33 @@ As the network has matured, we have gradually removed most of the published
|
||||
statistics to improve anonymity, and we plan to remove more in future releases.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_RouterInfo">{% trans %}RouterInfo specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/RouterInfo.html">{% trans %}RouterInfo Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
<h3>{% trans %}Family Options{% endtrans %}</h3>
|
||||
|
||||
<p>{% trans -%}
|
||||
As of release 0.9.24, routers may declare that they are part of a "family", operated by the same entity.
|
||||
Multiple routers in the same family will not be used in a single tunnel.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans -%}
|
||||
The family options are:
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<ul>
|
||||
<li><b>family</b>
|
||||
({% trans %}The family name{% endtrans %})
|
||||
</li>
|
||||
<li><b>family.key</b>
|
||||
The signature type code of the family's
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPublicKey">Signing Public Key</a>
|
||||
(in ASCII digits)
|
||||
concatenated with ':'
|
||||
concatenated with the Signing Public Key in base 64
|
||||
</li>
|
||||
<li><b>family.sig</b>
|
||||
The signature of ((family name in UTF-8) concatenated with (32 byte router hash)) in base 64
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
||||
<h3>{% trans %}RouterInfo Expiration{% endtrans %}</h3>
|
||||
<p>{% trans -%}
|
||||
@@ -156,6 +180,15 @@ RouterInfos are periodically written to disk so that they are available after a
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
||||
<h3>{% trans %}See Also{% endtrans %}</h3>
|
||||
|
||||
<p>
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_RouterInfo">{% trans %}RouterInfo specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/RouterInfo.html">{% trans %}RouterInfo Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
|
||||
<h2 id="leaseSet">LeaseSet</h2>
|
||||
|
||||
<p>{% trans -%}
|
||||
@@ -189,9 +222,9 @@ In addition to these leases, the LeaseSet includes:
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_LeaseSet">{% trans %}LeaseSet specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/Lease.html">{% trans %}Lease Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Lease.html">{% trans %}Lease Javadoc{% endtrans %}</a>
|
||||
<br />
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/LeaseSet.html">{% trans %}LeaseSet Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/LeaseSet.html">{% trans %}LeaseSet Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
|
||||
|
||||
|
@@ -63,7 +63,7 @@ See <a href="#notes">below</a> for notes on minor changes since the paper was pu
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2>{% trans %}Profiles{% endtrans %}</h2>
|
||||
<p>{% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/router/peermanager/PeerProfile.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/router/peermanager/PeerProfile.html' -%}
|
||||
Each peer has a set of data points collected about them, including statistics
|
||||
about how long it takes for them to reply to a network database query, how
|
||||
often their tunnels fail, and how many new peers they are able to introduce
|
||||
@@ -142,7 +142,7 @@ speed calculation meets or exceeds the median of all peers.
|
||||
<li>{% trans %}A peer is considered "standard" if it is not "high capacity"{% endtrans %}</li>
|
||||
</ul>
|
||||
|
||||
<p>{% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/router/peermanager/ProfileOrganizer.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/router/peermanager/ProfileOrganizer.html' -%}
|
||||
These groupings are implemented in the router's
|
||||
<a href="{{ url }}">ProfileOrganizer</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
@@ -1,26 +1,22 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Introducing I2P{% endtrans %}{% endblock %}
|
||||
{% block title %}{% trans %}I2P: A scalable framework for anonymous communication{% endtrans %}{% endblock %}
|
||||
{% block content_nav %}
|
||||
<ul>
|
||||
<li><a href="#intro">{% trans %}Introduction{% endtrans %}</a></li>
|
||||
<li>
|
||||
<a href="#op">{% trans %}I2P Operation{% endtrans %}</a>
|
||||
<ul>
|
||||
<li><a href="#op.overview">{% trans %}Overview{% endtrans %}</a></li>
|
||||
<li><a href="#op.tunnels">{% trans %}Tunnels{% endtrans %}</a></li>
|
||||
<li><a href="#op.netdb">{% trans %}Network Database{% endtrans %}</a></li>
|
||||
<li><a href="#op.transport">{% trans %}Transport protocols{% endtrans %}</a></li>
|
||||
<li><a href="#op.crypto">{% trans %}Cryptography{% endtrans %}</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
{% endblock %}
|
||||
|
||||
{% block content %}
|
||||
|
||||
<h1 class="title">{% trans %}I2P: A scalable framework for anonymous communication{% endtrans %}</h1>
|
||||
<div id="toc">
|
||||
<h2>{% trans %}Table of Contents{% endtrans %}</h2>
|
||||
<ul>
|
||||
<li><a href="#intro">{% trans %}Introduction{% endtrans %}</a></li>
|
||||
<li>
|
||||
<a href="#op">{% trans %}I2P Operation{% endtrans %}</a>
|
||||
<ul>
|
||||
<li><a href="#op.overview">{% trans %}Overview{% endtrans %}</a></li>
|
||||
<li><a href="#op.tunnels">{% trans %}Tunnels{% endtrans %}</a></li>
|
||||
<li><a href="#op.netdb">{% trans %}Network Database{% endtrans %}</a></li>
|
||||
<li><a href="#op.transport">{% trans %}Transport protocols{% endtrans %}</a></li>
|
||||
<li><a href="#op.crypto">{% trans %}Cryptography{% endtrans %}</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<br/>
|
||||
<h1 id="intro">{% trans %}Introduction{% endtrans %}</h1>
|
||||
<p>{% trans -%}
|
||||
I2P is a scalable, self organizing, resilient packet switched anonymous
|
||||
|
@@ -41,6 +41,30 @@
|
||||
</ul>
|
||||
{% endmacro %}
|
||||
|
||||
{% block content_nav %}
|
||||
<h3>{% trans %}Index of Attacks{% endtrans %}</h3>
|
||||
<ul>
|
||||
<li><a href="#bruteforce">{% trans %}Brute force attacks{% endtrans %}</a></li>
|
||||
<li><a href="#timing">{% trans %}Timing attacks{% endtrans %}</a></li>
|
||||
<li><a href="#intersection">{% trans %}Intersection attacks{% endtrans %}</a></li>
|
||||
<li><a href="#dos">{% trans %}Denial of service attacks{% endtrans %}</a></li>
|
||||
<li><a href="#tagging">{% trans %}Tagging attacks{% endtrans %}</a></li>
|
||||
<li><a href="#partitioning">{% trans %}Partitioning attacks{% endtrans %}</a></li>
|
||||
<li><a href="#predecessor">{% trans %}Predecessor attacks{% endtrans %}</a></li>
|
||||
<li><a href="#harvesting">{% trans %}Harvesting attacks{% endtrans %}</a></li>
|
||||
<li><a href="#traffic">{% trans %}Identification Through Traffic Analysis{% endtrans %}</a></li>
|
||||
<li><a href="#sybil">{% trans %}Sybil attacks{% endtrans %}</a></li>
|
||||
<li><a href="#buddy">{% trans %}Buddy Exhaustion attacks{% endtrans %}</a></li>
|
||||
<li><a href="#crypto">{% trans %}Cryptographic attacks{% endtrans %}</a></li>
|
||||
<li><a href="#floodfill">{% trans %}Floodfill attacks{% endtrans %}</a></li>
|
||||
<li><a href="#netdb">{% trans %}Other Network Database attacks{% endtrans %}</a></li>
|
||||
<li><a href="#central">{% trans %}Attacks on centralized resources{% endtrans %}</a></li>
|
||||
<li><a href="#dev">{% trans %}Development attacks{% endtrans %}</a></li>
|
||||
<li><a href="#impl">{% trans %}Implementation attacks{% endtrans %}</a></li>
|
||||
<li><a href="#blocklist">{% trans %}Other Defenses{% endtrans %}</a></li>
|
||||
</ul>
|
||||
{% endblock %}
|
||||
|
||||
{% block content %}
|
||||
<h2>{% trans %}What do we mean by "anonymous"?{% endtrans %}</h2>
|
||||
|
||||
@@ -179,28 +203,6 @@ and priority scores are calculated using the equations outlined
|
||||
|
||||
#}
|
||||
|
||||
<h3 id="index">{% trans %}Index of Attacks{% endtrans %}</h3>
|
||||
<ul>
|
||||
<li><a href="#bruteforce">{% trans %}Brute force attacks{% endtrans %}</a></li>
|
||||
<li><a href="#timing">{% trans %}Timing attacks{% endtrans %}</a></li>
|
||||
<li><a href="#intersection">{% trans %}Intersection attacks{% endtrans %}</a></li>
|
||||
<li><a href="#dos">{% trans %}Denial of service attacks{% endtrans %}</a></li>
|
||||
<li><a href="#tagging">{% trans %}Tagging attacks{% endtrans %}</a></li>
|
||||
<li><a href="#partitioning">{% trans %}Partitioning attacks{% endtrans %}</a></li>
|
||||
<li><a href="#predecessor">{% trans %}Predecessor attacks{% endtrans %}</a></li>
|
||||
<li><a href="#harvesting">{% trans %}Harvesting attacks{% endtrans %}</a></li>
|
||||
<li><a href="#traffic">{% trans %}Identification Through Traffic Analysis{% endtrans %}</a></li>
|
||||
<li><a href="#sybil">{% trans %}Sybil attacks{% endtrans %}</a></li>
|
||||
<li><a href="#buddy">{% trans %}Buddy Exhaustion attacks{% endtrans %}</a></li>
|
||||
<li><a href="#crypto">{% trans %}Cryptographic attacks{% endtrans %}</a></li>
|
||||
<li><a href="#floodfill">{% trans %}Floodfill attacks{% endtrans %}</a></li>
|
||||
<li><a href="#netdb">{% trans %}Other Network Database attacks{% endtrans %}</a></li>
|
||||
<li><a href="#central">{% trans %}Attacks on centralized resources{% endtrans %}</a></li>
|
||||
<li><a href="#dev">{% trans %}Development attacks{% endtrans %}</a></li>
|
||||
<li><a href="#impl">{% trans %}Implementation attacks{% endtrans %}</a></li>
|
||||
<li><a href="#blocklist">{% trans %}Other Defenses{% endtrans %}</a></li>
|
||||
</ul>
|
||||
|
||||
<h3 id="bruteforce">{% trans %}Brute force attacks{% endtrans %}</h3>
|
||||
|
||||
{# DREAD_score(2, 1, 1, 1, 3) #}
|
||||
|
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Index to Technical Documentation{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}November 2014{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.17{% endblock %}
|
||||
{% block lastupdated %}{% trans %}January 2016{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block content %}
|
||||
<p>{% trans -%}
|
||||
Following is an index to the technical documentation for I2P.
|
||||
@@ -87,11 +87,11 @@ HTTP Bidir Proxy
|
||||
</li><li>
|
||||
<a href="{{ spec_url('streaming') }}">{{ _('Streaming Protocol Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/package-summary.html">{{ _('Streaming Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/client/streaming/package-summary.html">{{ _('Streaming Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('datagrams') }}">{{ _('Datagrams') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/client/datagram/package-summary.html">{{ _('Datagram Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/client/datagram/package-summary.html">{{ _('Datagram Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Client-to-Router Interface API and Protocol{% endtrans %}</h3>
|
||||
@@ -104,11 +104,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ spec_url('i2cp') }}">{{ _('I2CP Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/client/package-summary.html">{{ _('I2CP API Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/client/package-summary.html">{{ _('I2CP API Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('common-structures') }}">{{ _('Common data structures specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}End-to-End Encryption{% endtrans %}</h3>
|
||||
@@ -134,11 +134,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ spec_url('i2np') }}">{{ _('I2NP Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/i2np/package-summary.html">{{ _('I2NP Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/i2np/package-summary.html">{{ _('I2NP Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('common-structures') }}">{{ _('Common data structures specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Tunnels{% endtrans %}</h3>
|
||||
@@ -172,11 +172,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/how/cryptography') }}#udp">{{ _('SSU transport encryption') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/router/transport/package-summary.html">{{ _('Transport Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/transport/package-summary.html">{{ _('Transport Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/router/transport/ntcp/package-summary.html">{{ _('NTCP Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/transport/ntcp/package-summary.html">{{ _('NTCP Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/router/transport/udp/package-summary.html">{{ _('SSU Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/transport/udp/package-summary.html">{{ _('SSU Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Other Router Topics{% endtrans %}</h3>
|
||||
@@ -221,6 +221,8 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/applications/embedding') }}">{{ _('Embedding the router in your application') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('get-involved/guides/reseed') }}">{{ _('How to Set up a Reseed Server') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/ports') }}">{{ _('Ports used by I2P') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('update.killyourtv.i2p') }}/mtn/">{{ _('Automatic updates to development builds inside I2P') }}</a>
|
||||
@@ -241,9 +243,7 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="https://www.transifex.net/projects/p/I2P/">{{ _('Source translation at Transifex') }}</a>
|
||||
</li><li>
|
||||
<a href="https://trac.i2p2.de/wiki/Roadmaps/1.0">{{ _('Roadmap wiki') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('get-involved/roadmap') }}">{{ _('Old roadmap') }}</a> ({{ _('not current') }})
|
||||
<a href="{{ site_url('get-involved/roadmap') }}">{{ _('Roadmap') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('get-involved/todo') }}">{{ _('To Do List') }}</a> ({{ _('not current') }})
|
||||
</li><li>
|
||||
|
@@ -140,7 +140,7 @@ It also maintains a reverse-lookup map to implement rapid reverse lookups.
|
||||
|
||||
<h3>{{ _('Other Naming Service Facilities') }}</h3>
|
||||
|
||||
<p>{% trans nsjavadocs='http://docs.i2p-projekt.de/javadoc/net/i2p/client/naming/package-summary.html' -%}
|
||||
<p>{% trans nsjavadocs='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/naming/package-summary.html' -%}
|
||||
The lookup is case-insensitive.
|
||||
The first match is used, and conflicts are not detected.
|
||||
There is no enforcement of naming rules in lookups.
|
||||
|
@@ -1,6 +1,6 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Ports Used by I2P{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}April 2015{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}December 2015{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.19{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
@@ -61,6 +61,7 @@ in the 766x range.
|
||||
<tr><td>8999</td><td>Monotone Proxy (alt)</td></tr>
|
||||
<tr><td>9050</td><td>Tor SOCKS Proxy (reserve)</td></tr>
|
||||
<tr><td>9051-9053</td><td>SOCKS Proxy (typ)</td></tr>
|
||||
<tr><td>9152-9153</td><td>Tor Messenger Socks and Control ports (reserve)</td></tr>
|
||||
<tr><td>9111-30777</td><td>Network (random)</td></tr>
|
||||
<tr><td>11371</td><td>SKS/GPG Key Server (reserve)</td></tr>
|
||||
<tr><td>31000</td><td>Wrapper</td></tr>
|
||||
|
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}I2CP{% endblock %}
|
||||
{% block lastupdated %}{% trans %}December 2014{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.17{% endblock %}
|
||||
{% block lastupdated %}{% trans %}Fegruary 2016{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block content %}
|
||||
<p>{% trans -%}
|
||||
The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
|
||||
@@ -15,7 +15,7 @@ I2CP to tell the client when any messages have arrived, and to request authoriza
|
||||
for some tunnels to be used.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans url='http://docs.i2p-projekt.de/javadoc/net/i2p/client/package-summary.html',
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/package-summary.html',
|
||||
libi2cp='http://git.repo.i2p/w/libi2cp.git',
|
||||
streaming=site_url('docs/api/streaming') -%}
|
||||
The protocol itself is implemented in Java, to provide the
|
||||
@@ -709,6 +709,11 @@ turns the gzip effort setting to 0, which may save a little CPU.
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>
|
||||
Note: I2P protocol numbers 224-254 are reserved for experimental protocols.
|
||||
I2P protocol number 255 is reserved for future expansion.
|
||||
</p>
|
||||
|
||||
<p>{% trans -%}
|
||||
Data integrity is verified with the standard gzip CRC-32 as
|
||||
specified by <a href="http://www.ietf.org/rfc/rfc1952.txt">RFC 1952</a>.
|
||||
|
@@ -19,7 +19,7 @@ through multiple hops to the ultimate destination.
|
||||
Priority is only used locally at the origin, i.e. when queuing for outbound delivery.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans outnetmessage='http://docs.i2p-projekt.de/javadoc/net/i2p/router/OutNetMessage.html' -%}
|
||||
<p>{% trans outnetmessage='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/router/OutNetMessage.html' -%}
|
||||
The priorities listed below may not be current and are subject to change.
|
||||
See the <a href="{{ outnetmessage }}">OutNetMessage Javadocs</a>
|
||||
for the current priority settings.
|
||||
|
46
i2p2www/pages/site/docs/reseed.html
Normal file
46
i2p2www/pages/site/docs/reseed.html
Normal file
@@ -0,0 +1,46 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Reseed Hosts{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}January 2016{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
|
||||
<h2 id="about">{% trans %}About Reseed hosts{% endtrans %}</h2>
|
||||
|
||||
<p>{% trans -%}
|
||||
Reseed hosts are needed to for bootstrapping, that is, providing the initial set of I2P nodes for your I2P node to talk to. Depending on the status of your node it may need to bootstrap every now and then if many of the nodes it knows of aren't contactable.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans -%}
|
||||
Reseeding is done over an encrypted connection and all of the bootstrap information is signed by the reseed host you connect to, making it impossible for an unauthenticated source to provide you with false information.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
||||
<h2 id="running">{% trans %}Running a Reseed host{% endtrans %}</h2>
|
||||
<p>
|
||||
{% trans -%}
|
||||
The more reseed hosts that are run, the more resilient the I2P network becomes, and the harder it is to prevent users of I2P from connecting to the network.
|
||||
{%- endtrans %}
|
||||
</p>
|
||||
{% trans -%}
|
||||
There have also been cases where the reseed hosts we had, have been under heavy load due to botnet activities.
|
||||
{%- endtrans %}
|
||||
</p>
|
||||
<p>
|
||||
<a href="{{ site_url('get-involved/guides/reseed') }}">How to run a Reseed host</a>
|
||||
</p>
|
||||
|
||||
<h2 id="thank you">{% trans %}Thank you{% endtrans %}</h2>
|
||||
<p>
|
||||
{%-trans -%}
|
||||
If you are running a reseed server, We would like to thank you for helping to
|
||||
make the I2P network stronger and more resilient than ever.
|
||||
{%- endtrans-%}
|
||||
</p>
|
||||
<p>
|
||||
{%-trans -%}
|
||||
Thank you.
|
||||
{%- endtrans-%}
|
||||
</p>
|
||||
|
||||
{% endblock %}
|
Reference in New Issue
Block a user