186

Reminder: seeders, please seed on I2P (infosec.pub)

submitted 3 months ago by Findmysec@infosec.pub to c/piracy@lemmy.dbzer0.com

73 comments fedilink hide all child comments

Regular users in Sweden are in danger because a corporation needs to fill their pockets. Studios are suing your ISPs to get to you.

Use I2P. It will hide your IP address (among the many things it can do), afford you more privacy and allow you to torrent freely, even without a VPN/seedbox. The catch? You'll have to add the I2P trackers to your torrent.

I believe I2P is the way forward for piracy and I look forward to it getting bigger than it already is.

you are viewing a single comment's thread
view the rest of the comments

[-] melroy@kbin.melroy.org 18 points 3 months ago

https://geti2p.net/en/ looks like Tor. but it is not the same?

[-] sploodged@lemmy.dbzer0.com 31 points 3 months ago

similar yes but not the same. tor held together by volunteer that run nodes, i2p everyone is a node. tor good for clearnet things, i2p good for in-network things. torrenting in i2p is good for i2p, not tor. torrenting in i2p stays in the i2p network, doesn't go through exit nodes. there's only about 3 of those. it's torrenting as a darknet hidden service.

[-] melroy@kbin.melroy.org 20 points 3 months ago

Yeah, thanks for clearing this up. I was also reading: https://geti2p.net/en/comparison/tor if people want to know more in depth.

[-] melroy@kbin.melroy.org 1 points 3 months ago

After reading that whole page, I think your point is missing.. The use case of Tor and i2p isn't correctly explained on that site.

[-] Findmysec@infosec.pub 9 points 3 months ago

I2P is P2P, TOR is not. That is the gist of the matter

[-] sploodged@lemmy.dbzer0.com 4 points 3 months ago

yeah some of the docs on the official site lean more technical than practical

[-] AlexWIWA@lemmy.ml 11 points 3 months ago

Does being a node open one to liability?

[-] Findmysec@infosec.pub 6 points 3 months ago

Unless there's a zero-day, no. All traffic is encrypted and it should be impossible to correlate traffic chunks to identities like that

[-] Andromxda@lemmy.dbzer0.com 5 points 3 months ago* (last edited 3 months ago)

No, since they don't act as exit nodes (they're called outproxies in I2P), unless you specifically configure that. It's like running a Tor middle/guard relay. I2P was specifically designed that way, so everyone can use I2P and be a node by default without causing any trouble.

[-] 8andage@sh.itjust.works 2 points 3 months ago

I tried to find the answer to this in i2p docs, maybe you would know more

As I understand, i2p traffic still needs to send packets over TCP/IP, so what stops the nodes you communicate with from knowing your IP? Its the only thing that makes me cagey about it since other p2p services like local game servers require sharing your IP to work. Hoping to get back into torrenting, thanks!

[-] sploodged@lemmy.dbzer0.com 3 points 3 months ago* (last edited 3 months ago)

Here's the scary sounding part that can be counterintuitive. The routers you're communicating with do know your ip, since they have to like you mentioned. Your ip address is also in i2p's DHT as a "router info" which functions as a network addressbook for routers and services so things can be found without needing a centralized lookup service. Again, because for the network to work, routers need to be able to find eachother, or they can't communicate.

But, routers function on a need to know basis. i2p uses separate up and down links for each tunnel, and your side of the tunnel by default has 3 hops. other side usually also has 3 hops. typical unidirectional tunnel looks like this with total of 7 hops:

A-x-x-x=x-x-x-B

None of the chains in the link know what position they're in (except for the endpoints). They also don't know how long the whole tunnel is. The sender and receiver only know their parts of the tunnel. On the dht side, by design no single router has a whole view of the network, but there isn't a whole lot of information you get from that other than knowing that person at stated ip address uses i2p, which your isp would be able to tell for example anyway just like using tor or a vpn. There's no reason to try to obfuscate that except for getting around restrictive countries firewalls.

The way i made sense of it was like you have an envelope that is inside several other envelopes, with each envelope representing a layer of encryption. You get an envelope from kevin, so you know kevin. You open the envelope and see another envelope addressed to george, you give the envelope to him. So you know kevin and george. But the rest is unknown to you. You don't know who the true originator of the envelope is or where the message is ultimately going.

Not a perfect analogy, but because of this the ultimate sender and receiver are blind to each others ip address. It's layered encryption allowing this to happen which is similar to onion routing. Called garlic routing in i2p since there are some tweaks.

https://geti2p.net/en/docs/how/garlic-routing