I2P Address: [http://git.idk.i2p]

Skip to content
Snippets Groups Projects
Commit 1013665c authored by zzz's avatar zzz
Browse files

0.9.8 backup news

parent 2c12e914
No related branches found
No related tags found
No related merge requests found
<!--
<i2p.news date="$Date: 2013-08-10 00:00:00 $">
<i2p.release version="0.9.7.1" date="2013/08/10" minVersion="0.6" su2Torrent="magnet:?xt=urn:btih:837087d7817bc9ca35174e03d1b32ce774c3cc62&dn=i2pupdate-0.9.7.1.su2&tr=http://tracker2.postman.i2p/announce.php" />
<i2p.news date="$Date: 2013-09-30 00:00:00 $">
<i2p.release version="0.9.8" date="2013/09/30" minVersion="0.6" su2Torrent="magnet:?xt=urn:btih:e988b1ed282bd8e283efb5aea3a6b782b9575c86&dn=i2pupdate-0.9.8.su2&tr=http://tracker2.postman.i2p/announce.php" />
-->
<div lang="en">
<h3>2013-08-10: <b>0.9.7.1 <a href="http://www.i2p2.i2p/release-0.9.7.1.html">Released</a></b></h3>
<p>This unscheduled release disables the RouterInfo verification messages that were used in the
<a href="http://wwwcip.informatik.uni-erlangen.de/~spjsschl/i2p.pdf">UCSB "practical attacks" paper</a>,
which should make correlating a LeaseSet and a Router much more difficult.
We have also included a limited number of other fixes listed below.
Our 0.9.8 release, which will include IPv6 support, is still on-schedule for late September.
As usual, we recommend that all users update to this release.
<h3>2013-09-30: <b>0.9.8 <a href="http://www.i2p2.i2p/release-0.9.8.html">Released</a></b></h3>
<p>0.9.8 includes the long-awaited support for IPv6. It's enabled by default,
but of course you need a public IPv6 address to use it. Configuration is on the
"network" configuration tab in your console.
We also have anonymity improvements including padding of SSU packets and
longer router private keys.</p>
<p>If you have a public IPv6 address
and you are connecting to another router with a published IPv6 address, it will
connect via IPv6. There is a new IPv6 configuration section on <a href="/confignet">/confignet</a>.
If IPv6 is causing problems you may disable it there.</p>
<p>For those of you running I2P on faster hardware (generally, 64-bit x86) the
router will generate a new identity using longer keys. This will substantially
reduce your participating traffic for 48 hours or more, while your router
re-integrates into the network. Due to the new keys, the large number of
torrent updates, and the recent network growth, we expect substantial
disruption to the network for a week or more after the update is released.
Please be patient and things should start to improve after a few days.</p>
<p>We are experiencing rapid network growth in the last few weeks, which is
causing a bit of a bumpy ride for some, especially on weekends. The
network is still performing fairly well, so keep spreading the word.
See the <a href="http://www.i2p2.i2p/release-0.9.8.html">release notes</a>
for more information on IPv6 and rekeying, and
please report any bugs on
<a href="http://trac.i2p2.i2p/report/1">trac.i2p2.i2p</a>.
</p>
</div>
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment