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

SSU: intro key may be randomized

Browse Source
This commit is contained in:
zzz
2020-09-23 14:54:04 +00:00
parent 97a6a80aed
commit 51d844192c
2 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
i2p2www/pages/site/docs/transport/ssu.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Secure Semireliable UDP{% endtrans %} (SSU){% endblock %}
{% block lastupdated %}{% trans %}June 2018{% endtrans %}{% endblock %}
{% block accuratefor %}0.9.36{% endblock %}
{% block lastupdated %}2020-09{% endblock %}
{% block accuratefor %}0.9.48{% endblock %}
{% block content %}
<p>{% trans transports=site_url('docs/transport'), ntcp=site_url('docs/transport/ntcp'), ntcp2=site_url('docs/spec/ntcp2') -%}
@@ -343,8 +343,10 @@ the status message can be eliminated.
<p>{% trans -%}
Introduction keys are delivered through an external channel
(the network database, where they are identical to the router Hash for now)
and must be used when establishing a session key. For the indirect
(the network database),
where they have traditionally been identical to the router Hash through release 0.9.47,
but may be random as of release 0.9.48.
They must be used when establishing a session key. For the indirect
address, the peer must first contact the relayhost and ask them for
an introduction to the peer known at that relayhost under the given
tag. If possible, the relayhost sends a message to the addressed

7
i2p2www/spec/ssu.rst
View File

@@ -3,8 +3,8 @@ SSU Protocol Specification
==========================
.. meta::
:category: Transports
:lastupdated: August 2019
:accuratefor: 0.9.42
:lastupdated: 2020-09
:accuratefor: 0.9.48
.. contents::
@@ -250,7 +250,8 @@ Common structures specification [SESSIONKEY]_. The key used for the MAC and
encryption is specified for each message below.
Introduction keys are delivered through an external channel (the network
database, where they are identical to the router Hash for now).
database), where they have traditionally been identical to the router Hash through release 0.9.47,
but may be random as of release 0.9.48.
Notes