I2P - Revision history

5.143.79.150: Added citations and links

2024-10-13T07:03:38Z

Added citations and links

← Previous revision		Revision as of 07:03, 13 October 2024
Line 51:		Line 51:
	I2P started in 2003 as a fork of [[Freenet]].<ref name="urlAnonymity Networks: VPNs, Tor, and I2P \| Restore Privacy">{{cite web \|url=https://restoreprivacy.com/anonymity-networks/ \|title=Anonymity Networks: VPNs, Tor, and I2P \| Restore Privacy \|date=3 February 2020 \|format= \|accessdate= \|archive-date=28 January 2021 \|archive-url=https://web.archive.org/web/20210128084403/https://restoreprivacy.com/anonymity-networks/ \|url-status=live }}</ref><ref>{{Citation \| url = https://geti2p.net/en/blog/ \| type = blog \| title = Get I2P \| access-date = 2013-12-24 \| archive-date = 2017-07-02 \| archive-url = https://web.archive.org/web/20170702010806/https://geti2p.net/en/blog/ \| url-status = live }}.</ref>		I2P started in 2003 as a fork of [[Freenet]].<ref name="urlAnonymity Networks: VPNs, Tor, and I2P \| Restore Privacy">{{cite web \|url=https://restoreprivacy.com/anonymity-networks/ \|title=Anonymity Networks: VPNs, Tor, and I2P \| Restore Privacy \|date=3 February 2020 \|format= \|accessdate= \|archive-date=28 January 2021 \|archive-url=https://web.archive.org/web/20210128084403/https://restoreprivacy.com/anonymity-networks/ \|url-status=live }}</ref><ref>{{Citation \| url = https://geti2p.net/en/blog/ \| type = blog \| title = Get I2P \| access-date = 2013-12-24 \| archive-date = 2017-07-02 \| archive-url = https://web.archive.org/web/20170702010806/https://geti2p.net/en/blog/ \| url-status = live }}.</ref>

	The network is strictly message-based, like [[Internet Protocol\|IP]], but a [[Library (computing)\|library]] is available to allow reliable [[Streaming algorithm\|streaming]] communication on top of it (similar to [[Non-blocking IO]]-based [[Transmission control protocol\|TCP]], although from version 0.6, a new ''Secure Semi-reliable'' [[User Datagram Protocol\|UDP]] transport is used<ref>{{cite web \|title=Secure Semireliable UDP (SSU) \|url=https://geti2p.net/en/docs/transport/ssu \|access-date=18 May 2023 \|archive-url=https://archive.today/20230906220752/https://geti2p.net/en/docs/transport/ssu \|archive-date=6 September 2023 \|website=geti2p.net}}</ref>). All communication is end-to-end encrypted (in total, four layers of encryption are used when sending a message) through [[garlic routing]],<ref>{{cite web\|url=https://geti2p.net/en/docs/how/garlic-routing\|title=Garlic Routing – I2P\|website=geti2p.net\|access-date=2017-12-12\|archive-date=2019-11-16\|archive-url=https://web.archive.org/web/20191116095738/https://geti2p.net/en/docs/how/garlic-routing\|url-status=live}}</ref> and even the [[Communication endpoint\|end points]] ("destinations") are [[cryptographic]] identifiers (essentially a pair of [[public key]]s), so that neither senders nor recipients of messages need to reveal their [[IP address]] to the other side or to third-party observers.		The network is strictly message-based, like [[Internet Protocol\|IP]], but a [[Library (computing)\|library]] is available to allow reliable [[Streaming algorithm\|streaming]] communication on top of it (similar to [[Non-blocking IO]]-based [[Transmission control protocol\|TCP]], although from version 0.6, a new ''Secure Semi-reliable'' [[User Datagram Protocol\|UDP]] transport is used<ref>{{cite web \|title=Secure Semireliable UDP (SSU) \|url=https://geti2p.net/en/docs/transport/ssu \|access-date=18 May 2023 \|archive-url=https://archive.today/20230906220752/https://geti2p.net/en/docs/transport/ssu \|archive-date=6 September 2023 \|website=geti2p.net}}</ref>). All communication is [[end-to-end encrypted]] (in total, four layers of encryption are used when sending a message) through [[garlic routing]],<ref>{{cite web\|url=https://geti2p.net/en/docs/how/garlic-routing\|title=Garlic Routing – I2P\|website=geti2p.net\|access-date=2017-12-12\|archive-date=2019-11-16\|archive-url=https://web.archive.org/web/20191116095738/https://geti2p.net/en/docs/how/garlic-routing\|url-status=live}}</ref> and even the [[Communication endpoint\|end points]] ("destinations") are [[cryptographic]] identifiers (essentially a pair of [[public key]]s), 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)<ref>{{Citation \| title = Invisible IP \| publisher = Source forge \| contribution = IIP \| contribution-url = http://invisibleip.sourceforge.net/iip/ \| access-date = 2012-02-11 \| archive-date = 2009-05-18 \| archive-url = https://web.archive.org/web/20090518155407/http://invisibleip.sourceforge.net/iip/ \| url-status = live }}.</ref> and [[Freenet]] communities, significant differences exist between their designs and concepts. IIP was an anonymous centralized [[Internet Relay Chat\|IRC]] server. Freenet is a [[censorship]]-resistant [[distributed data store]]. I2P is an [[Anonymous P2P\|anonymous peer-to-peer]] distributed communication layer designed to run ''any'' traditional internet service (e.g. [[Usenet]], [[email]], [[Internet Relay Chat\|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 (software)\|Squid]], or [[Domain Name System\|DNS]]).		Although many developers had been a part of the Invisible IRC Project (IIP)<ref>{{Citation \| title = Invisible IP \| publisher = Source forge \| contribution = IIP \| contribution-url = http://invisibleip.sourceforge.net/iip/ \| access-date = 2012-02-11 \| archive-date = 2009-05-18 \| archive-url = https://web.archive.org/web/20090518155407/http://invisibleip.sourceforge.net/iip/ \| url-status = live }}.</ref> and [[Freenet]] communities, significant differences exist between their designs and concepts. IIP was an anonymous centralized [[Internet Relay Chat\|IRC]] server. Freenet is a [[censorship]]-resistant [[distributed data store]]. I2P is an [[Anonymous P2P\|anonymous peer-to-peer]] distributed communication layer designed to run ''any'' traditional internet service (e.g. [[Usenet]], [[email]], [[Internet Relay Chat\|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 (software)\|Squid]], or [[Domain Name System\|DNS]]).
Line 284:		Line 284:
	[[File:I2PBote-inbox-0.4.png\|thumb\|A screenshot of the inbox of I2P-Bote.]]		[[File:I2PBote-inbox-0.4.png\|thumb\|A screenshot of the inbox of I2P-Bote.]]

	* ''I2P-Bote'' is a free, fully [[Decentralized computing\|decentralized]] and distributed anonymous email system with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .{{~~citation~~ ~~needed~~\|date=~~September~~ ~~2020~~}}		* ''I2P-Bote'' is a [[Free and open-source software\|free]], fully [[Decentralized computing\|decentralized]] and distributed anonymous [[email system]] with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-09-20 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-10-13 \|publisher=The I2P Project}}</ref>
	* 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.		* 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#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P{{cn\|date=February 2024}}		* [[Bitmessage#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P{{cn\|date=February 2024}}

	=== Instant messaging ===		=== Instant messaging ===
	* ''I2P-Messenger'' is a simple [[Qt (framework)\|Qt]]-based, serverless, end-to-end-encrypted [[instant messenger]] for I2P.<ref>{{Citation \| title = Introducing I2P \| url = https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| date = Nov 10, 2015 \| access-date = November 11, 2015 \| archive-date = November 25, 2015 \| archive-url = https://web.archive.org/web/20151125093633/https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| url-status = live }}</ref> 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. <!--"Thus, it is also a useful tool against data retention in a surveillance society" Is this the part that is soapboxy?--> In addition to messaging, [[file transfer]] is also supported.		* ''I2P-Messenger'' is a simple [[Qt (framework)\|Qt]]-based, serverless, [[end-to-end-encrypted]] [[instant messenger]] for I2P.<ref>{{Citation \| title = Introducing I2P \| url = https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| date = Nov 10, 2015 \| access-date = November 11, 2015 \| archive-date = November 25, 2015 \| archive-url = https://web.archive.org/web/20151125093633/https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| url-status = live }}</ref> 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. <!--"Thus, it is also a useful tool against data retention in a surveillance society" Is this the part that is soapboxy?--> In addition to messaging, [[file transfer]] is also supported.

	* ''I2P-Talk'' is another simple instant messenger incompatible with I2P-Messenger, but having the same security properties		* ''I2P-Talk'' is another simple instant messenger incompatible with I2P-Messenger, but having the same security properties

Anachronist: Reverted edit by 203.144.79.126 (talk) to last version by Annh07

2024-10-01T14:08:37Z

Reverted edit by 203.144.79.126 (talk) to last version by Annh07

← Previous revision		Revision as of 14:08, 1 October 2024
Line 1:		Line 1:
	{{Short description\|Free and open source project building an anonymous network}}		{{Short description\|Free and open source project building an anonymous network}}
	{{Primary sources\|~~https://github.com/i2p/i2p.i2p~~\|date=August 2017}}		{{Primary sources\|article\|date=August 2017}}

	{{Infobox software		{{Infobox software

203.144.79.126: https://github.com/i2p/i2p.i2p

2024-10-01T14:04:41Z

https://github.com/i2p/i2p.i2p

← Previous revision		Revision as of 14:04, 1 October 2024
Line 1:		Line 1:
	{{Short description\|Free and open source project building an anonymous network}}		{{Short description\|Free and open source project building an anonymous network}}
	{{Primary sources\|~~article~~\|date=August 2017}}		{{Primary sources\|https://github.com/i2p/i2p.i2p\|date=August 2017}}

	{{Infobox software		{{Infobox software

Annh07: Reverted 1 edit by Asdfqwerjkiuhbc (talk) to last revision by Andkore

2024-09-20T12:07:49Z

Reverted 1 edit by Asdfqwerjkiuhbc (talk) to last revision by Andkore

← Previous revision		Revision as of 12:07, 20 September 2024
Line 286:		Line 286:
	* ''I2P-Bote'' is a free, fully [[Decentralized computing\|decentralized]] and distributed anonymous email system with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .{{citation needed\|date=September 2020}}		* ''I2P-Bote'' is a free, fully [[Decentralized computing\|decentralized]] and distributed anonymous email system with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .{{citation needed\|date=September 2020}}
	* 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.		* 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#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P~~<ref>~~{{~~Cite web~~ \|~~title~~=~~IAS~~ ~~Blogger \|url=https://iasblogger.com/ \|access-date=~~2024~~-09-20 \|language=en-US~~}}~~</ref>~~		* [[Bitmessage#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P{{cn\|date=February 2024}}

	=== Instant messaging ===		=== Instant messaging ===

Asdfqwerjkiuhbc: /* Email */ Add a missing link on this page

2024-09-20T12:06:02Z

Email: Add a missing link on this page

← Previous revision		Revision as of 12:06, 20 September 2024
Line 286:		Line 286:
	* ''I2P-Bote'' is a free, fully [[Decentralized computing\|decentralized]] and distributed anonymous email system with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .{{citation needed\|date=September 2020}}		* ''I2P-Bote'' is a free, fully [[Decentralized computing\|decentralized]] and distributed anonymous email system with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .{{citation needed\|date=September 2020}}
	* 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.		* 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#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P{{cn\|~~date~~=~~February~~ 2024}}		* [[Bitmessage#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P<ref>{{Cite web \|title=IAS Blogger \|url=https://iasblogger.com/ \|access-date=2024-09-20 \|language=en-US}}</ref>

	=== Instant messaging ===		=== Instant messaging ===

Andkore at 23:41, 10 September 2024

2024-09-10T23:41:03Z

@@ Line 1: / Line 1: @@
-{{short description|Free and open source project building an anonymous network}}
+{{Short description|Free and open source project building an anonymous network}}
 {{Primary sources|article|date=August 2017}}
@@ Line 29: / Line 29: @@
 | language footnote =
 | genre = [[Anonymity application]], [[Overlay network]], [[mix network]], [[garlic routing|garlic router]], [[peer-to-peer]]
 | alexa =
 | website = {{URL|https://geti2p.net/}}

154.144.248.76: /* Vulnerabilities */ corrected typo : eepsites => websites

2024-09-05T08:46:20Z

Vulnerabilities: corrected typo : eepsites => websites

← Previous revision		Revision as of 08:46, 5 September 2024
Line 335:		Line 335:
	A [[Zero-day (computing)\|zero-day vulnerability]] was discovered for I2P in 2014, and was exploited to [[Data re-identification\|de-anonymize]] at least 30,000 users. This included users of the operating system [[Tails (operating system)\|Tails]].<ref>{{Cite web\|last=Storm\|first=Darlene\|date=2014-07-24\|title=Zero-day broker exploits vulnerability in I2P to de-anonymize Tails users\|url=https://www.computerworld.com/article/2476563/zero-day-broker-exploits-vulnerability-in-i2p-to-de-anonymize-tails-users.html\|url-status=live\|access-date=2021-03-13\|website=[[Computerworld]]\|language=en\|archive-date=2020-09-29\|archive-url=https://web.archive.org/web/20200929102557/https://www.computerworld.com/article/2476563/zero-day-broker-exploits-vulnerability-in-i2p-to-de-anonymize-tails-users.html}}</ref> This vulnerability was later patched.<ref>{{Cite web\|date=2014-07-29\|title=I2P patched against de-anonymizing 0-day, Tails integration still to follow\|url=https://www.helpnetsecurity.com/2014/07/29/i2p-patched-against-de-anonymizing-0-day-tails-integration-still-to-follow/\|access-date=2021-03-13\|website=Help Net Security\|language=en-US\|archive-date=2020-12-10\|archive-url=https://web.archive.org/web/20201210174852/https://www.helpnetsecurity.com/2014/07/29/i2p-patched-against-de-anonymizing-0-day-tails-integration-still-to-follow/\|url-status=live}}</ref><ref>{{Cite web\|title=0.9.14 Release – Blog – I2P\|url=https://geti2p.net/en/blog/post/2014/07/26/0.9.14-Release\|access-date=2021-03-13\|website=geti2p.net\|archive-date=2021-04-22\|archive-url=https://web.archive.org/web/20210422103231/https://geti2p.net/en/blog/post/2014/07/26/0.9.14-Release\|url-status=live}}</ref>		A [[Zero-day (computing)\|zero-day vulnerability]] was discovered for I2P in 2014, and was exploited to [[Data re-identification\|de-anonymize]] at least 30,000 users. This included users of the operating system [[Tails (operating system)\|Tails]].<ref>{{Cite web\|last=Storm\|first=Darlene\|date=2014-07-24\|title=Zero-day broker exploits vulnerability in I2P to de-anonymize Tails users\|url=https://www.computerworld.com/article/2476563/zero-day-broker-exploits-vulnerability-in-i2p-to-de-anonymize-tails-users.html\|url-status=live\|access-date=2021-03-13\|website=[[Computerworld]]\|language=en\|archive-date=2020-09-29\|archive-url=https://web.archive.org/web/20200929102557/https://www.computerworld.com/article/2476563/zero-day-broker-exploits-vulnerability-in-i2p-to-de-anonymize-tails-users.html}}</ref> This vulnerability was later patched.<ref>{{Cite web\|date=2014-07-29\|title=I2P patched against de-anonymizing 0-day, Tails integration still to follow\|url=https://www.helpnetsecurity.com/2014/07/29/i2p-patched-against-de-anonymizing-0-day-tails-integration-still-to-follow/\|access-date=2021-03-13\|website=Help Net Security\|language=en-US\|archive-date=2020-12-10\|archive-url=https://web.archive.org/web/20201210174852/https://www.helpnetsecurity.com/2014/07/29/i2p-patched-against-de-anonymizing-0-day-tails-integration-still-to-follow/\|url-status=live}}</ref><ref>{{Cite web\|title=0.9.14 Release – Blog – I2P\|url=https://geti2p.net/en/blog/post/2014/07/26/0.9.14-Release\|access-date=2021-03-13\|website=geti2p.net\|archive-date=2021-04-22\|archive-url=https://web.archive.org/web/20210422103231/https://geti2p.net/en/blog/post/2014/07/26/0.9.14-Release\|url-status=live}}</ref>

	A 2017 study examining how [[Forensic science\|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 name registrar\|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 engineering (security)\|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.<ref name=":1" />		A 2017 study examining how [[Forensic science\|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 websites a user of a later-seized machine was interested in may also be inferred. The study identified a "trusted" I2P [[Domain name registrar\|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 engineering (security)\|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.<ref name=":1" />

	== I2PCon ==		== I2PCon ==

MichielN: /* General networking */ Added archived version of source

2024-07-21T13:20:52Z

General networking: Added archived version of source

← Previous revision		Revision as of 13:20, 21 July 2024
Line 254:		Line 254:
	* ''BOB'' (''Basic Open Bridge'') is a less complex app to router protocol similar to "SAM"<ref>{{Citation \| title = API \| contribution-url = https://geti2p.net/en/docs/api/bob \| contribution = BOB \| publisher = Get I2P \| access-date = 2013-12-24 \| archive-date = 2013-12-24 \| archive-url = https://web.archive.org/web/20131224112753/https://geti2p.net/en/docs/api/bob \| url-status = live }}.</ref>		* ''BOB'' (''Basic Open Bridge'') is a less complex app to router protocol similar to "SAM"<ref>{{Citation \| title = API \| contribution-url = https://geti2p.net/en/docs/api/bob \| contribution = BOB \| publisher = Get I2P \| access-date = 2013-12-24 \| archive-date = 2013-12-24 \| archive-url = https://web.archive.org/web/20131224112753/https://geti2p.net/en/docs/api/bob \| url-status = live }}.</ref>
	* ''Orchid'' Outproxy [[Tor (anonymity network)\|Tor]] plugin<ref>{{cite web\|url=https://github.com/subgraph/Orchid\|title=GitHub – subgraph/Orchid\|date=7 March 2019\|via=GitHub\|access-date=20 October 2017\|archive-date=9 August 2017\|archive-url=https://web.archive.org/web/20170809050525/https://github.com/subgraph/Orchid\|url-status=live}}</ref>		* ''Orchid'' Outproxy [[Tor (anonymity network)\|Tor]] plugin<ref>{{cite web\|url=https://github.com/subgraph/Orchid\|title=GitHub – subgraph/Orchid\|date=7 March 2019\|via=GitHub\|access-date=20 October 2017\|archive-date=9 August 2017\|archive-url=https://web.archive.org/web/20170809050525/https://github.com/subgraph/Orchid\|url-status=live}}</ref>
	* As of version 2.6.0, released in July 2024, I2P no longer allows I2P access over Tor connections.<ref>{{Cite web \|title=I2P 2.6.0 Release - Blog - I2P \|url=https://geti2p.net/en/blog/post/2024/07/19/2.6.0-Release \|access-date=2024-07-21 \|website=geti2p.net}}</ref>		* As of version 2.6.0, released in July 2024, I2P no longer allows I2P access over Tor connections.<ref>{{Cite web \|last=idk \|title=I2P 2.6.0 Release - Blog - I2P \|url=https://geti2p.net/en/blog/post/2024/07/19/2.6.0-Release \|url-status=live \|archive-url=https://web.archive.org/web/20240721131455/https://geti2p.net/en/blog/post/2024/07/19/2.6.0-Release \|archive-date=2024-07-21 \|access-date=2024-07-21 \|website=geti2p.net}}</ref>

	=== Chat ===		=== Chat ===

MichielN: /* General networking */ No more I2P-over-Tor

2024-07-21T13:16:46Z

General networking: No more I2P-over-Tor

← Previous revision		Revision as of 13:16, 21 July 2024
Line 254:		Line 254:
	* ''BOB'' (''Basic Open Bridge'') is a less complex app to router protocol similar to "SAM"<ref>{{Citation \| title = API \| contribution-url = https://geti2p.net/en/docs/api/bob \| contribution = BOB \| publisher = Get I2P \| access-date = 2013-12-24 \| archive-date = 2013-12-24 \| archive-url = https://web.archive.org/web/20131224112753/https://geti2p.net/en/docs/api/bob \| url-status = live }}.</ref>		* ''BOB'' (''Basic Open Bridge'') is a less complex app to router protocol similar to "SAM"<ref>{{Citation \| title = API \| contribution-url = https://geti2p.net/en/docs/api/bob \| contribution = BOB \| publisher = Get I2P \| access-date = 2013-12-24 \| archive-date = 2013-12-24 \| archive-url = https://web.archive.org/web/20131224112753/https://geti2p.net/en/docs/api/bob \| url-status = live }}.</ref>
	* ''Orchid'' Outproxy [[Tor (anonymity network)\|Tor]] plugin<ref>{{cite web\|url=https://github.com/subgraph/Orchid\|title=GitHub – subgraph/Orchid\|date=7 March 2019\|via=GitHub\|access-date=20 October 2017\|archive-date=9 August 2017\|archive-url=https://web.archive.org/web/20170809050525/https://github.com/subgraph/Orchid\|url-status=live}}</ref>		* ''Orchid'' Outproxy [[Tor (anonymity network)\|Tor]] plugin<ref>{{cite web\|url=https://github.com/subgraph/Orchid\|title=GitHub – subgraph/Orchid\|date=7 March 2019\|via=GitHub\|access-date=20 October 2017\|archive-date=9 August 2017\|archive-url=https://web.archive.org/web/20170809050525/https://github.com/subgraph/Orchid\|url-status=live}}</ref>
			* As of version 2.6.0, released in July 2024, I2P no longer allows I2P access over Tor connections.<ref>{{Cite web \|title=I2P 2.6.0 Release - Blog - I2P \|url=https://geti2p.net/en/blog/post/2024/07/19/2.6.0-Release \|access-date=2024-07-21 \|website=geti2p.net}}</ref>

	=== Chat ===		=== Chat ===

Brandon: −Category:Anonymity networks; −Category:Cryptographic protocols; −Category:Mix networks; −Category:Onion routing using HotCat

2024-07-09T16:27:00Z

−Category:Anonymity networks; −Category:Cryptographic protocols; −Category:Mix networks; −Category:Onion routing using HotCat

← Previous revision		Revision as of 16:27, 9 July 2024
Line 387:		Line 387:

	[[Category:I2P\| ]]		[[Category:I2P\| ]]
	[[Category:Anonymity networks]]
	[[Category:Anonymous file sharing networks]]		[[Category:Anonymous file sharing networks]]
	[[Category:Application layer protocols]]		[[Category:Application layer protocols]]
Line 394:		Line 393:
	[[Category:Cross-platform software]]		[[Category:Cross-platform software]]
	[[Category:Cryptographic software]]		[[Category:Cryptographic software]]
	[[Category:Cryptographic protocols]]
	[[Category:Dark web]]		[[Category:Dark web]]
	[[Category:Distributed data storage]]		[[Category:Distributed data storage]]
Line 413:		Line 411:
	[[Category:Internet privacy software]]		[[Category:Internet privacy software]]
	[[Category:Key-based routing]]		[[Category:Key-based routing]]
	[[Category:Mix networks]]
	[[Category:Onion routing]]
	[[Category:Overlay networks]]		[[Category:Overlay networks]]
	[[Category:Peer-to-peer computing]]		[[Category:Peer-to-peer computing]]

← Previous revision		Revision as of 07:03, 13 October 2024
Line 51:		Line 51:
	I2P started in 2003 as a fork of [[Freenet]].<ref name="urlAnonymity Networks: VPNs, Tor, and I2P \| Restore Privacy">{{cite web \|url=https://restoreprivacy.com/anonymity-networks/ \|title=Anonymity Networks: VPNs, Tor, and I2P \| Restore Privacy \|date=3 February 2020 \|format= \|accessdate= \|archive-date=28 January 2021 \|archive-url=https://web.archive.org/web/20210128084403/https://restoreprivacy.com/anonymity-networks/ \|url-status=live }}</ref><ref>{{Citation \| url = https://geti2p.net/en/blog/ \| type = blog \| title = Get I2P \| access-date = 2013-12-24 \| archive-date = 2017-07-02 \| archive-url = https://web.archive.org/web/20170702010806/https://geti2p.net/en/blog/ \| url-status = live }}.</ref>		I2P started in 2003 as a fork of [[Freenet]].<ref name="urlAnonymity Networks: VPNs, Tor, and I2P \| Restore Privacy">{{cite web \|url=https://restoreprivacy.com/anonymity-networks/ \|title=Anonymity Networks: VPNs, Tor, and I2P \| Restore Privacy \|date=3 February 2020 \|format= \|accessdate= \|archive-date=28 January 2021 \|archive-url=https://web.archive.org/web/20210128084403/https://restoreprivacy.com/anonymity-networks/ \|url-status=live }}</ref><ref>{{Citation \| url = https://geti2p.net/en/blog/ \| type = blog \| title = Get I2P \| access-date = 2013-12-24 \| archive-date = 2017-07-02 \| archive-url = https://web.archive.org/web/20170702010806/https://geti2p.net/en/blog/ \| url-status = live }}.</ref>

	The network is strictly message-based, like [[Internet Protocol\|IP]], but a [[Library (computing)\|library]] is available to allow reliable [[Streaming algorithm\|streaming]] communication on top of it (similar to [[Non-blocking IO]]-based [[Transmission control protocol\|TCP]], although from version 0.6, a new ''Secure Semi-reliable'' [[User Datagram Protocol\|UDP]] transport is used<ref>{{cite web \|title=Secure Semireliable UDP (SSU) \|url=https://geti2p.net/en/docs/transport/ssu \|access-date=18 May 2023 \|archive-url=https://archive.today/20230906220752/https://geti2p.net/en/docs/transport/ssu \|archive-date=6 September 2023 \|website=geti2p.net}}</ref>). All communication is end-to-end encrypted (in total, four layers of encryption are used when sending a message) through [[garlic routing]],<ref>{{cite web\|url=https://geti2p.net/en/docs/how/garlic-routing\|title=Garlic Routing – I2P\|website=geti2p.net\|access-date=2017-12-12\|archive-date=2019-11-16\|archive-url=https://web.archive.org/web/20191116095738/https://geti2p.net/en/docs/how/garlic-routing\|url-status=live}}</ref> and even the [[Communication endpoint\|end points]] ("destinations") are [[cryptographic]] identifiers (essentially a pair of [[public key]]s), so that neither senders nor recipients of messages need to reveal their [[IP address]] to the other side or to third-party observers.		The network is strictly message-based, like [[Internet Protocol\|IP]], but a [[Library (computing)\|library]] is available to allow reliable [[Streaming algorithm\|streaming]] communication on top of it (similar to [[Non-blocking IO]]-based [[Transmission control protocol\|TCP]], although from version 0.6, a new ''Secure Semi-reliable'' [[User Datagram Protocol\|UDP]] transport is used<ref>{{cite web \|title=Secure Semireliable UDP (SSU) \|url=https://geti2p.net/en/docs/transport/ssu \|access-date=18 May 2023 \|archive-url=https://archive.today/20230906220752/https://geti2p.net/en/docs/transport/ssu \|archive-date=6 September 2023 \|website=geti2p.net}}</ref>). All communication is [[end-to-end encrypted]] (in total, four layers of encryption are used when sending a message) through [[garlic routing]],<ref>{{cite web\|url=https://geti2p.net/en/docs/how/garlic-routing\|title=Garlic Routing – I2P\|website=geti2p.net\|access-date=2017-12-12\|archive-date=2019-11-16\|archive-url=https://web.archive.org/web/20191116095738/https://geti2p.net/en/docs/how/garlic-routing\|url-status=live}}</ref> and even the [[Communication endpoint\|end points]] ("destinations") are [[cryptographic]] identifiers (essentially a pair of [[public key]]s), 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)<ref>{{Citation \| title = Invisible IP \| publisher = Source forge \| contribution = IIP \| contribution-url = http://invisibleip.sourceforge.net/iip/ \| access-date = 2012-02-11 \| archive-date = 2009-05-18 \| archive-url = https://web.archive.org/web/20090518155407/http://invisibleip.sourceforge.net/iip/ \| url-status = live }}.</ref> and [[Freenet]] communities, significant differences exist between their designs and concepts. IIP was an anonymous centralized [[Internet Relay Chat\|IRC]] server. Freenet is a [[censorship]]-resistant [[distributed data store]]. I2P is an [[Anonymous P2P\|anonymous peer-to-peer]] distributed communication layer designed to run ''any'' traditional internet service (e.g. [[Usenet]], [[email]], [[Internet Relay Chat\|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 (software)\|Squid]], or [[Domain Name System\|DNS]]).		Although many developers had been a part of the Invisible IRC Project (IIP)<ref>{{Citation \| title = Invisible IP \| publisher = Source forge \| contribution = IIP \| contribution-url = http://invisibleip.sourceforge.net/iip/ \| access-date = 2012-02-11 \| archive-date = 2009-05-18 \| archive-url = https://web.archive.org/web/20090518155407/http://invisibleip.sourceforge.net/iip/ \| url-status = live }}.</ref> and [[Freenet]] communities, significant differences exist between their designs and concepts. IIP was an anonymous centralized [[Internet Relay Chat\|IRC]] server. Freenet is a [[censorship]]-resistant [[distributed data store]]. I2P is an [[Anonymous P2P\|anonymous peer-to-peer]] distributed communication layer designed to run ''any'' traditional internet service (e.g. [[Usenet]], [[email]], [[Internet Relay Chat\|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 (software)\|Squid]], or [[Domain Name System\|DNS]]).
Line 284:		Line 284:
	[[File:I2PBote-inbox-0.4.png\|thumb\|A screenshot of the inbox of I2P-Bote.]]		[[File:I2PBote-inbox-0.4.png\|thumb\|A screenshot of the inbox of I2P-Bote.]]

	* ''I2P-Bote'' is a free, fully [[Decentralized computing\|decentralized]] and distributed anonymous email system with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .{{~~citation~~ ~~needed~~\|date=~~September~~ ~~2020~~}}		* ''I2P-Bote'' is a [[Free and open-source software\|free]], fully [[Decentralized computing\|decentralized]] and distributed anonymous [[email system]] with a strong focus on security.<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-03-06 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-03-08 \|publisher=The I2P Project}}</ref> It supports multiple identities and does not expose email [[metadata]]. {{As of \| 2015}}, it is still considered [[beta version\|beta software]]. I2P-Bote is accessible via the I2P [[web application\|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 [[Pretty Good Privacy\|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 [[Node (networking)\|nodes]] relaying the mails do not know the sender, and apart from sender and receiver, only the end of the high-[[Network latency\|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 .<ref>{{Citation \|title=i2p/i2p.i2p-bote \|date=2024-09-20 \|url=https://github.com/i2p/i2p.i2p-bote \|access-date=2024-10-13 \|publisher=The I2P Project}}</ref>
	* 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.		* 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#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P{{cn\|date=February 2024}}		* [[Bitmessage#Bitmessage.ch\|Bitmessage.ch]] can be used over I2P{{cn\|date=February 2024}}

	=== Instant messaging ===		=== Instant messaging ===
	* ''I2P-Messenger'' is a simple [[Qt (framework)\|Qt]]-based, serverless, end-to-end-encrypted [[instant messenger]] for I2P.<ref>{{Citation \| title = Introducing I2P \| url = https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| date = Nov 10, 2015 \| access-date = November 11, 2015 \| archive-date = November 25, 2015 \| archive-url = https://web.archive.org/web/20151125093633/https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| url-status = live }}</ref> 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. <!--"Thus, it is also a useful tool against data retention in a surveillance society" Is this the part that is soapboxy?--> In addition to messaging, [[file transfer]] is also supported.		* ''I2P-Messenger'' is a simple [[Qt (framework)\|Qt]]-based, serverless, [[end-to-end-encrypted]] [[instant messenger]] for I2P.<ref>{{Citation \| title = Introducing I2P \| url = https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| date = Nov 10, 2015 \| access-date = November 11, 2015 \| archive-date = November 25, 2015 \| archive-url = https://web.archive.org/web/20151125093633/https://geti2p.net/en/docs/how/tech-intro#app.i2pmessenger \| url-status = live }}</ref> 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. <!--"Thus, it is also a useful tool against data retention in a surveillance society" Is this the part that is soapboxy?--> In addition to messaging, [[file transfer]] is also supported.

	* ''I2P-Talk'' is another simple instant messenger incompatible with I2P-Messenger, but having the same security properties		* ''I2P-Talk'' is another simple instant messenger incompatible with I2P-Messenger, but having the same security properties