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

Update info on certs in destinations

Browse Source
This commit is contained in:
zzz
2018-06-07 19:43:04 +00:00
parent e44a04c8fb
commit 2b51f2b17f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
i2p2www/pages/site/docs/naming.html
View File

@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Naming and Addressbook{% endtrans %}{% endblock %}
{% block lastupdated %}{% trans %}May 2016{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.26{% endblock %}
{% block lastupdated %}{% trans %}June 2018{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.34{% endblock %}
{% block content %}
<h2 id="overview">{% trans %}Overview{% endtrans %}</h2>
@ -78,10 +78,10 @@ for addressbook configuration and viewing of the local host lists.
<p>{% trans namingdiscussion=site_url('docs/discussions/naming'), todo=site_url('get-involved/todo') -%}
All destinations in I2P are 516-byte (or longer) keys.
(To be more precise, it is a 256-byte public key plus a 128-byte signing key
plus a null certificate, which in Base64 representation is 516 bytes.
<a href="{{ namingdiscussion }}#certificates">Certificates</a> are not used now,
if they are, the keys will be longer.
One possible use of certificates is for <a href="{{ todo }}#hashcash">proof of work</a>.)
plus a 3-or-more byte certificate, which in Base64 representation is 516 or more bytes.
Non-null <a href="{{ namingdiscussion }}#certificates">Certificates</a> are in use now
for signature type indication.
Therefore, certificates in recently-generated destinations are more than 3 bytes.
{%- endtrans %}</p>
<p>{% trans -%}