diff --git a/i2p2www/pages/site/docs/how/cryptography.html b/i2p2www/pages/site/docs/how/cryptography.html index 19a0add8..7aca16ce 100644 --- a/i2p2www/pages/site/docs/how/cryptography.html +++ b/i2p2www/pages/site/docs/how/cryptography.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}Low-level Cryptography Details{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}December 2013{% endtrans %}{% endblock %} -{% block accuratefor %}0.9.9{% endblock %} +{% block lastupdated %}{% trans %}March 2014{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.12{% endblock %} {% block content %}

{% trans -%} This page specifies the low-level details of the cryptography in I2P. @@ -363,10 +363,6 @@ As such, we do not know if the prime chosen is a 'strong prime'. If a larger prime is chosen for future purposes, this should be a strong prime, and we will document the construction process. {%- endtrans %}

-

{% trans -%} -The vulnerability of the network to a DSA attack and the impact of transitioning to longer keys is to be studied. -It may be quite difficult to make any change backward-compatible. -{%- endtrans %}

{% trans %}References{% endtrans %}

+ +

{% trans %}New Signature Algorithms{% endtrans %}

+

{% trans -%} +As of release 0.9.12, the router supports additional signature algorithms that are more secure than 1024-bit DSA. +The first usage is for Destinations; support for Router Identities will be added in a future release. +Support for migrating existing Destinations from old to new signatures will be added in a future release. +The supported signature types are as follows. Additional signature types will be added in future releases. +{%- endtrans %}

+ + + +

SHA256

{% trans code='https://github.com/i2p/i2p.i2p/tree/master/core/java/src/net/i2p/crypto/SHA256Generator.java' -%} diff --git a/i2p2www/pages/site/docs/how/elgamal-aes.html b/i2p2www/pages/site/docs/how/elgamal-aes.html index 9c44a9c3..6ab23d51 100644 --- a/i2p2www/pages/site/docs/how/elgamal-aes.html +++ b/i2p2www/pages/site/docs/how/elgamal-aes.html @@ -1,7 +1,7 @@ {% extends "global/layout.html" %} {% block title %}{% trans %}ElGamal/AES + SessionTag Encryption{% endtrans %}{% endblock %} -{% block lastupdated %}{% trans %}February 2011{% endtrans %}{% endblock %} -{% block accuratefor %}0.8.3{% endblock %} +{% block lastupdated %}{% trans %}March 2014{% endtrans %}{% endblock %} +{% block accuratefor %}0.9.12{% endblock %} {% block content %}

{% trans %}Overview{% endtrans %}

{% trans -%} @@ -328,6 +328,18 @@ If the tag is not found, the message is assumed to be a New Sessi +

{% trans %}Session Tag Configuration Options{% endtrans %}

+

{% trans i2cp=site_url('docs/protocol/i2cp#options') i2cpp=site_url('docs/spec/i2cp#msg_SendMessageExpires') -%} +As of release 0.9.2, the client may configure the default number of Session Tags to send +and the low tag threshold for the current session. +For brief streaming connections or datagrams, these options may be used to significantly reduce bandwidth. +See the I2CP options specification for details. +The session settings may also be overridden on a per-message basis. +See the I2CP Send Message Expires specification for details. +{%- endtrans %}

+ + +

{% trans %}Future Work{% endtrans %}

{% trans -%} There are many possible areas to tune the Session Key Manager's algorithms; @@ -335,21 +347,6 @@ some may interact with the streaming library behavior, or have significant impact on overall performance. {%- endtrans %}