Latest News

This release of I2P, 2.12.0, continues our work on improving the performance and security of the I2P network. It includes a number of bug fixes and improvements to the I2P software.

Work continues on the implementation of post-quantum cryptography. Improvements to the existing post-quantum implementations improve stability and interoperability with other I2P implementations. We encourage early adopters to continue testing and providing feedback to the I2P team.

A SAMv3 bug which was affecting applications by causing failed lookups has been fixed. Users of SAMv3 applications such as Bitcoin and Bittorrent clients should update to this release to resolve these issues.

For a detailed changelog, please see the local changelog.

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.

As of this release, I2P now requires Java 17 or later. Please consult your operating system's documentation for how to update Java. I2P now also uses Jetty 12. Please check your router logs for migration issues.

Work in this release continues to improve support for post-quantum cryptography. Post-Quantum crypto is now enabled at the ratchet layer by default.

We have implemented the first round of mitigations to the ongoing spam attacks. Additional mitigations are being developed.

The SAMv3 API has been upgraded to support new datagram types 2 and 3.

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.

The I2P network is currently experiencing instability due to ongoing Denial-of-Service and resource exhaustion attacks. These attacks are impacting the performance and reliability of I2P services and hidden sites. The I2P Development Team is actively investigating and implementing mitigations to counter these attacks.

Work continues on the implementation and deployment of post-quantum cryptography in I2P. In this release post-quantum cryptography is available but not turned on by default for new tunnels. Those of you interested in testing post-quantum support should enable it via the "Hidden Service Manager" under "Encryption Types." Be sure to get in touch on #i2p-dev in IRC2P for help and to report any issues you encounter.

I2PSnark now supports UDP trackers. This should help the network overall by reducing the load of torrent trackers.

Stability improvements have been made to the Hidden Mode which will reduce the chance of running out of RouterInfos.

Important! In the next release, I2P will require Java 17 or later.

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.9.0 is a maintenance release that includes bug fixes and work on new features.

Thread usage has been improved to improve the performance of the i2ptunnel system. NTCP2 has been improved to resist probing attacks. The notification system has been integrated into more applications to provide better feedback to users from I2PSnark and the other applications. Automatic floodfill enrollment has been fixed. Users may observe increased resource usage when acting as floodfill. If this is not desired, floodfill mode can be disabled on the /config page.

A new global map feature is available in the console which shows the locations of routers in your view of the netDb. These are the peers that help your router build tunnels and provide services anonymously.

Work continues on implementing automatic bandwidth management for tunnels, the Datagram2 protocol, and Post-Quantum cryptography. In two releases, at 2.11.0, I2P will require Java 17.

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.

2.8.2 fixes a bug causing SHA256 failures that was introduced in the 2.8.1 release. The bug primarily affected high-bandwidth routers.

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.

2.8.1 fixes accesses to local sites that were broken in 2.8.0. We have added notification bubbles to several applications in the console to highlight application messages. We fixed a tunnel test bug that may have been affecting tunnel reliability. The addressbook now has a new "latest" tab that displays the newest hostnames added from your subscriptions. There are several dark theme fixes and improvements.

We fixed the installer that previously failed on Java 21 or higher. We also fixed installing to directory paths that contain spaces on Linux. For those of you that use Docker, we updated outdated Docker container and container libraries.

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.

In 2.8.0, browsing to a local site (either by hostname or b32) will fail. The workaround is using localhost and the server port, usually 7658, to bypass I2P. For example, http://127.0.0.1:7658/. We apologize for the issue and are working on a fix.

This release improves I2P by fixing bugs, removing unused code, and improving network stability.

We have improved handling of congested routers in the network. Issues in UPnP and NAT traversal were addressed to improve connectivity and error reporting. We now have a more aggressive strategy for leaseset removal from the NetDb to improve router performance and mitigate overload. Other changes were implemented to reduce the observability of events like a router rebooting or shutting down.

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.

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

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

The I2P network is currently under a Denial-of-Service attack. This attack affects I2P and i2pd but in different ways and is having a serious effect on network health. Reachability of I2P sites is badly degraded.

