The potential for timing attacks has been known since the beginning of Tor. In other words, more than a decade. But that doesn’t mean you can’t defend against it. One way to defend against it is by having more nodes. Another way is to write clients that take into account the potential for timing attacks. Both of these were specifically mentioned in the article.
Based on what was in the article and what’s in the history books, I’m not sure how to interpret your comment in a constructive way. Is there anything more specific you meant, that isn’t contradicted by what’s in the article?
Before you use I2P, use Basic Computer Hygiene Always! Apply your OS vendor provided software updates in a prompt manner. Be aware of the state of your firewall and anti-virus status if you use one. Always get your software from authentic sources.
It may be dangerous to use I2P in what the project calls “Strict Countries”
Most I2P peers are not in those strict countries and the ones that are, are placed in “Hidden Mode” where they interact with the rest of the network in more limited ways, so that they are less visible to network observers.
Unlike Tor, “exit nodes” - or “outproxies” as they are referred to on the I2P network - are not an inherent part of the network. Only volunteers who specifically set up and run separate applications will relay traffic to the regular Internet. There are very, very few of these.
There is an outproxy guide available on our forums, if you would like to learn more about running an outproxy.
If you are hosting something sensitive, then your services will go down at the same time that your router goes down. Someone who observes your downtime and correlates it to real-world events could probably de-anonymize you with enough effort.
I2P has defenses available against this like multihoming or Tahoe-LAFS
I2P does not encrypt the Internet, neither does Tor - for example, through Transport Layer Security (TLS). I2P and Tor both aim to transport your traffic as-is securely and anonymously over the corresponding network, to its destination.
In addition, you may be vulnerable to collusion between the outproxy operator and operators of other I2P services, if you use the same tunnels (“shared clients”).
In theory, if you’re accessing the clearnet, then it is no better or worse than TOR. It is a little better if you’re stay in I2P land.
Don’t listen to me or him. If you’re reading this, go to the FAQ (https://geti2p.net/en/faq) and make your own decisions.
TOR is obvious too to someone snooping on your network, unless you’re using bridges (and that’s hit or miss). If you don’t want someone to know you’re using I2P, use OpenVPN and mask your traffic as HTTPS.
You’re going to have to explain better about “I2P not masking your traffic” and especially about “someone identifying you” - timing attacks are possible in both cases and the I2P Devs have mitigations against it. Please provide sources which define how I2P is weaker and more susceptible to TOR against network forensics
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
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.
Ok, technically still vulnerable in the sense that if you transfer a huge file in excess of other parts of the bundle, it might be identifiable by a bad actor, but that’s really misleading, since i2p has a lot of built in logic that makes that scenario pretty unlikely.
Not only huge files. At the end of the article the author goes on about changing the load or manipulating the timing of the traffic.
For both you need to be part of the network and (to some degree) the traffic you want to trace needs to go through a node you are controlling if i understand it correctly.
With increasing size it becomes more difficult.
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.
The potential for timing attacks has been known since the beginning of Tor. In other words, more than a decade. But that doesn’t mean you can’t defend against it. One way to defend against it is by having more nodes. Another way is to write clients that take into account the potential for timing attacks. Both of these were specifically mentioned in the article.
Based on what was in the article and what’s in the history books, I’m not sure how to interpret your comment in a constructive way. Is there anything more specific you meant, that isn’t contradicted by what’s in the article?
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
Confirmed the troll.
From the FAQ:
In theory, if you’re accessing the clearnet, then it is no better or worse than TOR. It is a little better if you’re stay in I2P land.
Don’t listen to me or him. If you’re reading this, go to the FAQ (https://geti2p.net/en/faq) and make your own decisions.
I2p lacks the ability to mask your traffic. It is obvious that you use i2p and someone could identity you from analyzing the network for long enough
TOR is obvious too to someone snooping on your network, unless you’re using bridges (and that’s hit or miss). If you don’t want someone to know you’re using I2P, use OpenVPN and mask your traffic as HTTPS.
You’re going to have to explain better about “I2P not masking your traffic” and especially about “someone identifying you” - timing attacks are possible in both cases and the I2P Devs have mitigations against it. Please provide sources which define how I2P is weaker and more susceptible to TOR against network forensics
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
You linked an article that doesn’t say anything to back up your claim. Why do you say i2p is vulnerable to timing attacks?
First sentence. Check up the linked article as source.
Ok, technically still vulnerable in the sense that if you transfer a huge file in excess of other parts of the bundle, it might be identifiable by a bad actor, but that’s really misleading, since i2p has a lot of built in logic that makes that scenario pretty unlikely.
Not only huge files. At the end of the article the author goes on about changing the load or manipulating the timing of the traffic.
For both you need to be part of the network and (to some degree) the traffic you want to trace needs to go through a node you are controlling if i understand it correctly. With increasing size it becomes more difficult.
I would also like to see prove for your claim.
First sentence. Check up the linked article as source.