|Original author(s)||I2P Team|
1.5.0 (API 0.9.51) / 23 August 2021
1.6.0 (API 0.9.52)
|Type||Anonymity application, Overlay network, mix network, garlic router, peer-to-peer|
|License||Free/Open Source – different licenses for different parts Public domain, BSD, GPL, MIT|
|Part of a series on|
|Video sharing sites|
|File sharing networks|
|Anonymous file sharing|
|Development and societal aspects|
|By country or region|
The Invisible Internet Project (I2P) is an anonymous network layer (implemented as a mix network) that allows for censorship-resistant, peer-to-peer communication. Anonymous connections are achieved by encrypting the user's traffic (by using end-to-end encryption), and sending it through a volunteer-run network of roughly 55,000 computers distributed around the world. Given the high number of possible paths the traffic can transit, a third party watching a full connection is unlikely. The software that implements this layer is called an "I2P router", and a computer running I2P is called an "I2P node". I2P is free and open sourced, and is published under multiple licenses.
I2P is beta software since 2003, when it started as a fork of Freenet. The software's developers emphasize that bugs are likey to occur in the beta version and that peer review has been insufficient to date. However, they believe the code is now reasonably stable and well-developed, and more exposure can help the development of I2P.
The network is strictly message-based, like IP, but a library is available to allow reliable streaming communication on top of it (similar to TCP, although from version 0.6, a new UDP-based SSU transport is used). All communication is end-to-end encrypted (in total, four layers of encryption are 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 senders nor recipients of messages need to reveal their IP address to the other side or to third-party observers.
Although many developers had been a part of the Invisible IRC Project (IIP) and Freenet communities, significant differences exist between their designs and concepts. IIP was an anonymous centralized IRC server. Freenet is a censorship-resistant distributed data store. I2P is an anonymous peer-to-peer distributed communication layer designed to run any traditional internet service (e.g. Usenet, email, IRC, file sharing, Web hosting and HTTP, or Telnet), as well as more traditional distributed applications (e.g. a distributed data store, a web proxy network using Squid, or DNS).
Many developers of I2P are known only under pseudonyms. 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.
I2P has had a stable release every six to eight weeks. Updates are distributed via I2P torrents and are signed by the release manager (generally zzz or str4d).
Since I2P is an anonymous network layer, it is designed so other software can use it for anonymous communication. As such, there are a variety of tools currently available for I2P or in development.
The I2P router is controlled through the router console, which is a web frontend accessed through a web browser.
- I2PTunnel is an application embedded into I2P that allows arbitrary TCP/IP applications to communicate over I2P by setting up "tunnels" which can be accessed by connecting to pre-determined ports on localhost.
- SAM (Simple Anonymous Messaging) is a protocol which allows a client application written in any programming language to communicate over I2P, by using a socket-based interface to the I2P router.
- BOB (Basic Open Bridge) is a less complex app to router protocol similar to "SAM"
- Orchid Outproxy Tor plugin
- Any IRC client made for the Internet Relay Chat can work, once connected to the I2P IRC server (on localhost).
- Several programs provide BitTorrent functionality for use within the I2P network. Users cannot connect to non-I2P torrents or peers from within I2P, nor can they connect to I2P torrents or peers from outside I2P. I2PSnark, included in the I2P install package, is a port of the BitTorrent client named Snark. Vuze, formerly known as Azureus, is a BitTorrent client that includes a plugin for I2P, allowing anonymous swarming through this network. This plugin is still in an early stage of development, however it is already fairly stable. I2P-BT is a BitTorrent client for I2P that allows anonymous swarming for file sharing. This client is a modified version of the original BitTorrent 3.4.2 program which runs on MS Windows and most dialects of Unix in a GUI and command-line environment. It was developed by the individual known as 'duck' on I2P in cooperation with 'smeghead'. It is no longer being actively developed; however, there is a small effort to upgrade the I2P-BT client up to par with the BitTorrent 4.0 release. I2PRufus is an I2P port of the Rufus BitTorrent client. Robert (P2P Software) is the most actively maintained I2PRufus fork. XD is a standalone BitTorrent client written in Go.
- Two Kad network clients exist for the I2P network, iMule and Nachtblitz. iMule (invisible Mule) is a port of eMule for I2P network. iMule has not been developed since 2013. iMule is made for anonymous file sharing. In contrast to other eDonkey clients, iMule only uses the Kademlia for proceeding to connect through I2P network, so no servers are needed. Nachtblitz is a custom client built on the .NET Framework. The latest version is 1.4.27, released on March 23, 2016. Nachtblitz includes a time lock to disable the software one year after its release date.
- I2Phex is a port of the popular Gnutella client Phex to I2P. It is stable and fairly functional.
- Tahoe-LAFS has been ported to I2P. This allows for files to be anonymously stored in Tahoe-LAFS grids.
- MuWire is a file-sharing program inspired by the LimeWire Gnutella client that works atop the I2P network.
Bridging to Clearnet
Currently, Vuze is the only torrent clients that makes clearnet (connections not through I2P) torrents available on I2P and vice versa, by using a plugin that connects them to the I2P network. Depending on the client settings, torrents from the internet can be made available on I2P (via announcements to I2P's DHT network) and torrents from I2P can be made available to the internet. For this reason, torrents previously published only on I2P can be made available to the entire Internet, and users of I2P can often download popular content from the Internet while maintaining the anonymity of I2P.
- I2P-Bote(github) is a free, fully decentralized and distributed anonymous email system with a strong focus on security. It supports multiple identities and does not expose email metadata. As of 2015[update], it is still considered beta software. I2P-Bote is accessible via the I2P web console interface or using standard email protocols (i.e. IMAP/SMTP). All bote-mails are transparently end-to-end encrypted and signed by the sender's private key, thus removing the need for PGP or other email encryption software. I2P-Bote offers additional anonymity by allowing for the use of mail relays with variable length delays. Since it is decentralized, there is no centralized email server that could correlate different email identities as communicating with each other (i.e. profiling). Even the nodes relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-latency mail route and the storing nodes will know to whom (which I2P-Bote address – the user's IP address is still hidden by I2P) the mail is destined. The original sender could have gone offline long before the email becomes available to the recipient. No account registration is necessary, all you have to do in order to use it is create a new identity. I2P-Bote can be installed as an I2P plugin .
- I2P also has a free pseudonymous e-mail service run by an individual called Postman. Susimail is a web-based email client intended primarily for use with Postman's mail servers, and is designed with security and anonymity in mind. Susimail was created to address privacy concerns in using these servers directly using traditional email clients, such as leaking the user's hostname while communicating with the SMTP server. It is currently included in the default I2P distribution, and can be accessed through the I2P router console web interface. Mail.i2p can contact both I2P email users and public internet email users.
- Bitmessage.ch can be used over I2p
- I2P-Messenger is a simple Qt-based, serverless, end-to-end-encrypted instant messenger for I2P. No servers can log the user's conversations. No ISP can log with whom the user chats, when, or for how long. As it is serverless, it can make use of I2P's end-to-end encryption, preventing any node between two parties from having access to the plain text. I2P-Messenger can be used for fully anonymous instant communication with persons the user doesn't even know, or, alternatively, to communicate securely and untraceably with friends, family members, or colleagues. In addition to messaging, file transfer is also supported.
I2P Chat download Windows 10: https://vituperative.github.io/i2pchat/
- I2P-Talk is another simple instant messenger incompatible with I2P-Messenger, but having the same security properties
- Syndie is a content distribution application, suitable for blogs, newsgroups, forums and small media attachments. Syndie is designed for network resilience. It supports connections to I2P, the Tor network (Syndie does not support Socks proxies, workaround needed for Tor access), Freenet and the regular internet. Server connections are intermittent, and support higher-latency communications. Connections can be made to any number of known servers. Content is spread efficiently using a Gossip protocol.
- Aktie is an anonymous file sharing and distributed Web of trust forums system. Aktie can connect to I2P with its internal router or use an external router. To fight spam, "hash payments" (proof of CPU work) is computed for every published item.
- I2PBerry is a Linux distribution which can be used as a router to encrypt and route network traffic through the I2P network.
- i2pd is a light-weight I2P router written in C++, stripping the excessive applications such as e-mail, torrents, and others that can be regarded as bloat.
- Kovri is an I2P router written in C++. It was forked from i2pd following developer disagreements. Kovri's primary purpose is to integrate with the cryptocurrency Monero to send new transaction information over I2P, making it much more difficult to find which node is the origin of a transaction request. Those using the Kovri router will be running full I2P routers that contribute to the I2P network the same way the current Java router does. This project is expected to benefit both the Monero and I2P communities, since it will allow for greater privacy in Monero, and it should increase the number of nodes on the I2P network.
The Privacy Solutions project
The Privacy Solutions project, a new organization that develops and maintains I2P software, launched several new development efforts designed to enhance the privacy, security, and anonymity for users, based on I2P protocols and technology.
These efforts include:
- The Abscond browser bundle.
- i2pd, an alternate implementation of I2P, written in C++ (rather than Java).
- The "BigBrother" I2P network monitoring project.
- Release builds of an I2P Router application for Android can be found on the Google Play store under The Privacy Solutions Project's Google Play account or on an F-Droid repository hosted by the developers.
- Nightweb is an Android application that utilizes I2P and Bittorrent to share blog posts, photos, and other similar content. It can also be run as a desktop application. It is no longer in development.
Some cryptocurrencies that support I2P are listed below.
- Eepsites are websites that are hosted anonymously within the I2P network. Eepsite names end in .i2p, such as ugha.i2p or forum.i2p. EepProxy can locate these sites through the cryptographic identifier keys stored in the hosts.txt file found within the I2P program directory. Typically, I2P is required to access these eepsites.
- 'I2p' is a pseudo-top-level domain which is only valid within the I2P overlay network scope.
.i2pnames are resolved by browsers by submitting requests to EepProxy which will resolve names to an I2P peer key and will handle data transfers over the I2P network while remaining transparent to the browser.
- The EepProxy program handles all communication between the browser and any eepsite. It functions as a proxy server that can be used by any web browser.
- Peers, I2P nodes
- Other machines using I2P that are connected to user's machine within the network. Each machine within the network shares the routing and forwarding of encrypted packets.
- Every ten minutes, a connection is established between the user's machine and another peer. Data to and from the user, along with the data for other peers (routed through the user's machine), pass through these tunnels and are forwarded to their final destination (may include more jumps).
- The distributed hash table (DHT) database based on the Kademlia algorithm that holds information on I2P nodes and I2P eepsites. This database is split up among routers known as "floodfill routers". When a user wants to know how to contact an eepsite, or where more peers are, they query the database.
A zero-day vulnerability was discovered for I2P in 2014, and was exploited to de-anonymize at least 30,000 users. This included users of the operating system Tails. This vulnerability was later patched.
A 2017 study examining how forensic investigators might exploit vulnerabilities in I2P software to gather useful evidence indicated that a seized machine which had been running I2P router software may hold unencrypted local data that could be useful to law enforcement. Records of which eepsites a user of a later-seized machine was interested in may also be inferred. The study identified a "trusted" I2P domain registrar ("NO.i2p") which appeared to have been abandoned by its administrator, and which the study identified as a potential target for law enforcement takeover. It alternatively suggested waiting for NO.i2p's server to fail, only to social engineer the I2P community into moving to a phony replacement. Another suggestion the study proposed was to register a mirror version of a target website under an identical domain.
From August 15, 2015 to August 16, 2015 the first I2P convention was held in Toronto, Ontario. The conference was hosted by a local hackerspace, Hacklab. The conference featured presentations from I2P developers and security researchers.
August 15, 2015 mainly had presentations on the past growth of the I2P network, a talk on what happens when companies sell people's personal information, and a round-table discussion on general privacy and security topics. The day ended with a CryptoParty, which helped to introduce new users to installing I2P, sending secure emails with I2P-Bote, and using I2P along with Vuze.
August 16, 2015 had more technical discussions than the previous day. The talks focused on how to dissuade bad-actors from using the network, how I2P has worked computer connection limits, how to do application development using I2P, and the development of the Android version. This day ended with a development meeting.
- Rendezvous protocol
- Deep web
- Garlic routing
- Key-based routing
- Public-key cryptography
- Secure communication
- Threat model
- "I2P Project Members". geti2p.net. Retrieved 22 November 2015.
- "I2P Roadmap". geti2p.net.
- "Licenses", Get involved, Get I2P.
- Gallagher, Sean (2015-01-13). "Under the hood of I2P, the Tor alternative that reloaded Silk Road". Ars Technica. Archived from the original on 2019-07-12. Retrieved 2019-08-17.
- "Anonymity Networks: VPNs, Tor, and I2P | Restore Privacy".
- Get I2P (blog).
- "Benefits of Tor over I2P". I2P Dev Team. Retrieved 23 December 2013.
- "Garlic Routing - I2P". geti2p.net.
- "IIP", Invisible IP, Source forge.
- "Jrandom's Announcement - I2P". geti2p.net. Retrieved 2017-07-15.
- "ElGamal/AES + SessionTag Encryption - I2P". geti2p.net.
- "Crypto/ECDSA – I2P Bugtracker". trac.i2p2.de.
- zzz (8 February 2014). "0.9.11 Release". geti2p.net.
- zzz (31 March 2014). "0.9.12 Release". geti2p.net.
- zzz (22 May 2014). "0.9.13 Release". geti2p.net.
- zzz (26 July 2014). "0.9.14 Release". geti2p.net.
- zzz (9 August 2014). "0.9.14.1 Release". geti2p.net.
- zzz (20 September 2014). "0.9.15 Release". geti2p.net.
- zzz (1 November 2014). "0.9.16 Release". geti2p.net.
- zzz (30 November 2014). "0.9.17 Release". geti2p.net.
- zzz (22 February 2015). "0.9.18 Release". geti2p.net.
- zzz (12 April 2015). "0.9.19 Release". geti2p.net.
- zzz (2 June 2015). "0.9.20 Release". geti2p.net.
- zzz (31 July 2015). "0.9.21 Release". geti2p.net.
- zzz (12 December 2015). "0.9.22 Release". geti2p.net.
- str4d (19 November 2015). "0.9.23 Release". geti2p.net.
- zzz (27 January 2016). "0.9.24 Release". geti2p.net.
- zzz (3 March 2016). "0.9.25 Release". geti2p.net.
- zzz (7 June 2016). "0.9.26 Release". geti2p.net.
- zzz (17 October 2016). "0.9.27 Release". geti2p.net.
- zzz (12 December 2016). "0.9.28 Release". geti2p.net.
- zzz (27 February 2017). "0.9.29 Release". geti2p.net.
- zzz (3 May 2017). "0.9.30 Release". geti2p.net.
- zzz (7 August 2017). "0.9.31 Release". geti2p.net.
- zzz (11 November 2017). "0.9.32 Release". geti2p.net.
- zzz (30 January 2018). "0.9.33 Release". geti2p.net.
- zzz (10 April 2018). "0.9.34 Release". geti2p.net.
- zzz (26 June 2018). "0.9.35 Release". geti2p.net.
- zzz (23 August 2018). "0.9.36 Release". geti2p.net.
- zzz (4 October 2018). "0.9.37 Release". geti2p.net.
- zzz (22 January 2019). "0.9.38 Release". geti2p.net.
- zzz (21 March 2019). "0.9.39 Release". geti2p.net.
- zzz (7 May 2019). "0.9.40 Release". geti2p.net.
- zzz (2 July 2019). "0.9.41 Release". geti2p.net.
- zzz (28 August 2019). "0.9.42 Release". geti2p.net.
- zzz (22 October 2019). "0.9.43 Release". geti2p.net.
- zzz (1 December 2019). "0.9.44 Release". geti2p.net.
- zzz (25 February 2020). "0.9.45 Release". geti2p.net.
- zzz (25 May 2020). "0.9.46 Release". geti2p.net.
- zzz (24 August 2020). "0.9.47 Release". geti2p.net.
- zzz (30 November 2020). "0.9.48 Release". geti2p.net.
- "SAM", API, I2P.
- "BOB", API, Get I2P.
- "GitHub - subgraph/Orchid". 7 March 2019 – via GitHub.
- I2P Bittorrent FAQ (forum), DE: i2p2, archived from the original on 2011-11-03.
- The Hunting of the Snark Project – BitTorrent Application Suite, Klomp.
- "How To for I2P Network Plugin", I2PHelper (Howto) (setup tutorial), Vuze.
- "Rufus – BitTorrent Client". Sourceforge..
- "GitHub - majestrate/XD: i2p bittorrent client". 22 March 2019 – via GitHub.
- "r/i2p - Introducing MuWire - a file-sharing application for I2P". reddit. Retrieved 2019-12-17.
- "Vuze Speeds Up Torrent Downloads Through "Swarm Merging"". TorrentFreak. 20 March 2015. Retrieved 4 June 2016.
- "I2PHelper HowTo". VuzeWiki. Retrieved 4 June 2016.
- Introducing I2P, Nov 10, 2015
- "PurpleI2P/i2pd". GitHub. Retrieved 2018-08-20.
- "Invisible Internet Protocol Daemon". i2pd.website. Retrieved 2018-08-20.
- "Archived copy". Archived from the original on 2017-11-07. Retrieved 2017-10-30.CS1 maint: archived copy as title (link)
- "What is the difference between i2pd and Kovri?". StackExchange. Retrieved 4 March 2017.
- "Kovri - Moneropedia". GetMonero. Retrieved 4 March 2017.
- "What use cases will Kovri have for Monero?". StackExchange.
- Privacy Solutions project, archived from the original on 19 Apr 2018.
- List of ongoing Privacy Solutions projects.
- "Invisible Internet Protocol Daemon". i2pd.website.
- Active development, The Privacy Solutions
- Active development, Purple I2P
- Android App Releases
- Discontinued, Nightweb.
- "Add I2P support using I2P SAM by vasild · Pull Request #20685 · bitcoin/bitcoin". GitHub. Retrieved 2021-04-03.
- "I2P con 2015 - Growing the Network, Spreading the Word, 03:41". YouTube.
- "Intro". I2P. Retrieved 4 June 2016.
- "Naming and Addressbook - I2P". geti2p.net. Retrieved 4 June 2016.
- "Tunnel Routing". I2P. Retrieved 4 June 2016.
- "The Network Database". I2P. Retrieved 4 June 2016.
- Kack, Christopher (2012-09-11). "Layer 7 DOS against I2P darknet". Kejsarmakten:Development. Archived from the original on 2012-10-14. Retrieved 2021-03-13.
- Bazli, Behnam; Wilson, Maxim; Hurst, William (2017-01-01). "The dark side of I2P, a forensic analysis case study". Systems Science & Control Engineering. 5 (1): 278–286. doi:10.1080/21642583.2017.1331770.
- Storm, Darlene (2014-07-24). "Zero-day broker exploits vulnerability in I2P to de-anonymize Tails users". Computerworld. Retrieved 2021-03-13.
- "I2P patched against de-anonymizing 0-day, Tails integration still to follow". Help Net Security. 2014-07-29. Retrieved 2021-03-13.
- "0.9.14 Release - Blog - I2P". geti2p.net. Retrieved 2021-03-13.
- "I2PCon: Mission Accomplished - Blog". I2P. Retrieved 4 June 2016.
- "Hacker-Turned-Consultant Helps 'House Of Cards'". New Orleans Public Radio. 9 April 2014. Retrieved 4 October 2017.