If you are hosting a service inside I2P and it is hosted on a Floodfill router, you should consider multihoming the service on a Floodfill-disabled router to improve reachability. Other mitigations are being discussed but a long-term, backward-compatible solution is still being worked on.

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.

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.

This release contains fixes for CVE-2023-36325. CVE-2023-36325 is a context-confusion bug which occurred in the bloom filter. An attacker crafts an I2NP message containing a unique messageID, and sends that messageID to a client. The message, after passing through the bloom filter, is not allowed to be re-used in a second message. The attacker then sends the same message directly to the router. The router passes the message to the bloom filter, and is dropped. This leaks the information that the messageID has been seen before, giving the attacker a strong reason to believe that the router is hosting the client. This has been fixed by separting the bloom filter's functionality into different contexts based on whether a message came down a client tunnel, an exploratory tunnel, was sent to the router directly. Under normal circumstances, this attack takes several days to perform successfully and may be confounded by several factors such as routers restarting during the attack phase and sensitivity to false-positives. Users of Java I2P are recommended to update immediately to avoid the attack.

In the course of fixing this context confusion bug, we have revised some of our strategies to code defensively, against these types of leaks. This includes tweaks to the netDb, the rate-limiting mechanisms, and the behavior of floodfill routers.

This release adds not_bob as a second default hosts provider, and adds notbob.i2p and ramble.i2p to the console homepage.

This release also contains a tweakable blocklist. Blocklisting is semi-permanent, each blocked IP address is normally blocked until the router is restarted. Users who observe explosive blocklist growth during sybil attacks may opt-in to shorter timeouts by configuring the blocklist to expire entries at an interval. This feature is off-by-default and is only recommended for advanced users at this time.

This release also includes an API for plugins to modify with the Desktop GUI(DTG). It is now possible to add menu items to the system tray, enabling more intuitive launching of plugins which use native application interfaces.

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.

After the I2P 2.2.0 release, which was moved forward to accelerate mitigations for the DDOS attacks, we learned about a few developing issues which made it necessary to build and release new packages. This release fixes an issue within Ubuntu Lunar and Debian Sid where the router console was inaccessible using an updated version of the jakarta package. Docker packages were not reading arguments correctly, resulting in inaccessible configuration files. This issue has also been resolved. The docker container is now also compatible with Podman.

This release syncs translations with transifex and updates the GeoIP database.

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.

We have elected to move forward the 2.2.0 release date, which will be occurring today, March 13, 2023. This release includes a changes across the NetDB, Floodfill, and Peer-Selection components which improve the ability of the router to survive DDOS attacks. The attacks are likely to continue, but the improvements to these systems will help to mitigate the risk of DDOS attacks by helping the router identify and de-prioritize routers that appear malicious.

This release also adds replay protection to the Streaming subsystem, which prevents an attacker who can capture an encrypted packet from being able to re-use it by sending it to unintended recipients. This is a backward-compatible change, so older routers will still be able to use the streaming capabilities of newer routers. This issue was discovered and fixed internally, by the I2P development team, and is not related to the DDOS attacks. We have never encountered a replayed streaming packet in the wild and do not believe a streaming replay attack has ever taken place against the I2P network at this time.

As you may have noticed, these release notes and the release itself have been signed by idk, and not zzz. zzz has chosen to step away from the project and his responsibilities are being taken on by other team members. As such, the project is working on replacing the network statistics infrastructure and moving the development forum to i2pforum.i2p. We thank zzz for providing these services for such a long time.

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.

We have confirmed that the attacker controls a large number of routers. Our investigations and mitigations continue.

This is a good time to remind people that even after 20 years, the I2P network is relatively small. We have no evidence that the attacker is attempting to deanonymize any particular user or hidden service. However, if you have a high-risk threat model, you should carefully consider whether I2P currently provides the protection you require. The best solution, in the long run, is to spread the word and grow the I2P network to increase security of our users.

