I2P
I2P is an anonymizing network, offering a simple layer that identity-sensitive applications can use to securely communicate. All data is wrapped with several layers of encryption, and the network is both distributed and dynamic, with no trusted parties.
| Tags | Communications Internet Security Networking Utilities |
|---|---|
| Licenses | GPLv2 |
| Operating Systems | Mac OS X POSIX Windows Windows |
| Implementation | Java |
Recent releases
- 18 May 2009 20:38
Changes: A patch to I2P's internal web server Jetty is included to correct SusiDNS behaviour on Windows. The way I2P nodes volunteer to participate in the Network Database is changed to avoid too many doing this simultaneously, and creation of new participating tunnels is now throttled before messages in existing tunnels start to get dropped. Multiple improvements to the Router Console and other components are included, I2PSnark can handle bigger torrents and more files, while work continues on the experimental desktop interface.
- 19 Apr 2009 23:16
Changes: Support has been added for accessing the Router Console over IPv6. A new message type enables I2CP applications to query the router's bandwidth limits, and participation of a single peer in too many tunnels is prevented to improve reliability and safety. Besides other maintenance work, several old statistics calculators are dropped to make router profiles smaller and quicker, while new build scripts are supplied for I2P's big integer math library. Updating is highly recommended.
- 30 Mar 2009 17:35
Changes: Support for encrypted LeaseSets (for creation of links over I2P that an adversary cannot obstruct by attacking its gateways) is more complete. New tunnel types like IRC server tunnels and new options like delayed start and idling of tunnels also gain support, along with improved usability of the I2P SOCKS proxy mechanism.
- 25 Jan 2009 22:25
Changes: Various feature enhancements and bugfixes.
- 02 Dec 2008 18:13
Changes: This release introduces new components, drops some old ones (like the old TCP transport), and has been optimized to perform better. The BOB (Basic Open Bridge) protocol is introduced, for use by client applications that cannot import I2CP libraries directly. This deprecates the old SAM protocol that was previously used in such cases. Improved code should be better at preventing congestion.
