forked from I2P_Developers/i2p.www
SSU: intro key may be randomized
This commit is contained in:
@@ -1,7 +1,7 @@
|
|||||||
{% extends "global/layout.html" %}
|
{% extends "global/layout.html" %}
|
||||||
{% block title %}{% trans %}Secure Semireliable UDP{% endtrans %} (SSU){% endblock %}
|
{% block title %}{% trans %}Secure Semireliable UDP{% endtrans %} (SSU){% endblock %}
|
||||||
{% block lastupdated %}{% trans %}June 2018{% endtrans %}{% endblock %}
|
{% block lastupdated %}2020-09{% endblock %}
|
||||||
{% block accuratefor %}0.9.36{% endblock %}
|
{% block accuratefor %}0.9.48{% endblock %}
|
||||||
{% block content %}
|
{% block content %}
|
||||||
|
|
||||||
<p>{% trans transports=site_url('docs/transport'), ntcp=site_url('docs/transport/ntcp'), ntcp2=site_url('docs/spec/ntcp2') -%}
|
<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 -%}
|
<p>{% trans -%}
|
||||||
Introduction keys are delivered through an external channel
|
Introduction keys are delivered through an external channel
|
||||||
(the network database, where they are identical to the router Hash for now)
|
(the network database),
|
||||||
and must be used when establishing a session key. For the indirect
|
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
|
address, the peer must first contact the relayhost and ask them for
|
||||||
an introduction to the peer known at that relayhost under the given
|
an introduction to the peer known at that relayhost under the given
|
||||||
tag. If possible, the relayhost sends a message to the addressed
|
tag. If possible, the relayhost sends a message to the addressed
|
||||||
|
@@ -3,8 +3,8 @@ SSU Protocol Specification
|
|||||||
==========================
|
==========================
|
||||||
.. meta::
|
.. meta::
|
||||||
:category: Transports
|
:category: Transports
|
||||||
:lastupdated: August 2019
|
:lastupdated: 2020-09
|
||||||
:accuratefor: 0.9.42
|
:accuratefor: 0.9.48
|
||||||
|
|
||||||
.. contents::
|
.. contents::
|
||||||
|
|
||||||
@@ -250,7 +250,8 @@ Common structures specification [SESSIONKEY]_. The key used for the MAC and
|
|||||||
encryption is specified for each message below.
|
encryption is specified for each message below.
|
||||||
|
|
||||||
Introduction keys are delivered through an external channel (the network
|
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
|
Notes
|
||||||
|
Reference in New Issue
Block a user