We will provide additional information here in the news feed and on zzz.i2p as necessary. We ask for your patience as we work to improve I2P.

The I2P network is currently being affected by a Denial of Service attack. The floodfill function of the network has been affected, resulting in responses being disrupted and tunnel build success rates dropping. Participants in the network have experienced difficulties connecting to I2P sites and using I2P services. Mitigation strategies are being investigated and implemented gradually.

While the attack has degraded performance, the network remains intact and usable. Java I2P routers appear to be handling the issues better than i2pd routers for now. Various mitigations should begin to appear in dev builds of both Java and C++ routers in the next week.

We have learned several things since our 2.0.0 release in November. As routers have updated to that release, the network has gone from about 1% to over 60% support for our new SSU2 transport protocol. First, we have confirmed that SSU2 is a solid, well designed, and secure protocol. Second, however, we have found and fixed numerous minor or rarely-triggered bugs in the implementation of the protocol. Cumulatively, the effects of these bugs have reduced the performance of the network.

Also, we are aware of increased tunnel count and reduced tunnel build success rate in the network, possibly triggered by Bitcoin's new I2P transient address feature, but made worse by our SSU2 bugs and other congestion control problems. We are working with Bitcoin and other non-Bitcoin projects to reduce I2P network demands. We have improved our algorithms to reduce network load during times of congestion. We are also collaborating with i2pd to develop common congestion control strategies.

Therefore, we have accelerated this release by about six weeks, to get the fixes out to everybody. i2pd released their version 2.45.0 last week and the early results are encouraging. New protocols, and distributed networks, are difficult to develop. Congestion can arrive with little warning and with little clue of the cause. Thank you for your patience as we have diagnosed and hopefully fixed the problems.

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 release 2.0.0 enables our new UDP transport SSU2 for all users, after completion of minor features, testing, and numerous bug fixes.

We also have fixes all over, including for the installer, network database, adding to the private address book, the Windows browser launcher, and IPv6 UPnP.

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.

Here's links to several recent blog posts on our website:

• Overview of our new SSU2 transport
• A warning about I2P coins and other scams
• An interview with Konrad from diva.exchange
• An interview with Dustin from StormyCloud

We have spent the last three months working on our new UDP transport protocol "SSU2" with a small number of volunteer testers. This release completes the implementation, including relay and peer testing. We are enabling it by default for Android and ARM platforms, and a small percentage of other routers at random. This will allow us to do much more testing in the next three months, finish the connection migration feature, and fix any remaining issues. We plan to enable it for everyone in the next release scheduled for November. No manual configuration is necessary.

Of course, there's the usual collection of bug fixes in this release as well. We also added an automatic deadlock detector that has already found a rare deadlock that is now fixed.

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 "outproxies" (exit nodes) may be used to access the internet through your HTTP proxy tunnel. As approved at our monthly meeting, exit.stormycloud.i2p is now our official, recommended outproxy, replacing the long-dead false.i2p. For more information on the StormyCloud organization, outproxy, and terms of service, see the StormyCloud website.

We suggest you change your Hidden Services Manager configuration to specify exit.stormycloud.i2p in two places: Outproxies and SSL Outproxies. After editing, scroll down and click Save. See our blog post for a screenshot. For Android instructions and screenshots see notbob's blog.

Router updates will not update your configuration, you must edit it manually. Thanks to StormyCloud for their support, and please consider a donation.

This release includes bug fixes in i2psnark, the router, I2CP, and UPnP. Router fixes address bugs in soft restart, IPv6, SSU peer testing, network database stores, and tunnel building. Router family handling and Sybil classification have also been significantly improved.

Together with i2pd, we are developing our new UDP transport, SSU2. SSU2 will bring substantial performance and security improvements. It will also allow us to finally replace our last usage of the very slow ElGamal encryption, completing the full cryptography upgrade we started about 9 years ago. This release contains a preliminary implementation which is disabled by default. If you wish to participate in testing, please look for current information on zzz.i2p.

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.

