diff --git a/i2p2www/pages/site/docs/protocol/i2cp.html b/i2p2www/pages/site/docs/protocol/i2cp.html index 409f6bd2..6452daa7 100644 --- a/i2p2www/pages/site/docs/protocol/i2cp.html +++ b/i2p2www/pages/site/docs/protocol/i2cp.html @@ -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 %}
{% 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. @@ -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. @@ -738,13 +739,18 @@ See proposals 123, 144, and 145.