From 51d844192ca3a9931ff0be0e30f30df8ef4dee03 Mon Sep 17 00:00:00 2001 From: zzz Date: Wed, 23 Sep 2020 14:54:04 +0000 Subject: [PATCH] SSU: intro key may be randomized --- i2p2www/pages/site/docs/transport/ssu.html | 10 ++++++---- i2p2www/spec/ssu.rst | 7 ++++--- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git a/i2p2www/pages/site/docs/transport/ssu.html b/i2p2www/pages/site/docs/transport/ssu.html index 154752c4..eba98b0d 100644 --- a/i2p2www/pages/site/docs/transport/ssu.html +++ b/i2p2www/pages/site/docs/transport/ssu.html @@ -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 %}

{% 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.

{% 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 diff --git a/i2p2www/spec/ssu.rst b/i2p2www/spec/ssu.rst index 8776f275..bd20e0f1 100644 --- a/i2p2www/spec/ssu.rst +++ b/i2p2www/spec/ssu.rst @@ -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