The recent Java "Psychic Signatues" vulnerability affects I2P. Current users of I2P on Linux, or any users of I2P who are using a non-bundled JVM should update their JVM or switch to a version which does not contain the vulnerability, below Java 15.

New I2P Easy-Install bundles have been generated using the latest release of the Java Virtual Machine. Further details have been published in the respective bundle newsfeeds.

The 1.7.0 release contains several performance and reliability improvements.

There are now popup messages in the system tray, for those platforms that support it. i2psnark has a new torrent editor. The NTCP2 transport now uses much less CPU.

The long-deprecated BOB interface is removed for new installs. It will continue to work in existing installs, except for Debian packages. Any remaining users of BOB applications should ask the developers to convert to the SAMv3 protocol.

We know that since our 1.6.1 release, network reliability has steadily deteriorated. We were aware of the problem soon after the release, but it took us almost two months to find the cause. We eventually identified it as a bug in i2pd 2.40.0, and the fix will be in their 2.41.0 release coming out about the same time as this release. Along the way, we've made several changes on the Java I2P side to improve the robustness of network database lookups and stores, and avoid poorly-performing peers in tunnel peer selection. This should help the network be more robust even in the presence of buggy or malicious routers. Additionally, we're starting a joint program to test pre-release i2pd and Java I2P routers together in an isolated test network, so we can find more problems before the releases, not after.

In other news, we continue to make great progress on the design of our new UDP transport "SSU2" (proposal 159) and have started implementation. SSU2 will bring substantial performance and security improvements. It will also allow us to finally replace our last usage of the very slow ElGamal encryption, completing a full cryptography upgrade that started about 9 years ago. We expect to start joint testing with i2pd soon, and roll it out to the network later this year.

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.

This release completes the rollout of two major protocol updates developed in 2021. The transition to X25519 encryption for routers is accelerated, and we expect almost all routers to be rekeyed by the end of the year. Short tunnel build messages are enabled for a significant bandwidth reduction.

We added a theme selection panel to the new install wizard. We've improved SSU performance and fixed an issue with SSU peer test messages. The tunnel build Bloom filter was adjusted to reduce memory usage. We have enhanced support for non-Java plugins.

In other news, we are making excellent progress on the design of our new UDP transport SSU2 and expect to start implementation early next year.

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.

Yes, that's right, after 9 years of 0.9.x releases, we are going straight from 0.9.50 to 1.5.0. This does not signify a major API change, or a claim that development is now complete. It is simply a recognition of almost 20 years of work to provide anonymity and security for our users.

This release finishes implementation of smaller tunnel build messages to reduce bandwidth. We continue the transition of the network's routers to X25519 encryption. Of course there are also numerous bug fixes and performance improvements.

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.

A security vulnerability has been discovered in the MuWire standalone desktop application. It does not affect the console plugin, and is not related to the previously-announced plugin issue. If you are running the MuWire desktop application you should update to version 0.8.8 immediately.

Details of the issue will be published on muwire.i2p on July 15, 2021.

A security vulnerability has been discovered in the MuWire plugin. It does not affect the standalone desktop client. If you are running the MuWire plugin you should update to version 0.8.7-b1 immediately.

See muwire.i2p for more information about the vulnerability and updated security recommendations.

0.9.50 continues the transition to ECIES-X25519 for router encryption keys. We have enabled DNS over HTTPS for reseeding to protect users from passive DNS snooping. There are numerous fixes and improvements for IPv6 addresses, including new UPnP support.

We have finally fixed some longstanding SusiMail corruption bugs. Changes to the bandwidth limiter should improve network tunnel performance. There are several improvements in our Docker containers. We have improved our defenses for possible malicious and buggy routers in the network.

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.

0.9.49 continues the work to make I2P faster and more secure. We have several improvements and fixes for the SSU (UDP) transport that should result in faster speeds. This release also starts the migration to new, faster ECIES-X25519 encryption for routers. (Destinations have been using this encryption for a few releases now) We've been working on the specifications and protocols for new encryption for several years, and we are getting close to the end of it! The migration will take several releases to complete.

