kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix i2cp.leaseSetPrivateKey spec for LS2

Browse Source
This commit is contained in:
zzz
2020-05-05 13:13:35 +00:00
parent befcede793
commit 874681edb8
1 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}I2CP{% endblock %}
{% block lastupdated %}2019-09{% endblock %}
{% block accuratefor %}0.9.42{% endblock %}
{% block lastupdated %}2020-05{% endblock %}
{% block accuratefor %}0.9.46{% endblock %}
{% block content %}
<p>{% trans -%}
The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
@@ -242,7 +242,7 @@ only if per-client authentication is enabled.
Optionally preceded by the key type and ':'.
Only "ECIES_X25519:" is supported, which is the default.
See proposal 123.
Do not confuse with i2cp.leaseSetPrivateKey which is for LS1.
Do not confuse with i2cp.leaseSetPrivateKey which is for the leaseset encryption keys.
</td>
</tr>
@@ -717,6 +717,7 @@ The encryption type to be used, as of 0.9.38.
Interpreted client-side, but also passed to the router in the
SessionConfig, to declare intent and check support.
As of 0.9.39, may be comma-separated values for multiple types.
See also i2cp.leaseSetPrivateKey.
See PublicKey in common strutures spec for values.
See proposals 123, 144, and 145.
</td>
@@ -738,13 +739,18 @@ See proposals 123, 144, and 145.
<td>&nbsp;
<td>&nbsp;
<td>{% trans -%}
Base 64 private key for encryption, for old encrypted LS1.
Optionally preceded by the key type and ':'.
Only "ELGAMAL_2048:" is supported, which is the default.
Base 64 private keys for encryption.
Optionally preceded by the encryption type name or number and ':'.
For LS1, only one key is supported, and
only "0:" or "ELGAMAL_2048:" is supported, which is the default.
As of 0.9.39, for LS2, multiple keys may be comma-separated,
and each key must be a different encryption type.
I2CP will generate the public key from the private key.
Use for persistent leaseset keys across restarts.
See proposals 123, 144, and 145.
See also i2cp.leaseSetEncType.
{%- endtrans %}</td>
Do not confuse with i2cp.leaseSetPrivKey which is for LS2.
Do not confuse with i2cp.leaseSetPrivKey which is for encrypted LS2.
</tr>
<tr>