forked from I2P_Developers/i2p.www
minor updates
This commit is contained in:
@@ -1,7 +1,7 @@
|
|||||||
{% extends "global/layout.html" %}
|
{% extends "global/layout.html" %}
|
||||||
{% block title %}{% trans %}ElGamal/AES + SessionTag Encryption{% endtrans %}{% endblock %}
|
{% block title %}{% trans %}ElGamal/AES + SessionTag Encryption{% endtrans %}{% endblock %}
|
||||||
{% block lastupdated %}{% trans %}January 2016{% endtrans %}{% endblock %}
|
{% block lastupdated %}April 2020{% endblock %}
|
||||||
{% block accuratefor %}0.9.24{% endblock %}
|
{% block accuratefor %}0.9.46{% endblock %}
|
||||||
{% block content %}
|
{% block content %}
|
||||||
<h2>{% trans %}Overview{% endtrans %}</h2>
|
<h2>{% trans %}Overview{% endtrans %}</h2>
|
||||||
<p>{% trans -%}
|
<p>{% trans -%}
|
||||||
@@ -342,6 +342,14 @@ See the <a href="{{ i2cpspec }}#msg_SendMessageExpires">I2CP Send Message Expire
|
|||||||
|
|
||||||
|
|
||||||
<h2 id="future">{% trans %}Future Work{% endtrans %}</h2>
|
<h2 id="future">{% trans %}Future Work{% endtrans %}</h2>
|
||||||
|
|
||||||
|
<p><b>Note:</b>
|
||||||
|
ElGamal/AES+SessionTags is being replaced with ECIES-X25519-AEAD-Ratchet (Proposal 144).
|
||||||
|
The issues and ideas referenced below have been incorporated
|
||||||
|
into the design of the new protocol.
|
||||||
|
The following items will not be addressed in ElGamal/AES+SessionTags.
|
||||||
|
</p>
|
||||||
|
|
||||||
<p>{% trans -%}
|
<p>{% trans -%}
|
||||||
There are many possible areas to tune the Session Key Manager's algorithms;
|
There are many possible areas to tune the Session Key Manager's algorithms;
|
||||||
some may interact with the streaming library behavior, or have significant
|
some may interact with the streaming library behavior, or have significant
|
||||||
|
@@ -5,7 +5,7 @@ ECIES-X25519-AEAD-Ratchet
|
|||||||
:author: zzz, chisana, orignal
|
:author: zzz, chisana, orignal
|
||||||
:created: 2018-11-22
|
:created: 2018-11-22
|
||||||
:thread: http://zzz.i2p/topics/2639
|
:thread: http://zzz.i2p/topics/2639
|
||||||
:lastupdated: 2020-04-27
|
:lastupdated: 2020-04-28
|
||||||
:status: Open
|
:status: Open
|
||||||
:target: 0.9.46
|
:target: 0.9.46
|
||||||
:implementedin: 0.9.46
|
:implementedin: 0.9.46
|
||||||
@@ -3512,11 +3512,14 @@ Storage
|
|||||||
The sender generates tags and keys on the fly, so there is no storage.
|
The sender generates tags and keys on the fly, so there is no storage.
|
||||||
This cuts overall storage requirements in half compared to ElGamal/AES.
|
This cuts overall storage requirements in half compared to ElGamal/AES.
|
||||||
ECIES tags are 8 bytes instead of 32 for ElGamal/AES.
|
ECIES tags are 8 bytes instead of 32 for ElGamal/AES.
|
||||||
This cuts overall storage requiremens by another factor of 4.
|
This cuts overall storage requirements by another factor of 4.
|
||||||
Per-tag session keys are not stored at the receiver except for "gaps",
|
Per-tag session keys are not stored at the receiver except for "gaps",
|
||||||
which are minimal for reasonable loss rates.
|
which are minimal for reasonable loss rates.
|
||||||
|
|
||||||
Therefore, the total space savings vs. ElGamal/AES is a factor of 8, or 87%.
|
The 33% reduction in tag expiration time creates another 33% savings,
|
||||||
|
assuming short session times.
|
||||||
|
|
||||||
|
Therefore, the total space savings vs. ElGamal/AES is a factor of 10.7, or 92%.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user