For this release, to minimize disruption, only new installs and a very small percentage of existing installs (randomly selected at restart) will be using the new encryption. If your router does "rekey" to use the new encryption, it may have lower traffic or less reliability than usual for several days after you restart. This is normal, because your router has generated a new identity. Your performance should recover after a while.

We have "rekeyed" the network twice before, when changing the default signature type, but this is the first time we've changed the default encryption type. Hopefully it will all go smoothly, but we're starting slowly to be sure.

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.

0.9.48 enables our new end-to-end encryption protocol (proposal 144) for most services. We have added preliminary support for new tunnel build message encryption (proposal 152). There are significant performance improvements throughout the router.

Packages for Ubuntu Xenial (16.04 LTS) are no longer supported. Users on that platform should upgrade so you may continue to receive I2P updates.

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.

0.9.47 enables our new end-to-end encryption protocol (proposal 144) by default for some services. The Sybil analysis and blocking tool is now enabled by default.

Java 8 or higher is now required. Debian packages for Wheezy and Stretch, and for Ubuntu Trusty and Precise, are no longer supported. Users on those platforms should upgrade so you may continue to receive I2P updates.

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.

0.9.46 contains significant performance improvements in the streaming library. We have completed development of ECIES encryption (proposal 144) and there is now an option to enable it for testing.

Windows users only: This release fixes a local privilege escalation vulnerability which could be exploited by a local user. Please apply the update as soon as possible. Thanks to Blaze Infosec for responsible disclosure of the issue.

This is the last release to support Java 7, Debian packages Wheezy and Stretch, and Ubuntu packages Precise and Trusty. Users on those platforms must upgrade to receive future I2P updates.

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.

0.9.45 contains important fixes for hidden mode and the bandwidth tester. There's an update to the console dark theme. We continue work on improving performance and the development of new end-to-end encryption (proposal 144).

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.

0.9.44 contains an important fix for a denial of service issue in hidden services handling of new encryption types. All users should update as soon as possible.

The release includes initial support for new end-to-end encryption (proposal 144). Work continues on this project, and it is not yet ready for use. There are changes to the console home page, and new embedded HTML5 media players in i2psnark. Additional fixes for firewalled IPv6 networks are included. Tunnel build fixes should result in faster startup for some users.

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.

In the 0.9.43 release, we continue work on stronger security and privacy features and performance improvements. Our implementation of the new leaseset specification (LS2) is now complete. We are beginning our implementation of stronger and faster end-to-end encryption (proposal 144) for a future release. Several IPv6 address detection issues have been fixed, and there of course are several other bug fixes.

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.

0.9.42 continues the work to make I2P faster and more reliable. It includes several changes to speed up our UDP transport. We have split up the configuration files to enable future work for more modular packaging. We continue work to implement new proposals for faster and more secure encryption. There are, of course, a lot of bug fixes also.

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.

0.9.41 continues the work to implement new features for proposal 123, including per-client authentication for encrypted leasesets. The console has an updated I2P logo and several new icons. We've updated the Linux installer.

Startup should be faster on platforms such as Raspberry Pi. We've fixed several bugs, including some serious ones affecting low-level network messages.

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.

0.9.40 includes support for the new encrypted leaseset format. We disabled the old NTCP 1 transport protocol. There's a new SusiDNS import feature, and a new scripted filtering mechanism for incoming connections.

We've made a lot of improvements to the OSX native installer, and we've updated the IzPack installer as well. The work continues on refreshing the console with new icons. As usual, we've fixed lots of bugs also!

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.

0.9.39 includes extensive changes for the new network database types (proposal 123). We've bundled the i2pcontrol plugin as a webapp to support development of RPC applications. There are numerous performance improvements and bug fixes.

We've removed the midnight and classic themes to reduce the maintenance burden; previous users of those themes will now see the dark or light theme. There's also new home page icons, a first step in updating the console.

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.

