I2P is an anonymous P2P network that protects from online censorship, surveillance and monitoring.
A few days ago it was announced release of the new version of the I2P project 2.4.0 in which they have been carried out significant improvements to the network database, they were implemented changes in NetDb to protect individual routers and simplify support for multihoming applications, as well as also various security improvements and bug fixes.
For those who are unaware of the I2P Invisible Internet Project, this is a project that provides users with an option to access the internet anonymously, similar to Tor, but it has differences from this, because while Tor uses layers of encryption, I2P uses "garlic" routing, where messages are grouped into data packets called "garlic cloves." Unlike Tor's layered method, which allows outside observers to guess the timing of messages, I2P's method avoids this possibility.
I2P has a limited ability to provide access to superficial information on the web. Instead, it stands out for its ability to create exclusive sites on the Dark Web, called eepsites, comparable to Tor sites. These eepsites allow users to perform actions such as sending secure messages or hiding their geolocation from external Internet users.
What's new in I2P 2.4.0?
In this new version that is presented of I2P 2.4.0 stands out the best significant in the network database and Among the changes made, it stands out in the Congestion management will improve network stability, allowing routers to avoid congested peers and limit the impact of tunnel spam.
In addition to it, the SSU1 transport protocol has been disabled, which is already classified as obsolete and replaced by the SSU2 protocol and the handling of overload cases and has been implemented the ability to transfer load from overloaded peers to other nodes, which has increased network resilience during DDoS attacks.
Regarding the security improvements, it is highlighted that they include the Bug fixes and improvements to I2PSnark and SusiMail applications, as well as the ability to temporarily lock routers.
Another security improvement, is the one implemented in the individual routers and the applications that use them. To prevent information leaks between routers and applications, the database NetDB is divided into two isolated databases, one for routers and one for applications.
It is mentioned that routers can now "defend against attackers by separating NetDB into multiple Sub-DBs." This also improves the information available to Java routers about their NetDB activity and simplifies our support for multihoming applications.
Of the other changes that stand out from this new version:
- i2pd now supports Haiku OS.
- Fixed sidebar not immediately displaying manual update check results
- Fixed radio/checkbox visibility (light theme)
- Sidebar state overflow prevented
- Increased comment repository size to reduce duplicates
- Avoid errors when starting everything from search results
- Fixed gzip footer verification in GunzipOutputStream
- Update address fix on transition to firewall
- SAM: Acceptance fix after soft reset
- SAM: Reset incoming socket if no subsession matches
- SSU2: Fix undetected IAE caused by itags with zero values
- SSU2: Prevent rare IAEs in peer testing timer
- Dark theme fixes
- Fixed binary content encoding
- Fixed incorrect “previous” icons
- Fixed configuration encoding for attachments
- NPE fix during soft reset
- Fix multiple IGD delivery
- Fix missing port in host header causing crashes on libupnp based devices
Finally If you are interested in knowing more about it, you can check the details in the following link