I did out the math for what was necessary to control the entire path of 50% of the network traffic. I might post the resulting charts and stuff but when I did i

I did out the math for what was necessary to control the entire path of 50% of the network traffic. I might post the resulting charts and stuff but when I did it out a few months ago it required 12,000 nodes. Entry/Exit are sufficient when also combining timing attacks but why not go whole hog? Also the increased security from new-identitying every few minutes increases the chance that at least some of your traffic would be caught while this type of attack is going on. In reply to s_q_b: Amazon actually hosted this guy's demonstration, so at least one good cloud provider has in fact done this. Additionally, if you time your attack correctly and don't have persistent objectives, then it's pretty much moot that the spike is obvious because who checks the total amount of nodes frequently while surfing? Finally, if you do have persistent objectives, then you could mask it by introducing nodes by the dozen or so randomly spaced over a year or two. Edit: just to clarify: Not my paper. No one has commented to that effect yet, but I just realized that that could be a conclusion drawn. I've only done some analysis on this type of attack.