I2P GLOSSARY
- darknet
- off-the-radar communications network. eg. I2P
- eepsite
- anonymous encrypted website served from within the I2P darknet.
- Itoopie
- I2P Official Mascot. Fluffy toys coming soon!
enci2pedia's database
Maybe we can make use of some of enci2pedia's factoids here.
There is some nonsense in the database so I decided against pasting the whole list here. Instead I will attach it as a file to selectively pick from.
I generally publish enci2pedia's db here by the way: http://darrob.i2p/factoids/
[ RN Coment: while pruning the nonsense in the attachment darrob, I'm glad you left the unicorn entry, but what happened to the flying ponys? ]
I2P terminology
singular
- Addressbook
- The I2P addressbook manages .i2p addresses, similar to your OS's hosts file. See http://www.i2p2.i2p/faq.html#subscriptions.
- bandwidth
- Your bandwidth is configured on http://localhost:7657/config.jsp . All rates in I2P are specified in bytes per second. Divide your connection rate in bits per second by 8 to get bytes per second.
- block list
- the manually-configured list of banned peers
- bob
- a Basic Open Bridge API to the I2P router. see http://bob.i2p/ for more info.
- bulk
- an i2ptunnel connection type and is the default. You generally do not need to change this.
- e2ee
- end to end encryption
- eepannouncer
- EepAnnouncer is a webapplication that announces your <eepsite> to the <seedless> cloud.
- Eepget on Windows
- Look here for instructions to use eepget on Windows: http://zzz.i2p/topics/105. There is also a bat script for the lazy: http://qgv64klyy4tgk4ranaznet5sjgi7ccsrawtjx3j5tvekvvfl67aa.b32.i2p/handystuff/eepget_url.bat.
- eepget
- a command line HTTP client similar to wget, found in your I2P installation directory. It fetches web pages and files through the I2P HTTP proxy. If you use Windows see <eepget on Windows>. For an alternative ask me about <wget>.
- eeproxy
- I2P provides a resident http proxy server to access .i2p domains, and optionally http sites on the outernet (via false.i2p). Default: 127.0.0.1:4444
- Exit node
- a Tor relay that relays traffic to the open web. In I2P they are called <outproxies>. As a participant on I2P you are never an exit node/outproxy yourself.
- firewalled
- Firewalled means your UDP port appears to be firewalled. As the firewall detection methods are not 100% reliable, this may occasionally be displayed in error. See http://127.0.0.1:7657/config.jsp#help and <ports>
- Floodfill
- a special kind of router that does most of the searching for information on the I2P distributed database. You could call it an "ultrapeer" or a "tracker" but people have been using "floodfill" because that refers to exactly what it does.
- garlic routing
- layered encryption of messages, passing through routers selected by the original sender; a technique employed by the i2p router, see http://www.i2p2.i2p/how_garlicrouting
- i2cp
- http://www.i2p2.i2p/i2cp
- i2np
- http://www.i2p2.i2p/i2np
- i2pupdate.sud
- a signed update file. These are normally downloaded by your router and installed automatically. See <updating>.
- identity
- Your router identity is shown at http://localhost:7657/netdb.jsp?r=. It is the 44-character string after "our info" and represents a 256-bit SHA-256 hash of your router's public keys. You do not normally need to change it, but see http://zzz.i2p/topics/21 if you really want to.
- interactive
- an i2ptunnel connection type and is not the default. It may be better than bulk for IRC, but this option really doesn't do much and might be removed someday.
- Irc2P
- the official I2P-internal <IRC network>. You are currently connected to it. See http://hq.postman.i2p/?page_id=25. Related: <IRC servers>, <IRC tunnel>, <SOCKS5 IRC proxy>.
- Itoopie
- the official I2P Mascot.
- Jetty
- the webserver that is bundled with I2P. It is used to serve I2P's router console and also your <eepsite> by default. It supports HTML and CGI. If you need more features it's easy to setup <Apache> to work with I2P.
- manual reseed
- only recomended when you have absolutely no communication from anyone at all. Otherwise i2p seeds itself. See http://www.i2p2.de/faq.html#manual_reseed for more info
- message delay
- How long an outbound message waits in the queue. This should generally be a few hundred milliseconds or less. see also http://localhost:7657/help.jsp
- neodatis
- Neodatis ODB is a very simple Object Database that currently runs on the Java, .Net, Google Android, Groovy and Scala. More info at http://www.neodatis.org/
- outer net
- a term for the open Internet as opposed to closed (inner) darknets like I2P.
- peer ban list
- automatically updated, but may also contain manual entries called the block list
- rejecting tunnels
- when the router is refusing to route traffic for others, for example when it has just started up.
- Reseed
- automatic in I2P. See <manual reseed>.
- Router Console
- the place to configure your I2P router. It also links to interesting eepsites and tells you how to configure your browser and IRC client. You find it under http://localhost:7657. Also see <remote router> if applicable.
- Seedless Server
- Seedless Server is a webapplication that allows you to participate in the <seedless> cloud.
- Seedless
- a distributed service directory that is used for trackerless torrents, hidden eepsites and more. See http://sponge.i2p/files/seedless/
- share
- Your share bandwidth is configured on http://localhost:7657/config.jsp . It is the maximum percentage of your bandwidth limits that is used to route traffic for others. The remainder is reserved for your own traffic. See also <bandwidth>
- streaming lib
- described at http://www.i2p2.i2p/streaming
- tunnel timeout
- fixed at 10 minutes (unlike Tor where a circuit is long-lived). It used to be configurable but it isn't any more. All peers assume a timeout of 10 minutes.
- tunnel
- A tunnel in I2P refers to the connection between 2 endpoints. Ask me about <creating tunnels>
- Updating
- By default your router will check for updates periodically and inform you in the <router console>. After the update is transferred all you have to do is restart the router (give it 11 minutes). For options see http://localhost:7657/configupdate.jsp.
- UPnP
- I2P supports UPnP (Universal Plug and Play) and UDP hole punching with "SSU introductions" to relay traffic. This is useful if you can't open/forward the necessary ports manually. See http://localhost:7657/config.jsp#help.
- zzzot
- an open tracker plugin. It sets up a tunnel automatically. The statistics page is at http://127.0.0.1:7662/tracker/index.jsp . There is no admin interface.
plural
- b32 addresses
- shorter addresses to eepsites (shorter than b64) that don't have to be registered anywhere. You can find the b32 address of your eepsite by clicking on the preview button in your eepsite tunnel entry here: http://localhost:7657/i2ptunnel/index.jsp
- Darknets
- closed communication networks. I2P falls into that category. See http://en.wikipedia.org/wiki/Darknet_(file_sharing).
- Deepsites
- distributed eepsites hosted on the Tahoe-LAFS distributed data storage.
- Eepsites
- anonymously hosted websites in I2P, sometimes accessible from the outernet through an <inproxy>. Ask me about <browsing eepsites>, <hosting eepsites> and <backing up eepsites>. Related: <Deepsites>, <links>.
- Hidden Services
- Tor internal services and therefor very similar to I2P's. Their addresses have a .onion domain.
- Inproxies
- servers that allow access to I2P-internal services from outside the I2P net, most commonly the open web. You can access many eepsites from the internet by appending ".to" to their .i2p domain, i.e. forum.i2p → forum.i2p.to.
- Outproxies
- servers that allow you to access the Internet anonymously through I2P. They are the equivalent to Tor's exit nodes, however in I2P there are only a few that are run by volunteers. We usually recommend Tor for anonymous web access.
- Plugins
- a way to easily support additional software for I2P. This is quite new but several useful plugins exist already. See http://stats.i2p/i2p/plugins/.
- ports
- You'll need to make sure that your router is reachable from the outside. The following link will help you set up your ports correctly: http://localhost:7657/config.jsp#chelp
I2P related
singular
- addressbook update
- The interval for updating the addressbook from the subscriptions is 12 hours by default. Change the subscription list to force an update immediately.
- CIA-1
- CIA-1 is a bot that reports commits to the I2P monotone database. Ask me about <monotone>.
- Forum project
- something <dream> is working on. That's unfortunately all I know.
- Forum
- Forum may refer to <forum.i2p> (http://forum.i2p/) or to dream's <Forum> project>. Forum.i2p is a donated service, please respect the operator.
- fox
- a link between irc servers outside and irc2p servers inside i2p. The nick of the person is shown after <fox>
- guitone
- a nice GUI frontend for monotone
- I2P
- I2P (Invisible Internet Project) is a darknet implementation built atop java, with full support for streaming, anonymous <BitTorrent>, <webserving>, <mail> and more. See http://www.i2project.net/ or http://www.i2p2.i2p/.
- jrandom
- the founder of i2p, who vanished in November 2007
- monotone help
- http://www.i2p2.i2p/newdevelopers
- monotone
- the distributed version control system (DVCS) used to propagate and store development work on I2P. See http://monotone.ca also see http://www.i2p2.i2p/newdevelopers
- mtn ci
- monotone checkin (commit), you do this to commit your changes, and you must do mtn push after this to send the committed changes to the main project repository
- mtn co
- monotone checkout, you only need to do this once for each branch
- mtn help
- an easy way to get inline help about misc monotone commands. see also <monotone>
- pastebin
- a place where you can share snippets of text that are too long for IRC (e.g. error messages). The I2P internal, anonymous pastbin is at http://paste.i2p2.i2p/.
- stats.i2p
- http://stats.i2p provides near-realtime stats on the network and other misc services, run by zzz.
- Techintro
- For an introduction to how I2P works see http://www.i2p2.i2p/techintro.html.
- Telecomix
- a group of internet activists that is also active on I2P. See http://telecomix.org/ and http://telecomix.i2p/.
- Trac
- an open source, web-based project management and bug-tracking tool. I2P's trac is located here: http://trac.i2p2.i2p/
- Video tutorial
- There is a video tutorial on how to install I2P by Telecomix: http://www.youtube.com/watch?v=QeRN2G9VW5E.
- vulpine
- a link between irc servers outside and irc2p servers inside i2p. The nick of the person is shown after <vulpine>
plural
Not I2P related
singular
- DATA statement
- The primary purpose of the DATA statement is to give names to constants; instead of referring to pi as 3.141592653589793 at every appearance, the variable PI can be given that value with a DATA statement and used instead of the longer form of the constant. This also simplifies modifying the program, should the value of pi change. — FORTRAN manual for Xerox Computers
- Encryption
- the process of transforming information (referred to as plaintext) using an algorithm (called cipher) to make it unreadable to anyone except those possessing special knowledge, usually referred to as a key. http://en.wikipedia.org/wiki/Encryption
- Search engine
- http://eepsites.i2p/ is an I2P internal search engine.
plural
- Factoids
- these little tidbits of information that an infobot can give you.
Hosting & File Sharing
singular
- BitTorrent
- You can use BitTorrent on I2P. However, be aware that you cannot connect to trackers or clients on the <outernet>. Ask me about <BitTorrent clients> or <BitTorrent trackers>.
- Browsing eepsites
- To be able to browse eepsites you'll have to configure your browser according to <proxy settings>. Once that's done you'll be able to access .i2p domains just like normal web domains. Also add some <subscriptions>.
- Eepsite backup
- To backup your eepsite it should be enough to save your eepsite directory (probably in ~/.i2p). The most important file to backup is your private key (eepsite/eepPriv.dat).
- Eepsite Unreachable
- The eepsite unreachable error means that the eepsite is either offline, there is network congestion, or that your router is not yet well-integrated with peers. In any case you should retry. You can check if an eepsite is online at http://perv.i2p/.
- Eepsite uptime
- The uptime of <eepsites> can vary if the owner's router is not running 24/7. <Deepsites> might be a solution to this particular problem.
- eMule
- a file-sharing client not compatible with I2P. You're probably looking for iMule.
- File-sharing
- There are several file-sharing solutions for I2P: <BitTorrent>, <iMule>, <I2Phex>, your own <eepsite> and at some point in the future also <Tahoe-LAFS>. BitTorrent is the most popular one.
- gnutella
- I2Phex is the I2P port of Phex. It offers you file sharing using the gnutella protocol in I2P.
- Hosting eepsites
- If you want to run your own, fully anonymous eepsite follow the instructions on your <router console> (http://127.0.0.1:7658). This will make use of I2P's <Jetty> webserver. You may also use <Apache>.
- how eepsite
- to view eepsites, your browser (or system) proxy for http needs to have the same settings as "eepproxy" under the local destinations link in your console. Usually this is 127.0.0.1 port 4444
- I2P Rufus
- a now unmaintained <BitTorrent client>. Look into <Robert> instead.
- I2P-BT
- I2P-BT was the first working <BitTorrent> client for I2P. See http://i2p-bt.postman.i2p/. You should also look into the other <BitTorrent clients> available.
- i2phex browser
- I2Phex is a standalone application, it is not accessible from a browser.
- I2Phex
- a Gnutella client for use within the I2P network. There is a I2Phex forum here: http://forum.i2p/viewforum.php?f=25. You can download it here: http://echelon.i2p/.
- I2PSnark
- the built-in BitTorrent client. It has links to the most common I2P trackers and even explains how to add torrents (http://localhost:7657/i2psnark/). There are also alternative <BitTorrent clients> though.
- I2PSnarkXL
- an extension of the router-builtin I2PSnark BitTorrent client. It adds a nice GUI and some performance enhancements. See http://i2psnarkxl.i2p/. Also ask me about the other <BitTorrent clients>.
- iMule
- an open-source aMule clone for I2P-internal use. It offers filesharing via an I2P-kad network and can be downloaded from http://echelon.i2p or http://www.imule.i2p. And there's a section in the forum: http://forum.i2p/viewforum.php?f=30.
- PyBit?
- a <BitTorrent client> for I2P. I haven't learned much about it yet. All I know is that you can get it from http://echelon.i2p/.
- Robert
- a bittorrent client for the I2P network, with support for trackerless torrents. For more information visit: http://bob.i2p
- Tahoe-LAFS
- the first cloud storage system with provider-independent security. Find out more at http://duck.i2p/tahoe-lafs/ and join #tahoe-lafs.
- thepiratebay
- an eepsite that is hard to find, has bad stuff on it, and may not be up anymore. Not recommended. Instead ask me about <BitTorrent trackers>.
- tracker
- A tracker is a public site dedicated to offering bittorrent downloads.
- Transmission
- a BitTorrent client. There is also a port of it that works for I2P-internal torrents. See http://echelon.i2p for more details.
plural
- BitTorrent clients
- applications that manage file transfers using the <BitTorrent> protocol. The following clients work on I2P and you can ask me about them individually: I2PSnark, I2PSnarkXL, I2P-BT, I2P Rufus, Transmission, PyBit? and Robert.
- BitTorrent trackers
- sites dedicated to offering bittorrent downloads. You can find a list of the most widely used ones in I2PSnark's webconsole at http://localhost:7657/i2psnark/. The most popular tracker is http://tracker2.postman.i2p/.
Tools
singular
- -no-remote
- a Firefox command line option that lets you run separate <Firefox profiles> at the same time. See http://kb.mozillazine.org/Command_line_arguments
- Apache
- a webserver you can use to serve <eepsites> (default is <Jetty>). All you have to do is tweak the existing eepsite server settings to match your Apache port. Make sure it doesn't leak information. See also: http://forum.i2p/viewtopic.php?t=194#578
- Better Privacy
- a Firefox extension that tries to protect you from Super Cookies. See https://addons.mozilla.org/en-US/firefox/addon/6623/.
- CS Lite
- a Firefox extension that will allow you to easily control cookie permissions. See https://addons.mozilla.org/en-US/firefox/addon/5207/.
- ELinks
- a free text-based console web browser for Unix-like operating systems. To use it with I2P you need to set the http proxy variable: 'http_proxy=127.0.0.1:4444 elinks'. You could create a bash alias for convenience.
- Fetchmail
- a MRA. Personally I think <getmail> is a better choice, but I may be convinced otherwise. See http://www.fetchmail.info/.
- Firefox
- a recommended web browser for I2P. Ask me about <Firefox extensions> and <browser profiles>.
- FoxyProxy? I2P rule
- To correctly route all I2P traffic using <FoxyProxy?> add the following regular expression rule:
^http://[^/]*\.i2p/.*
- FoxyProxy?
- an addon that lets you configure several different proxies in Firefox to access I2P and the web at the same time. See http://zephyr.i2p/foxyproxy.html and <FoxyProxy? I2P rule>. Alternatives are <browser profiles> and <Privoxy>.
- Getmail
- a MRA that is very easy to setup to work with <mail.i2p>. Simply point it to localhost port 7660 and set it to SimplePOP3Retriever (non-SSL). See http://pyropus.ca/software/getmail/. An alternative is <Fetchmail>.
- MRA
- A mail retrieval agent (MRA) is an application that retrieves e-mail from a remote mail server, for example <mail.i2p>. I know about <getmail> and <fetchmail>.
- Multiproxy Switch
- a Firefox extension for proxy management, it can be used to quickly switch proxy settings; with a visual indication… covers more settings than the on/off of torbutton… and is not conditional like foxyproxy,so it works better feeding a conditional proxy. More details of it's robustness and info leaks are needed…
- Mutt
- a mail client (MUA) that works with <mail.i2p>. Research the header related options to make sure you're not giving away personal information though. Use <getmail> and mutt's native SMTP support. See http://www.mutt.org/ and compare it with other MUAs here: http://hq.postman.i2p/?page_id=9.
- NoScript?
- a recommended Firefox extension that allows JavaScript?, Java and other executable content to run only from trusted domains of your choice. See https://addons.mozilla.org/en-US/firefox/addon/722/.
- Polipo
- a light-weight proxy server designed for single users or small groups. It supports caching to speed up browsing. It's also the default proxy of the Tor project. See http://www.pps.jussieu.fr/~jch/software/polipo/. Another caching 'proxy server' is 'Squid'.
- Privoxy
- a proxy server that can route your traffic to different places (I2P, Tor, internet) based on URL rules (similar to <FoxyProxy?>). See http://forum.i2p/viewtopic.php?t=218, http://forum.i2p/viewtopic.php?t=3191, http://www.privoxy.org/faq/.
- PuTTY
- a free implementation of Telnet and SSH for Windows and Unix platforms. See http://www.chiark.greenend.org.uk/~sgtatham/putty/.
- RefControl?
- a Firefox extension that allows you to forge the HTTP Referer and thereby hide from which site you have been redirected. See https://addons.mozilla.org/en-US/firefox/addon/953/ and http://www.stardrifter.org/refcontrol/.
- RequestPolicy?
- a highly recommended Firefox extension that allows you to control which cross-site requests you want to allow. See https://addons.mozilla.org/en-US/firefox/addon/9727/ and http://www.requestpolicy.com/.
- Sendmail
- an MTA. Sorry, that's all I can tell you right now.
- slrn
- an open source text-based news client. Once you created the tunnel for an I2P <news server> run 'slrn —nntp -h localhost -p $port' to connect. Before actually using it you should configure a .slrnrc for I2P. Ask me about <slrnrc>.
- slrnrc
- A standard .slrnrc will work. However, make sure you configure your desired nickname and 'set generate_message_id 0' to keep your hostname secret. Also fake your hostname (set hostname) and set your mail.i2p address as the replyto address.
- Squid
- possibly the most common caching proxy server. It is rather complex and most users might be better off using Polipo. See http://www.squid-cache.org/.
- Thunderbird
- a MUA that can be used with <mail.i2p>. Be sure to read the following page though: http://hq.postman.i2p/?page_id=9.
- Torbutton
- a recommended Firefox extensions that despite its name is very useful on I2P. It takes care of many different browser settings to prevent privacy attacks. See https://www.torproject.org/torbutton/.
- wget
- a utility for downloading network data. It reads the http_proxy environment variable. Set it to localhost:4444 to be able to retrieve files from I2P. Also see <eepget>.
plural
- Browser profiles
- a way to run several different browser configurations at the same time (i.e. web and I2P). For Firefox try 'firefox -P -no-remote'. Alternatively you could install the <FoxyProxy?> extension.
- Browsers
- You should be able to use all web browsers with I2P, but not all are equally qualified for anonymous networks. Use Firefox when in doubt and ask me about Firefox extensions.
- Cookies
- text strings stored by a user's web browser. It is advisable to turn off cookies (in general even, but at least for I2P). Relevant <Firefox extensions> are <CS Lite> and <Torbutton>.
- Firefox extensions
- Recommended Firefox extensions are <NoScript?>, <CS Lite>, <Torbutton>, <Request Policy>, <RefControl?>, <Better Privacy>. Related: <browser profiles>, <FoxyProxy?> and <Privoxy>.
- Mail clients
- Mail clients (MUAs) can be used with mail.i2p. See this page for a comparison: http://hq.postman.i2p/?page_id=9.
- Newsreaders
- used to read and post to <news servers>. Here is a list newsreaders: http://en.wikipedia.org/wiki/List_of_news_clients. I can give you a few hints on how to configure <slrn> for I2P.
Other networks
singular
- FLIP
- FLIP (Freenet Lightweight IRC Program) is an application to provide chat over Freenet using the IRC protocol. See http://new-wiki.freenetproject.org/FLIP.
- Freenet proxy
- There is a Freenet proxy at http://fproxy.tino.i2p/.
- Freenet
- a decentralized, distributed data store. All applications etc. are built on top of the data store which is extremely limiting. See http://freenetproject.org/. For a distributed datastore on I2P see <Tahoe-LAFS>.
- FreeTalk?
- supposed to be a spam-resistant system for discussion forums on Freenet. See http://new-wiki.freenetproject.org/Freetalk.
- Frost
- an external application for Freenet that provides usenet-like messaging and a searchable file-sharing system. See http://new-wiki.freenetproject.org/Frost.
- GNUnet
- an anoymous P2P network that's build around the purpose of file-sharing. http://gnunet.org/
- Mixminion
- an anonymous remailer: http://en.wikipedia.org/wiki/Mixminion. For I2P mail systems ask me about <mail>.
- Phantom protocol
- a system for decentralized anonymization of generic network traffic. It is a very young project. See http://code.google.com/p/phantom/.
- Thaw
- a filesharing utility and upload/download manager. It is used as a graphical interface for Freenet filesharing. See http://new-wiki.freenetproject.org/Thaw.
- Tor overview
- https://www.torproject.org/overview.html.en
- Tor
- an anonymous network very similar to I2P, but unlike I2P it focuses on anonymous access to the open web. We consider the two as being complimentary. See http://www.i2p2.de/techintro.html#similar.tor & https://www.torproject.org/
plural
- Freesites
- web pages on Freenet. See http://new-wiki.freenetproject.org/Freesite.
- Other networks
- being listed here: http://en.wikipedia.org/wiki/Anonymous_P2P#List_of_anonymous_P2P_networks_and_clients
Networking
singular
- Creating tunnels
- To setup a new I2P tunnel go to: http://localhost:7657/i2ptunnel/index.jsp
- GarliCat
- GarliCat creates a transparent IP layer on top of I2P. It transmits any kind of IP-based data transparently through the I2P network. See http://www.cypherpunk.at/onioncat/wiki/GarliCat and http://echelon.i2p/garlicat/.
- i2ping
- like ping over i2p
- iptables
- a user space application program that allows a system administrator to configure the tables provided by the Linux kernel firewall and the chains and rules it stores. See http://www.netfilter.org/.
- Netfilter
- a framework that provides hook handling within the Linux kernel for intercepting and manipulating network packets. See http://www.netfilter.org/.
- Network accessible router
- To make your router accessible by all computers on your network subsitute '127.0.0.1' for the IP address of the server in line 'clientApp.0.args=7657 127.0.0.1 ./webapps/' in file ~/.i2p/clients.config. Be aware that traffic to the router console will be unencrypted. You should use <SSH tunnels> instead.
- OnionCat
- OnionCat creates a transparent IP layer on top of <Tor>'s <hidden services>. It transmits any kind of IP-based data transparently through the Tor network on a location hidden basis. See http://www.cypherpunk.at/onioncat/.
- OpenVPN
- a software application that implements VPN solutions for creating secure point-to-point or site-to-site connections. See http://openvpn.net/index.php/open-source/333-what-is-openvpn.html.
- Remote router
- If you run the I2P router on another computer the best way to access it is using <SSH tunnels>. Alternatively you can set the router to accept connections from the network (see <network accessible router>).
- Shutdown
- The reason a shutdown/restart of your router takes 11 minutes is that tunnel leases last 10 minutes. Your router waits 11 minutes to make sure that all participating tunnels are finished.
- SOCKS5 IRC proxy
- With a SOCKS5 IRC proxy tunnel you'll be able to connect to several IRC servers without having to setup a seperate tunnel for each one. Here are the instructions: http://zzz.i2p/topics/690
- SSH tunnel settings
- To tunnel I2P through SSH create the necessary tunnels by either running 'ssh -L7657:127.0.0.1:7657 -L4444:127.0.0.1:4444 $USER@$SERVER' or setting the LocalForwards? in your ~/.ssh/config accordingly.
- TLS
- Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for communications over networks such as the Internet. Since I2P encrypts connections by default TLS is not needed for internal services.
- VPN
- VPNs (virtual private networks) are a very useful tool. For the purpose of staying anonymous those commercial VPN providers that are being hyped everywhere are useless though. Be careful.
plural
- Proxy servers
- servers that act as an intermediary for requests from clients seeking resources from other servers. Potentially useful proxies for I2P are 'Privoxy', 'Polipo' and 'Squid', which can even be used in combination.
- Proxy settings
- HTTP address 127.0.0.1 and port 4444. Related: <browser profiles>/<FoxyProxy?>/<Privoxy>, <subscriptions>
- SSH tunnel settings
- To create the necessary tunnels run 'ssh -L7657:127.0.0.1:7657 -L4444:127.0.0.1:4444 $USER@$SERVER' or set the LocalForwards? in your ~/.ssh/config accordingly.
Communication
singular
- howtoirc
- Dear visitors, you can connect to the anonymous I2P IRC servers directly by adding a server with the address 127.0.0.1 and port 6668 (no proxy) in your client.
- I2P Status
- a <Twitter>-like microblogging service on I2P: http://status.h2ik.i2p/. There is also http://annontwitter.i2p/.
- I2P-Bote
- an I2P-internal, anonymous and secure (end-to-end encrypted) serverless e-mail system. For more information visit: http://i2pbote.i2p
- I2P-Messenger
- an I2P-internal, anonymous and secure (end-to-end encrypted) serverless instant messenger with support for file transfers. See http://echelon.i2p/qti2pmessenger.
- IM
- For I2P-internal instant messaging there is <I2P-Messenger>, furthermore we have the I2P-internal IRC network <Irc2P>.
- IRC servers
- I know of the following I2P IRC servers: irc.postman.i2p/irc.freshcoffee.i2p (here, <Irc2P>), irc.welterde.i2p and irc.telecomix.i2p. You cannot connect to regular internet IRC servers. See <IRC tunnel> and <SOCKS5 IRC poxy> for help on how to connect.
- Mail.i2p
- an I2P mail service. Your you@… account also works on the internet as you@…. You can use it to communicate with I2P and non-I2P users. See http://hq.postman.i2p/?page_id=4. Also ask me about <MUAs> and <I2P-Bote>.
- There are two very different email systems on I2P. Ask me about <mail.i2p> and <I2P-Bote>.
- Microblogging
- a form of blogging (like on Twitter). There is an I2P microblogging service called I2P Status at http://status.h2ik.i2p.
- News server
- There is a news server (<NNTP>) operated by welterde at nntp.welterde.i2p. To access it you need to create a new <tunnel> to point to that address and then set your <newsreader> to connect to localhost and the port you chose. Also see <newsreaders>.
- NNTP
- the Network News Transfer Protocol which is used for transporting Usenet news articles (netnews) between news servers and for reading and posting articles. Ask me about <news servers> and <newsreaders>.
- POP3
- a protocol used to retrieve email from a remote server. For <mail.i2p> see http://hq.postman.i2p/?page_id=11. POP3 support is also planned for <I2P-Bote>.
- Smigmacy
- Smigacy (which stands for Send Messages through I2pmail with Greater privACY) is an anonymity filter for SMTP, primarily intended to be used with Postman’s I2PMail service. See http://hq.postman.i2p/?page_id=35.
- SMTP
- a protocol used to transfer email. For <mail.i2p> see http://hq.postman.i2p/?page_id=10. STMP support is also planned for <I2P-Bote>.
- susimail
- Susimail is the resident webmail client that interfaces with postman's mail services. http://127.0.0.1:7657/susimail
- Syndie
- an open source system for operating distributed forums, offering a secure and consistent interface to various anonymous and non-anonymous content networks. More at http://syndie.i2p2.de/ and http://forum.i2p/viewforum.php?f=29.
- a micro-blogging platform. There are 2 similar services on I2P. See http://status.h2ik.i2p/ and http://annontwitter.i2p/. Also, zzz is on twitter at http://twitter.com/i2p/.
- wiki
- see http://ugha.i2p
plural
- IRC servers
- I know of the following I2P IRC servers: irc.postman.i2p/irc.freshcoffee.i2p (here), irc.welterde.i2p and irc.telecomix.i2p. You cannot connect to regular internet IRC servers. See <IRC tunnel> and <SOCKS5 IRC poxy> for help on how to connect.
- IRC tunnels
- The standard IRC tunnel listens on port 6668. To connect with xchat (for example) connect to 127.0.0.1/6668 (no proxy). Alternatively you can setup a <SOCKS5 IRC proxy>.
Dangers
singular
- Anonymity on I2P
- Anonymity is not a boolean - we are not trying to make something "perfectly anonymous", but instead are working at making attacks more and more expensive to mount. I2P is a low latency mix network, and there are limits to the anonymity offered by such a system, but the applications on top of I2P, such as Syndie, I2P mail, and I2PSnark extend it to offer both additional functionality and protection.
- Anonymity
- a broad subject. Most importantly it's not a boolean. You may want to ask me about the <disclaimer> or <staying safe>.
- Disclaimer
- I2P is still a work in progress. It should not be relied upon for "guaranteed" anonymity at this time, due to the relatively small size of the network and the lack of extensive academic review. It is not immune to to attacks from those with unlimited resources, and may never be, due to the inherent limitations of low-latency mix networks.
- Exit node sniffing
- a potential problem when routing unencrypted traffic through Tor or I2P to the web, because a malicious exit node/outproxy can easily sniff that traffic. This problem does not exist inside I2P or when using Tor's Hidden Services.
- Staying safe
- Staying safe on anonymous networks requires discipline regarding the information you give away as well as a secure and trustworthy computer system.
plural
Last modified 9 years ago
Last modified on Sep 15, 2010 1:44:13 PM
Attachments (1)
-
2010-07-29-dump.txt (47.6 KB) - added by 10 years ago.
enci2pedia's factoids (2010-07-29)
Download all attachments as: .zip