I2P full changelog

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.

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.

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.

Release with SHA256 fix

Release with local site access fix

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.

Changes:
Graphs: render graphs in svg
Translations: generate internal translation leaderboard
Bug Fixes:
i2ptunnel: Fix bug causing truncation configuration UI
Other:
Translation updates

Changes:
I2PTunnel: Implement support for Keepalive/Server-side Persistence
Susimail: Add markdown support for formatted plain-text content
Susimail: Add HTML Email support
I2PSnark: Add search capability
I2PSnark: Preserve private=0 in torrent files
Data: Store compressed RI and LS
Bug Fixes:
Susimail: Fix handling of forwarded mail with attachments
Susimail: Fix handling of forwarded mail with unspecified encoding
Susimail: Fix forwarding of HTML-only email
Susimail: Bugfixes in presentation of encoded attachmments, mail body
I2PSnark: Handle data directory changes
SSU2: Cancel peer test if Charlie does not have B cap
SSU2: Treat peer test result as unknown if Charlie is unreachable
Router: Filter additional garlic-wrapped messages
I2CP: Prevent loopback messages to same session
NetDB: Resolve Exploratory/Router isolation-piercing event