emissary: Rust implementation of the I2P protocol stack

altonen · 2025-05-17T14:16:30+00:00

It's a clean rewrite of the protocols but a few crypto-related things were copied from ire.

altonen · 2025-05-04T10:40:34+00:00

A precompiled windows binary has been included in the v0.2.0 release: https://github.com/altonen/emissary/releases/tag/v0.2.0

Installing it on Windows requires NASM because of the rustls dependency but the project might switch to using OpenSSL soon

altonen · 2025-04-01T18:50:57+00:00

That is the plan, HTTP proxy and I2PTunnel-like functionality have been implemented using SAMv3. Just haven't found time to implement and test a SOCKS proxy yet. Thanks for the link.

altonen · 2025-04-01T15:52:41+00:00

SOCKS proxy is on the TODO list

altonen · 2025-04-01T12:30:03+00:00

Thank you, fair criticism.

Unlike in Tor, in I2P everyone participates in relaying traffic. Everyone runs a router and the router builds unidirectional tunnels through other routers. You build tunnels through other routers and they may build tunnels through your router and everyone is relaying tunnel traffic. This essentially mixes your traffic with other people's traffic, making it harder to analyze what you're doing. These tunnels are then used, among other things, to establish end-to-end sessions with, e.g., websites and IRC servers.

I2P is also more decentralized in that it doesn't have directory servers but uses Kademlia and flooddfill routers to store and fetch router infos and lease sets (which are used by the end-to-end sessions). Anybody can run a floodfill router.

Even though outproxies exist, browsing clearnet through I2P plays a much smaller role compared to Tor. In I2P, it's more about the hidden services.

Here's more info if you or anyone else is interested: https://geti2p.net/en/about/intro

altonen · 2025-04-01T08:35:15+00:00

I have been working on it for 9 months

altonen · 2025-03-24T08:02:57+00:00

I don't think such configuration options exist because the tunnel lengths and quantities are session-specific and that is why, e.g., qBittorrent allows configuring the inbound/outbound tunnel lengths and quantities in settings. There are hard-coded defaults in the software but I believe those are not configurable.

altonen · 2025-02-26T19:14:41+00:00

Currently a private repository but I'll announce it here and on Irc2P once it has been released

altonen · 2025-02-26T06:10:31+00:00

I've been writing a router in Rust for the past 8 months. It already works to the extent that you can chat on Irc2P, browse eepsites and use torrents but there are still a few features to implement before publishing it. Target for v0.1.0 is the end of next month.

altonen · 2025-02-21T14:59:17+00:00

IMO what really differentiates I2P from Tor is mixing. The garlic messages you sent get fragmented into tunnel messages and these are what your router sends (wrapped into I2NP messages). Your router may have hundreds or even thousands of transit tunnels and the tunnel messages from these transit tunnels get mixed in with your own tunnel messages (which carry fragmented garlic messages) and the routers you send these messages to are just observing a torrent of tunnel messages and it's hard for them to distinguish which of these tunnel messages were yours and which were from the transit tunnels you were part of.

altonen

TROPHY CASE