0.9.38 includes a new first-install wizard with a bandwidth tester. We've added support for the latest GeoIP database format. There's a new Firefox profile installer and a new, native Mac OSX installer on our website. Work continues on supporting the new "LS2" netdb format.

This release also contains plenty of bug fixes, including several issues with susimail attachments, and a fix for IPv6-only routers.

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.

The I2P team was mostly all in attendance at 35C3 in Leipzig. Daily meetings were held to review the past year and cover our development and design goals for 2019.

The Project Vision and new Roadmap can be reviewed here.

Work will continue on LS2, the Testnet, and usability improvements to our website and console. A plan is in place to be in Tails, Debian and Ubuntu Disco. We still need people to work on Android and I2P_Bote fixes.

0.9.37 enables a faster, more secure transport protocol called NTCP2.

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.

0.9.36 contains a new, more secure transport protocol called NTCP2. It is disabled by default, but you may enable it for testing by adding the advanced configurationi2np.ntcp2.enable=true and restarting. NTCP2 will be enabled in the next release.

This release also contains several performance improvements and bug fixes.

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.

0.9.35 adds support for folders in SusiMail, and a new SSL Wizard for setting up HTTPS on your Hidden Service website. We also have the usual collection of bug fixes, especially in SusiMail.

We're hard at work on several things for 0.9.36, including a new OSX installer and a faster, more secure transport protocol called NTCP2.

I2P will be at HOPE in New York City, July 20-22. Find us and say hello!

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.

0.9.34 contains a lot of bug fixes! It also has improvements in SusiMail, IPv6 handling, and tunnel peer selection. We add support for IGD2 schemas in UPnP. There's also preparation for more improvements you will see in future releases.

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.

0.9.33 contains a large number of bug fixes, including i2psnark, i2ptunnel, streaming, and SusiMail. For those who cannot access the reseed sites directly, we now support several types of proxies for reseeding. We now set rate limits by default in the hidden services manager. For those that run high-traffic servers, please review and adjust the limits as necessary.

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.

Happy new year from the I2P team to everyone!

No less than 7 I2P team members did meet at the 34C3 in Leipzig from 27th til 30th december 2017. Beside the meetings at our table we did meet lots of friends of I2P all over the place. Results of the meetings are posted on zzz.i2p already.

Also we did hand out lots of stickers and gave information about our project to anyone asking. Our annual I2P dinner was a full success as a thank you to all attendees for ongoing support of I2P.

0.9.32 contains a number of fixes in the router console and associated webapps (addressbook, i2psnark, and susimail). We have also changed the way we handle configured hostnames for published router infos, to eliminate some network enumeration attacks via DNS. We have added some checks in the console to resist rebinding attacks.

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.

The changes in this release are much more noticeable than usual! We have refreshed the router console to make it easier to understand, improved accessibility and cross-browser support, and generally tidied things up. This is the first step in a longer-term plan to make the router console more user-friendly. We have also added torrent ratings and comments support to i2psnark.

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.

In preparation for the 0.9.31 release, which brings with it significant updates to the user interface, we have a larger than normal collection of untranslated strings that need attention. If you're a translator, we would greatly appreciate it if you could set aside a little more time than usual during this release cycle in order to bring the translations up to speed. We have pushed the strings early to give you three weeks to work on them.

If you're not currently an I2P translator, now would be a great time to get involved! Please see the New Translator's Guide for information on how to get started.

0.9.30 contains an upgrade to Jetty 9 and Tomcat 8. The previous versions are no longer supported, and are not available in the upcoming Debian Stretch and Ubuntu Zesty releases. The router will migrate the jetty.xml configuration file for each Jetty website to the new Jetty 9 setup. This should work for recent, unmodified configurations but may not work for modified or very old setups. Verify that your Jetty website works after upgrading, and contact us on IRC if you need assistance.

Several plugins are not compatible with Jetty 9 and must be updated. The following plugins have been updated to work with 0.9.30, and your router should update them after restart: i2pbote 0.4.6; zzzot 0.15.0. The following plugins (with current versions listed) will not work with 0.9.30. Contact the appropriate plugin developer for the status of new versions: BwSchedule 0.0.36; i2pcontrol 0.11.

