Clarify i2cp.leaseSetSecret option

This commit is contained in:
zzz
2019-09-06 15:36:06 +00:00
parent 68560eab1a
commit bb66c992f8
2 changed files with 9 additions and 8 deletions

View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}I2CP{% endblock %}
{% block lastupdated %}{% trans %}June 2019{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.41{% endblock %}
{% block lastupdated %}2019-09{% endblock %}
{% block accuratefor %}0.9.42{% endblock %}
{% block content %}
<p>{% trans -%}
The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
@@ -254,7 +254,7 @@ Do not confuse with i2cp.leaseSetPrivateKey which is for LS1.
<td>""
<td>
Base 64 encoded UTF-8
secret used to blind the leaseset.
secret used to blind the leaseset address.
See proposal 123.
</td>
</tr>
@@ -755,7 +755,7 @@ Do not confuse with i2cp.leaseSetPrivKey which is for LS2.
<td>""
<td>
Base 64 encoded UTF-8
secret used to blind the leaseset.
secret used to blind the leaseset address.
See proposal 123.
</td>
</tr>