I read through some of the high level docs, but can someone simply explain how a user discovers other nodes in the network? I started reading the netDB docs [0] but it was pretty dense. [0] https://geti2p.net/en/docs/how/network-database
[deleted]
I2P: Invisible Internet Protocol
21–30 of 59 posts
Re: I2P: Invisible Internet Protocol
#22Earlier quoted context omitted.
>> My guess is the I2P gets more scrutiny from the US government, because it's much harder to break versus TOR How so? Is this what is alluded to by "onion vs garlic" routing design? http://resources.infosecinstitute.com/anonymizing-networks-t... (I can't get the I2P explanation/comparison on their official site right now; not sure it's me or them, haha.) Again, I read a while back. I am pleased to know it is more se…
>> How so? It's been a long time since i read about those subjects, but from what i remember - TOR is a low-latency network, which is required for regular web sites to work. This means the network can do little to randomize/mess with packet timing, and thus leaks packet timing which theoretically(and practically) can expose them to timing attacks. The onion network, on the other hand, does support high-latency connec…
Did you mean to refer to I2P in that last sentence?
Re: I2P: Invisible Internet Protocol
#23I2P developer here, feel free to ask me any questions.
Who is zzz? :)
Re: I2P: Invisible Internet Protocol
#24Earlier quoted context omitted.
From the Bootstrapping section of the link you provided.. >volunteers publish their netDb directories (or a subset) on the regular (non-i2p) network, and the URLs of these directories are hardcoded in I2P. When the router starts up for the first time, it automatically fetches from one of these URLs, selected at random.
OK, so you put your IP address into several centralized DB's on the regular internet, then when I2P starts it randomly fetches from one of those repositories.
The only not totally implausible alternative is broadcasting addresses over amateur radio
Re: I2P: Invisible Internet Protocol
#25Re: I2P: Invisible Internet Protocol
#26Earlier quoted context omitted.
>> How so? It's been a long time since i read about those subjects, but from what i remember - TOR is a low-latency network, which is required for regular web sites to work. This means the network can do little to randomize/mess with packet timing, and thus leaks packet timing which theoretically(and practically) can expose them to timing attacks. The onion network, on the other hand, does support high-latency connec…
Did you mean to refer to I2P in that last sentence?
True, thanks.
Re: I2P: Invisible Internet Protocol
#27Good to see I2P get some attention here.
For those who don't know about I2P:
* Anonymity network similar to TOR in some ways, but rather than focusing on getting someone out to the internet anonymously, I2P is a low-latency mix network with no out proxies. See: https://ritter.vg/blog-mix_and_onion_networks.html
* Virtually every I2P router relays traffic, unlike TOR the network is very "flat". Directory servers are replaced with a DHT called the netDB.
Recently I've been working on a Go implementation of the I2P router: https://github.com/hkparker/go-i2p. It isn't on the network yet, would be really interested in working with anyone who wants to contribute.
Re: I2P: Invisible Internet Protocol
#28Are there JVM-less I2P implementations?
Re: I2P: Invisible Internet Protocol
#29I2P developer here, feel free to ask me any questions.
Thanks for contributing to I2P!
Do you have any thoughts on HORNET? Could I2P benefit from a more stateless routing mechanism as opposed to tunnels in the far future?
Are any of the devs going to defcon this year? I tried to get a small meetup going last year in the privacy village but no turnout, would love to make something official.
I'm working on Go implementation here: https://github.com/hkparker/go-i2p. Haven't made to irc2p to introduce myself yet but I will. Are there any devs who might be interested in contributing?
Privacy of developers seems a priority. Without any detail of course, can you comment on how necessary this has been. Is it irresponsible of me to work on an implementation in the clear?
Re: I2P: Invisible Internet Protocol
#30I2P developer here, feel free to ask me any questions.
Thanks for contributing to I2P! Do you have any thoughts on HORNET? Could I2P benefit from a more stateless routing mechanism as opposed to tunnels in the far future? Are any of the devs going to defcon this year? I tried to get a small meetup going last year in the privacy village but no turnout, would love to make something official. I'm working on Go implementation here: https://github.com/hkparker/go-i2p . Haven'…
> Thanks for contributing to I2P!
;) My contributions are relatively minor and I2P (as well as other crypto systems) is something I really believe in.
> Do you have any thoughts on HORNET? Could I2P benefit from a more stateless routing mechanism as opposed to tunnels in the far future?
It's been a while since I read the HORNET paper, but as I remember it, HORNET relied heavily on ISP level cooperation which is just not realistic. However, the idea of reducing state is a very good one. Going forward I hope to see more cryptographic systems that aspire to reduce overall state.
> I'm working on Go implementation here: https://github.com/hkparker/go-i2p. Haven't made to irc2p to introduce myself yet but I will. Are there any devs who might be interested in contributing?
Currently there are 3 implementations of I2P apart from yours. The original java one, i2pd[1] and kovri[2]. We all cooperate and discuss specifications to maintain interoperability. However the alternative implementations are not maintained under the I2P project as the developers of them desire to be separate. I was previously unaware of your Go implementation, but you should definitely head over to #i2p-dev and say hi. You can find me under the nick hottuna there.
> Privacy of developers seems a priority. Without any detail of course, can you comment on how necessary this has been. Is it irresponsible of me to work on an implementation in the clear?
About privacy, people have taken various stances. Some a truly anonymous, some are semi anonymous, and some like me are not anonymous. Maintaining privacy for a while might be a good idea. You can always get less anonymous, but going the other way is harder.