|
|
| Line 1: |
Line 1: |
| − | '''I2P''' is an [[open source]] project for building an [[anonymizing]] [[overlay network]] layered over the [[Internet]]. The software manages the connection to the I2P network and provides services that can be accessed by network-aware applications (such as [[web browsers]], [[mail readers]], [[instant messaging clients]]). The I2P network itself aims to be fully decentralized, although ordinary client-server protocols can be run on it.
| + | nn |
| − | | + | |
| − | Note that it is likely that there are bugs in the software and there has been insufficient peer review to date; thus those seeking strong anonymity should probably look elsewhere.
| + | |
| − | | + | |
| − | The network itself is strictly message-based (''Ã la'' [[internet protocol|IP]]), but there is a library available to allow reliable streaming communication on top of it (''Ã la'' [[Transmission control protocol|TCP]], although from version 0.6 there is a new [[User datagram protocol|UDP]]-based SSU transport). All communication is end-to-end [[encryption|encrypted]] (in total there are four layers of encryption used when sending a message), and even the end points ("destinations") are cryptographic identifiers (essentially a pair of [[Public key|public keys]]).
| + | |
| − | | + | |
| − | Although many of the developers had been a part of the [[Invisible IRC Project|IIP]] and [[Freenet]] communities, there are significant differences between their designs and concepts. IIP was an anonymous centralized [[Internet Relay Chat|IRC]] server, Freenet is a [[censorship]]-resistant [[distributed data store]], but I2P is an [[Anonymous P2P|anonymous peer-to-peer]] distributed communication layer designed to run any traditional internet service (e.g. [[Usenet]], [[E-mail]], [[Internet Relay Chat|IRC]], [[Web hosting]] and [[HTTP]], [[Telnet]]), as well as more traditional distributed applications (e.g. a distributed data store, a web proxy network using [[Squid cache]], and [[Domain Name System|DNS]]).
| + | |
| − | | + | |
| − | I2P is currently in the [[Development_stage#Pre-Alpha|pre-alpha]] development stage and not yet ready for general anonymity use. The first stable release, version 1.0 was planned to arrive in August [[2005]].
| + | |
| − | | + | |
| − | The main developer of I2P is jrandom, with support from numerous others [http://www.i2p.net/team].
| + | |
| − | | + | |
| − | ==I2P software tools==
| + | |
| − | Since I2P is an anonymous network layer, it is designed so ''other'' software programs can use it for anonymous communication, the so-called application layer. As such there are a variety of tools currently available for I2P or in development.
| + | |
| − | | + | |
| − | ===BitTorrent===
| + | |
| − | ====Azureus====
| + | |
| − | [[Azureus]] is a [[BitTorrent]] client that includes a [[plugin]] for I2P, allowing anonymous swarming through this network.
| + | |
| − | | + | |
| − | ====I2P-BT====
| + | |
| − | I2P-BT was a [[BitTorrent]] client for I2P that allowed anonymous [[swarming]] for [[file sharing]]. This client was a modified version of the original BitTorrent 3.4.2 program which ran on Windows and most Unices in a GUI and command-line environment.
| + | |
| − | | + | |
| − | I2P-BT was developed by the individual known as 'duck' on I2P in cooperation with smeghead. It is no longer being actively developed. The main reason for this is that the [[Azureus]] BitTorrent client took over with a new [http://azureus.sourceforge.net/plugin_details.php?plugin=azneti2p I2P plugin], but many have found it is a bit troublesome to use. However, there is a small effort to upgrade the I2P-BT client up to par with the BitTorrent 4.0 release.
| + | |
| − | | + | |
| − | ===Gnutella===
| + | |
| − | ====I2Phex====
| + | |
| − | I2Phex is a port of the popular gnutella client [[Phex]] to i2p. Although currently still in alpha development, it does tend to run with stability and without crashing and is fairly functional. Some issues with file transfers still exist and there is much cleanup left to be done concerning its [[GUI]]. It does already provide a halfway decent way of sharing content. Though BitTorrent would probably remain the best way to release new content.
| + | |
| − | | + | |
| − | ===I2PTunnel===
| + | |
| − | 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===
| + | |
| − | SAM [http://www.i2p.net/sam] is a protocol that allows a client application written in any language to communicate over I2P.
| + | |
| − | | + | |
| − | ===Susimail===
| + | |
| − | I2P has a free pseudonymous e-mail service, run by an individual called Postman. The mail transfer servers are ''[[Post Office Protocol|pop]].mail.i2p'' and ''[[Simple Mail Transfer Protocol|smtp]].mail.i2p''. 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. Susimail is a Web-based email client intended primarily for use with Postman's mail servers, designed with security and anonymity in mind. It is currently included in the default I2P distribution, and can be accessed through your I2P router console web interface. (Note that this is only used to read and send e-mail, not to create or manage your mail.i2p account; the latter must be done at ''www.mail.i2p''.)
| + | |
| − | | + | |
| − | ===Syndie===
| + | |
| − | Syndie is a [[Blog|blogging]] application for i2p (and also useable through Tor); it is currently at an alpha release.
| + | |
| − | | + | |
| − | ==I2P terminology==
| + | |
| − | I2P users will see references to the following terms on the I2P home page and on the router console.
| + | |
| − | | + | |
| − | ===Eepsite===
| + | |
| − | Eepsites are [[website]]s that are hosted anonymously within the I2P network. Eepsite names end in ''.i2p'', such as ugha.i2p or orion.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.
| + | |
| − | | + | |
| − | ===EepProxy===
| + | |
| − | The EepProxy program handles all communication between your browser and any eepsite. It functions as a [[proxy server]] that can be used by any [[web browser]].
| + | |
| − | | + | |
| − | ===Peers===
| + | |
| − | Other machines using I2P that are connected to your machine within the network. Each machine within the network shares the routing and forwarding of encrypted packets.
| + | |
| − | | + | |
| − | ===Tunnels===
| + | |
| − | Every ten minutes, a connection is established between your machine and another peer. Data to and from your machine, along with data for other users, passes through these tunnels, and are forwarded such that the packets eventually reach their final destination.
| + | |
| − | | + | |
| − | ==See also==
| + | |
| − | *[[Anonymous P2P]]
| + | |
| − | *[[Tor (anonymity network)|Tor]] - A similar anonymous communication system that is designed as more of an outproxy network to the existing Internet.
| + | |
| − | | + | |
| − | ==External links==
| + | |
| − | *[http://www.i2p2.de/ Official I2P website]
| + | |
| − | *[http://board.planetpeer.de/ Support forums for I2P and related applications like i2phex]
| + | |
| − | *[http://azureus.sourceforge.net/doc/AnonBT/i2p/I2P_howto.htm How to use Azureus with I2P]
| + | |
| − | | + | |
| − | ===I2P links===
| + | |
| − | :(I2P is required to access these sites)
| + | |
| − | *[http://ugha.i2p/ Ugha's wiki]
| + | |
| − | *[http://orion.i2p/ A list of active websites inside I2P]
| + | |
| − | | + | |
| − | {{anonymity}}
| + | |
| − | | + | |
| − | {{wikipedia|I2P}}
| + | |
| − | | + | |
| − | [[Category:Anonymous networks]][[Category:Open source software]][[Category:Java software]]
| + | |