This release also supports migration of old (2014 and earlier) DSA-SHA1 hidden services to the more-secure EdDSA signature type. See zzz.i2p for further information, including a guide and FAQ.

Note: On non-Android ARM platforms such as the Raspberry Pi, the blockfile database will upgrade on restart, which may take several minutes. Please be patient.

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.

0.9.29 contains fixes for numerous Trac tickets, including workarounds for corrupt compressed messages. We now support NTP over IPv6. We've added preliminary Docker support. We now have translated man pages. We now pass same-origin Referer headers through the HTTP proxy. There are more fixes for Java 9, although we do not yet recommend Java 9 for general use.

As usual, we recommend that all users update to this release. The best way to help the network and stay secure is to run the latest release.

I2P-Bote 0.4.5 fixes a security vulnerability present in all earlier versions of the I2P-Bote plugin. The Android app was not affected.

When showing emails to the user, most fields were being escaped. However, the filenames of attachments were not escaped, and could be used to execute malicious code in a browser with JavaScript enabled. These are now escaped, and additionally a Content Security Policy has been implemented for all pages.

All I2P-Bote users will be upgraded automatically the first time they restart their router after I2P 0.9.29 is released in mid-February. However, for safety we recommend that you follow the instructions on the installation page to upgrade manually if you plan on using I2P or I2P-Bote in the intervening time.

0.9.28 contains fixes for over 25 Trac tickets, and updates for a number of bundled software packages including Jetty. There are fixes for the IPv6 peer testing feature introduced last release. We continue improvements to detect and block peers that are potentially malicious. There are preliminary fixes for Java 9, although we do not yet recommend Java 9 for general use.

I2P will be at 33C3, please stop by our table and give us your ideas on how to improve the network. We will review our 2017 roadmap and priorities 2017 at the Congress.

As usual, we recommend that all users update to this release. The best way to help the network and stay secure is to run the latest release.

I2P-Bote 0.4.4 fixes a security vulnerability present in all earlier versions of the I2P-Bote plugin. The Android app was not affected.

A lack of CSRF protection meant that if a user was running I2P-Bote and then loaded a malicious site in a browser with JavaScript enabled, the adversary could trigger actions in I2P-Bote on behalf of the user, such as sending messages. This might also have enabled extraction of private keys for I2P-Bote addresses, however no proof-of-exploit was tested for this.

All I2P-Bote users will be upgraded automatically the first time they restart their router after I2P 0.9.28 is released in mid-December. However, for safety we recommend that you follow the instructions on the installation page to upgrade manually if you plan on using I2P or I2P-Bote in the intervening time. You should also consider generating new I2P-Bote addresses if you regularly browse sites with JavaScript enabled while running I2P-Bote.

0.9.27 contains a number of bug fixes. The updated GMP library for crypto acceleration, which was bundled in the 0.9.26 release for new installs and Debian builds only, is now included in the in-network update for 0.9.27. There are improvements in IPv6 transports, SSU peer testing, and hidden mode.

We updated a number of plugins during I2P Summer and your router will automatically update them after restart.

As usual, we recommend that all users update to this release. The best way to help the network and stay secure is to run the latest release.

I2P is now a proposed site on Stack Exchange! Please commit to using it so the beta phase can begin.

0.9.26 contains a major upgrade to our native crypto library, a new addressbook subscription protocol with signatures, and major improvements to the Debian/Ubuntu packaging.

For crypto, we have upgraded to GMP 6.0.0, and added support for newer processors, which will speed up crypto operations considerably. Also, we are now using constant-time GMP functions to prevent side-channel attacks. For caution, the GMP changes are enabled for new installs and Debian/Ubuntu builds only; we will include them for in-net updates in the 0.9.27 release.

For Debian/Ubuntu builds, we have added dependencies on several packages, including Jetty 8 and geoip, and removed the equivalent bundled code.

