it has higher latency, even variable latency if you set up variable hops, and everyone routes the traffic of a lot of other users, so a lot of data they can gather from timing info is noise by default
Yes it has better defenses against timing attacks. Just alone the fact that multiple packets are bundled together makes it harder to identify the route a single package used.
Also, it seems that I2P is more vulnerable against deanonymization when leaving the hidden network, i think the official I2P faq has some info about that, but have not read up upon it myself.
Also, it seems that I2P is more vulnerable against deanonymization when leaving the hidden network, i think the official I2P faq has some info about that, but have not read up upon it myself.
on a quick look I did not find such a mention, but in any case in addition to that, I2P users often don’t have such a fortified browser as Tor users do, so that’s also something to count with.
and maybe it’s not a good idea either to just reconfigure a Tor browser profile for I2P
Garlic routing[1] is a variant of onion routing that encrypts multiple messages together to make it more difficult[2] for attackers to perform traffic analysis and to increase the speed of data transfer.[3]
First sentence. Check up the linked article as source.
This attack has been known for years now. And tor is simply not able to defend against it without a complete redesign.
deleted by creator
Yes, sorry i worded it incorrectly you can try to make it harder but timing attacks are still possible.
Nope, just a summary that this is just old news. There is nothing new in the article.
Redesign being I2P
I2p has issues that can more easily lead to deanonymization attacks. It says it on the FAQ
Nope, I2P is still vulnerable to timing attacks. https://en.m.wikipedia.org/wiki/Garlic_routing
isn’t it less vulnerable, though?
it has higher latency, even variable latency if you set up variable hops, and everyone routes the traffic of a lot of other users, so a lot of data they can gather from timing info is noise by default
Yes it has better defenses against timing attacks. Just alone the fact that multiple packets are bundled together makes it harder to identify the route a single package used.
Also, it seems that I2P is more vulnerable against deanonymization when leaving the hidden network, i think the official I2P faq has some info about that, but have not read up upon it myself.
on a quick look I did not find such a mention, but in any case in addition to that, I2P users often don’t have such a fortified browser as Tor users do, so that’s also something to count with.
and maybe it’s not a good idea either to just reconfigure a Tor browser profile for I2P
I would also like to see prove for your claim.
First sentence. Check up the linked article as source.