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.
RELEASE DETAILS Changes
-
Router: Increase minimum version for floodfill routers
-
Router: Disable I2P over Tor
-
Address Book: Cache locally hosted destinations
Bug Fixes
-
I2PSnark: Peer Exchange Tweaks
-
I2PSnark: Bugfixes
-
Router: Peer Selection Tweaks
Other
- Translation updates
What does I2P do to prevent denial of service attacks? I know that Tor obviously has proof of work, but I do not know of any mitigation measures in the I2P network. Mind you, I also used Tor quite a bit more than I use I2P, so I could be missing something.
There was an attack not too long ago. I think there’s something about it here on lemmy too. But start with this link.
https://geti2p.net/en/blog/post/2023/02/09/about_the_recent_denial_of_service_attacks