There's a collection of bug fixes also, including a fix for a timer bug that caused instability and performance degradations over time. As usual, we recommend that all users update to this release. The best way to help the network and stay secure is to run the latest release.

0.9.25 contains a major new version of SAM, v3.3, to support sophisticated multiprotocol applications. It adds QR codes for sharing hidden service addresses with others, and "identicon" images for visually distinguishing addresses.

We've added a new "router family" configuration page in the console, to make it easier to declare that your group of routers is run by a single person. There are several changes to increase the capacity of the network and hopefully improve tunnel build success.

As usual, we recommend that all users update to this release. The best way to help the network and stay secure is to run the latest release.

0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and efficiency improvements. Note that this release is the first to require Java 7. Please update to Java 7 or 8 as soon as possible. Your router will not automatically update if you are using Java 6.

To prevent the problems caused by the ancient commons-logging library, we have removed it. This will cause very old I2P-Bote plugins (0.2.10 and below, signed by HungryHobo) to crash if they have IMAP enabled. The recommended fix is to replace your old I2P-Bote plugin with the current one signed by str4d. For more details, see this post.

We had a great 32C3 Congress and are making good progress on our 2016 project plans. Echelon gave a talk on I2P's history and current status, and his slides are here (pdf). Str4d attended Real World Crypto and gave a talk on our crypto migration, his slides are here (pdf).

As usual, we recommend that all users update to this release. The best way to help the network and stay secure is to run the latest release.

Hello I2P! This is the first release signed by me (str4d), after 49 releases signed by zzz. This is an important test of our redundancy for all things, including people.

Housekeeping

My signing key has been in router updates for over two years (since 0.9.9), so if you are on a recent version of I2P this update should be just as easy as every other update. However, if you are running an older version than 0.9.9, you will first need to manually update to a recent version. Update files for recent versions can be downloaded here, and instructions on how to manually update are provided here. Once you have manually updated, your router will then find and download the 0.9.23 update as usual.

If you installed I2P via a package manager, you are not affected by the change, and can update as usual.

Update details

The migration of RouterInfos to new, stronger Ed25519 signatures is going well, with at least half of the network already estimated to have rekeyed. This release accelerates the rekeying process. To reduce network churn, your router will have a small probability of converting to Ed25519 at each restart. When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity.

Note that this will be the last release to support Java 6. Please update to Java 7 or 8 as soon as possible. We are already working to make I2P compatible with the upcoming Java 9, and some of that work is in this release.

We have also made some minor improvements in I2PSnark, and added a new page in the routerconsole for viewing older news items.

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.

0.9.22 contains fixes for i2psnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures. To reduce network churn, your router will have only a small probability of converting to Ed25519 at each restart. When it does rekey, expect to see lower bandwidth usage for a couple of days as it reintegrates into the network with its new identity. If all goes well, we will accelerate the rekeying process in the next release.

I2PCon Toronto was a big success! All the presentations and videos are listed on the I2PCon page.

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.

0.9.21 contains several changes to add capacity to the network, increase the efficiency of the floodfills, and use bandwidth more effectively. We have migrated the shared clients tunnels to ECDSA signatures and added a DSA fallback using the new "multisession" capability for those sites that don't support ECDSA.

The speakers and the schedule of the I2PCon in Toronto 2015 have been announced. Have a look on the I2PCon page for details. Reserve your seat on Eventbrite I2PCon.

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.

The speakers and the schedule of the I2PCon in Toronto 2015 have been announced. Have a look on the I2PCon page for details. Reserve your seat on Eventbrite I2PCon.

Welcome to I2P! Please have patience as I2P boots up and finds peers.

While you are waiting, please adjust your bandwidth settings on the configuration page.

Also you can setup your browser to use the I2P proxy to reach eepsites. Just enter 127.0.0.1 (or localhost) port 4444 as a http proxy into your browser settings. Do not use SOCKS for this. More information can be found on the I2P browser proxy setup page.

Once you have a "shared clients" destination listed on the left, please check out our FAQ.

Point your IRC client to localhost:6668 and say hi to us on #i2p.