I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

I2CP: Add persistent key proposal

Browse Source 
RSA: Add RFC reference
SU3: Add plugin info
This commit is contained in:
zzz
2014-12-17 14:28:39 +00:00
parent eec0494fd8
commit ed54f24e22
4 changed files with 63 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/pages/site/docs/how/cryptography.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Low-level Cryptography Details{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}November 2014{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.16{% endblock %}
{% block lastupdated %}{% trans %}December 2014{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.17{% endblock %}
{% block content %}
<p>{% trans -%}
This page specifies the low-level details of the cryptography in I2P.
@@ -414,7 +414,7 @@ Usage for Router Identities is supported as of release 0.9.16 and migration may
<h3>RSA</h3>
<p>{% trans -%}
Standard RSA with the public exponent F4 = 65537.
Standard RSA PKCS#1 v1.5 (RFC 2313) with the public exponent F4 = 65537.
RSA is now used for signing all out-of-band trusted content, including router updates, reseeding, plugins, and news.
The signatures are embedded in the "su3" format documented on the router updates page.
4096-bit keys are recommended and used by all known signers.

35
i2p2www/pages/site/docs/protocol/i2cp.html
View File

@@ -1,6 +1,6 @@
{% extends "global/layout.html" %}
{% block title %}I2CP{% endblock %}
{% block lastupdated %}{% trans %}November 2014{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}December 2014{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.17{% endblock %}
{% block content %}
<p>{% trans -%}
@@ -537,7 +537,38 @@ of sending a MessageStatus and awaiting a ReceiveMessageBegin.
<td>&nbsp;
<td>&nbsp;
<td>&nbsp;
<td>{% trans %}Base64 SessionKey (44 characters){% endtrans %}</td>
<td>{% trans %}For encrypted leasesets. Base 64 SessionKey (44 characters){% endtrans %}</td>
</tr>
<tr>
<td>i2cp.leaseSetPrivateKey
<td>0.9.18</td>
<td>&nbsp;
<td>&nbsp;
<td>&nbsp;
<td>{% trans -%}
Base 64 private key for encryption.
Optionally preceded by the key type and ':'.
Only "ELGAMAL_2048:" is supported, which is the default.
I2CP will generate the public key from the private key.
Use for persistent leaseset keys across restarts.
{%- endtrans %}</td>
</tr>
<tr>
<td>i2cp.leaseSetSigningPrivateKey
<td>0.9.18</td>
<td>&nbsp;
<td>&nbsp;
<td>&nbsp;
<td>{% trans -%}
Base 64 private key for signatures.
Optionally preceded by the key type and ':'.
DSA_SHA1 is the default.
Key type must match the signature type in the destination.
I2CP will generate the public key from the private key.
Use for persistent leaseset keys across restarts.
{%- endtrans %}</td>
</tr>
<tr>

6
i2p2www/pages/site/docs/spec/plugin.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}I2P Plugin Specification{% endblock %}
{% block lastupdated %}August 2014{% endblock %}
{% block accuratefor %}0.9.14.1{% endblock %}
{% block lastupdated %}December 2014{% endblock %}
{% block accuratefor %}0.9.17{% endblock %}
{% block content %}
<h3>Overview</h3>
<p>
@@ -18,7 +18,7 @@ The basic .xpi2p file format is the same as a i2pupdate.sud file
but the installer will let the user install the
addon even if it doesn't know the signer's key yet.
<p>
As of release 0.9.15, the .su3 file format is supported and is preferred.
As of release 0.9.15, the <a href="updates">su3 file format</a> is supported and is preferred.
This format enables stronger signing keys.

25
i2p2www/pages/site/docs/spec/updates.html
View File

@@ -178,7 +178,7 @@ The router will then delete the deletelist.txt file.
<p>{% trans -%}
This specification is used for router updates as of release 0.9.9, reseed data as of release 0.9.14,
and the news file as of release 0.9.17.
plugins as of release 0.9.15, and the news file as of release 0.9.17.
{%- endtrans %}</p>
<h4>{% trans %}Issues with the previous .sud/.su2 format:{% endtrans %}</h4>
@@ -400,6 +400,29 @@ The I2P base 64 alphabet must be used.
<h3>{% trans %}SU3 Plugin File Specification{% endtrans %}</h3>
<p>{% trans -%}
As of 0.9.15, plugins may be packaged in an "su3" file format.
{%- endtrans %}</p>
<p><b>SU3 Details:</b></p>
<ul><li>
SU3 Content Type: 2 (PLUGIN)
</li><li>
SU3 File Type: 0 (ZIP)
See <a href="plugin">the plugin specification</a> for details.
</li><li>
SU3 Version: The plugin version, must match that in plugin.config.
</li><li>
Jar and war files in the zip are compressed with pack200 as documented above for "su2" files.
</li></ul>
<h3>{% trans %}SU3 News File Specification{% endtrans %}</h3>
<p>{% trans -%}
As of 0.9.17, the news is delivered in an "su3" file format.