Skip to content

Releases: i2p/i2p.i2p

I2P 2.7.0 Release

09 Oct 00:29
Compare
Choose a tag to compare

This release, I2P 2.7.0, continues our work by fixing bugs, improving performance, and adding features.

Access to information from the console and applications has been improved.
Issues have been fixed in I2PSnark and SusiMail search.
The netDB search embedded into the router console now operates in a more intuitive and useful way.
Minor improvements have been made to diagnostic displays in advanced mode.

Bugs have also been fixed to improve compatibility within the network.
An issue with publishing leaseSets was solved which improves reliability major hidden services.
I2PSnark no longer changes the infohash when a user changes only the trackers on an existing torrent.
This prevents torrents from being unnecessarily disrupted by these changes.
We welcomed this contribution from a new contributor.
A conflict in the handling of a streaming library option was resolved to improve compatibility with other I2P implementations.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.

I2P 2.6.1 Release

19 Aug 20:00
Compare
Choose a tag to compare

I2P 2.6.1 is released in order to fix a User-Interface bug in the Hidden Services Manager application.
This bug caused scrolling to be disabled, rendering some configuration inaccessible.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.

I2P 2.6.0 Release

19 Jul 17:46
Compare
Choose a tag to compare

This release, I2P 2.6.0, continues our work by fixing bugs, adding features, and improving the network's reliability.

Newer routers will be favored when selecting floodfill routers.
I2PSnark received features which improve the performance of PeX(Peer Exchange), in addition to bug fixes.
Legacy transport protocols are being removed, simplifying the code in the UDP transports.
Locally-hosted destination will be reachable by local clients without requesting their LeaseSet, improving performance and testability.
Additional tweaks were made to peer selection strategies.

I2P no longer allows I2P-over-Tor, connections from Tor exit IP addresses are now blocked.
We discourage this because it degrades the performance of I2P and uses up the resources of Tor exits for no benefit.
If you are a helpful person running both a Tor Exit and I2P we encourage you to continue to do so, using different IP addresses for each.
Non-exit relays and Tor clients are unaffected by this and do not need to change anything.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.

I2P 2.5.2

27 Jun 23:54
i2p-2.5.2
84971f6
Compare
Choose a tag to compare

I2P 2.5.2 is released to fix a bug introduced in 2.5.0 causing truncation of some HTTP content.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.

I2P 2.5.1 Point Release

06 May 20:08
Compare
Choose a tag to compare

I2P 2.5.1 Point Release

I2P 2.5.1 is released to address Denial-of-Service Attacks affecting the I2P network and services.
With this release we disable the IP-based parts of the Sybil attack detection tool which were targeted to amplify the effect and duration of the attack.
This should help the network return to normal operation.
Those of you who have disabled the Sybil attack detection tool may safely re-enable it.
Adjustments to other subsystems to improve RouterInfo validation and peer selection have also been made.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.

More Application Improvements, Audit of NetDB Isolation strategy

08 Apr 15:06
Compare
Choose a tag to compare

This release, I2P 2.5.0, provides more user-facing improvements than the 2.4.0 release, which was focused on implementing the NetDB isolation strategy.

New features have been added to I2PSnark like the ability to search through torrents.
Bugs have been fixed to improve compatibility with other I2P torrent clients like BiglyBT and qBittorrent.
We would like to thank all of the developers who have worked with libtorrent and qBittorrent to enable and improve their I2P support.
New features have also been added to SusiMail including support for Markdown formatting in emails and the ability to drag-and-drop attachments into emails.
Tunnels created with the Hidden Services manager now support "Keepalive" which improves performance and compatibility with web technologies, enabling more sophisticated I2P sites.

During this release we also made several tweaks to the NetDB to improve its resilience to spam and to improve the router's ability to reject suspicious messages.
This was part of an effort to "audit" the implementation of "Sub-DB isolation" defenses from the 2.4.0 release.
This investigation uncovered one minor isolation-piercing event which we repaired.
This issue was discovered and fixed internally by the I2P team.

During this release several improvements were made to the process of releasing our downstream distributions for Android and Windows.
This should result in improved delivery and availability for these downstream products.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.

I2P 2.4.0-10rc **Release Candidate**

06 Apr 03:03
bbf1e41
Compare
Choose a tag to compare
Pre-release

I2P 2.4.0-10rc Release Candidate

This dev build includes all the new features planned for I2P 2.5.0, including:

  • Improvements and bugfixes in Susimail
  • Changes to inbound message handling
  • Audit of netDb sub-db implementation
  • Tunnel Test Changes, Narrow circumstances where peer tests happen
  • Bugfixes and improvements to I2PSnark
  • Bugfixes and improvements to I2PTunnel

Help us test this release candidate

If you want to help, you can get a dev build at our official Github:

We depend on bug reports and feedback

Please reach out:

I2P 2.4.0-4 Dev Build

17 Jan 14:39
ce5c75c
Compare
Choose a tag to compare
I2P 2.4.0-4 Dev Build Pre-release
Pre-release
SSU2: Drop small packets in UDPReceiver

now that SSU1 is disabled.
SSU2 min packet size is 40 and does not support 0-byte hole punch

I2P 2.4.0-3 **Dev Build**

12 Jan 12:36
Compare
Choose a tag to compare
Pre-release

This development build showcases some of the new features and improvements
to the I2P router. Please help us test these changes incrementally while
we work on the 2.5.0 release.

Help us test this release candidate

If you want to help, you can get a dev build at our official Github:

We depend on bug reports and feedback

The I2P network is getting some big upgrades this release and we're
excited to get them out to you. Please help us make the router better
by reporting your bugs.

Please reach out to us at:

I2P 2.4.0 Release with Congestion and NetDB Security improvements

18 Dec 18:13
Compare
Choose a tag to compare

This release, I2P 2.4.0, continues our effort to improve the security and stability of the I2P network.
It contains significant improvements to the Network Database, an essential structure within the I2P network used for disovering your peers.

The congestion handling changes will improve network stability by giving routers the ability to relieve congested peers by avoiding them.
This will help the network limit the effect of tunnel spam.
It will also help the network heal during and after DDOS attacks.

The NetDb changes also help secure individual routers and the applications that use them.
Routers can now defend against attackers by separating the NetDB into multiple "Sub-DB's" which we use to prevent information leaks between applications and the router.
This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.

Also included are a number of bug-fixes and enhancements across the I2PSnark and SusiMail applications.

As usual, we recommend that you update to this release.
The best way to maintain security and help the network is to run the latest release.