Old version, no longer maintained: 0.9.22įixes for I2PSnark getting stuck before completion, and begins the migration of router infos to new, stronger Ed25519 signatures. Old version, no longer maintained: 0.9.21Ĭontains several changes to add capacity to the network, increase the efficiency of the floodfills, and use bandwidth more effectively. Important bug fixes, and several changes to increase floodfill capacity in the network. Old version, no longer maintained: 0.9.20 Several fixes and improvements for floodfill performance. Old version, no longer maintained: 0.9.19 Shortened the startup time, and reduced latency throughout our network protocols. Old version, no longer maintained: 0.9.18 Old version, no longer maintained: 0.9.17 Old version, no longer maintained: 0.9.16Īdd support for stronger Router Info signatures. Preliminary support for Ed25519 EdDSA signatures. Old version, no longer maintained: 0.9.15 Old version, no longer maintained: 0.9.14.1 Old version, no longer maintained: 0.9.14Ĭritical fixes for XSS and remote execution vulnerabilities. SusiMail improvements and fixes for firewalled router. Old version, no longer maintained: 0.9.13 Support for ECDSA and updates to Jetty 8. Old version, no longer maintained: 0.9.12 Support for outproxy plugins, improves lease set lookup security, and reduces memory usage. Old version, no longer maintained: 0.9.11 Updates are distributed via I2P torrents and are signed by the release manager (generally zzz or str4d). I2P has had a stable release every six to eight weeks. I2P uses 2048bit ElGamal/ AES256/ SHA256+Session Tags encryption and Ed25519 EdDSA/ ECDSA signatures. While the previous main developer, jrandom, is currently on hiatus, others, such as zzz, killyourtv, and Complication have continued to lead development efforts, and are assisted by numerous contributors. Many developers of I2P are known only under pseudonyms. a distributed data store, a web proxy network using Squid, or DNS). Usenet, email, IRC, file sharing, Web hosting and HTTP, Telnet), as well as more traditional distributed applications (e.g. I2P is an anonymous peer-to-peer distributed communication layer designed to run any traditional internet service (e.g. Freenet is a censorship-resistant distributed data store. IIP was an anonymous centralized IRC server. All communication is end-to-end encrypted (in total there are four layers of encryption used when sending a message) through garlic routing, and even the end points ("destinations") are cryptographic identifiers (essentially a pair of public keys), so that neither sender nor recipient of a message need to reveal their IP address to the other side or to third-party observers.Īlthough many developers had been a part of the Invisible IRC Project (IIP) and Freenet communities, there are significant differences between their designs and concepts. The network itself is strictly message-based (like IP), but there is a library available to allow reliable streaming communication on top of it (similar to TCP, although from version 0.6 there is a new UDP-based SSU transport). However, they believe the code is now reasonably stable and well-developed, and more exposure can help the development of I2P. The software's developers emphasize that there are likely to be bugs in the beta version and that there has been insufficient peer review to date. I2P is beta software since 2003, when it started as a fork of Freenet. Comparison of Internet Relay Chat clients.Incomplete translations: Russian, French,Romanian, German, Swedish, Italian, Portuguese, Chinese, Dutch, Polish, Hungarian, Arabic, Japanese, Estonian, Persian Īnonymity application, Overlay network, mix network, garlic router, peer-to-peerįree/Open Source – different licenses for different parts Public domain, BSD, GPL, MIT Cross-platform: Unix-like ( Android, Linux, BSD, macOS), Microsoft Windows
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |