News for hackers. Stuff that matters.
Re:The Trouble with CloudFlare by _Codemonkeyism on Friday April 01, 2016 @11:38AM (#11405600)
The main point I took away from the article, that from one exit node many users originate. Some users are spammer. They contaminate the exit node IP. CF blocks an IP for spam, but does not remove the block after some time (when the spammer moved on).
Re:The Trouble with CloudFlare by scurvy on Friday April 01, 2016 @11:43AM (#11405643)
That's definitely a legitimate point, but not the main point IMHO. The main point is that Tor makes zero effort to clean up the problem and uses the legitimate Tor users as helpless, scapegoated victims and a bullying tactic. "But think of the oppressed users!" Sorry, not buying it.

The blacklisted IP lifetime problem is real though. It's a problem I've had to raise several times with our product and network teams. People would see an abusive IP and just ban it...without a TTL or lifetime. This really upset me as they seemed to think that was OK not just for the time being, but that it was good enough. When I describe IPv6 to them, their faces just melt as it sinks in that they can't just keep banning IP's and must do something higher up the stack to detect and block fraud.

Re:The Trouble with CloudFlare by _Codemonkeyism on Monday April 04, 2016 @03:52AM (#11420113)
Interesting point, what would "Tor cleans up" mean?
Re:The Trouble with CloudFlare by ryandrake on Friday April 01, 2016 @11:53AM (#11405736)
What will happen when IPv6 takes off and anyone can just go get a unique, random, throwaway IP address each day? Do "IP reputation" systems work in such a world?
Re:The Trouble with CloudFlare by tonfa on Friday April 01, 2016 @12:21PM (#11406006)
I guess reputation will be based on /64, that's the most practical solution.
Re:The Trouble with CloudFlare by cronjobber on Friday April 01, 2016 @12:23PM (#11406042)
Maybe coalesce neighboring bad IPs and subnets into larger bad subnets.
Re:The Trouble with CloudFlare by unexistance on Friday April 01, 2016 @12:19PM (#11405978)
The somewhat-faster way to reduce this annoyance (I've been hit by this) is to 'block'/captcha the offending IPs for a time (depends on whatever metrics CloudFlare think is best) then unblock it.

At least this will reduce legitimate user's annoyance, instead of being blocked indefinitely

My own experience: Tried accessing wikialpha from work LAN, 'blocked' by endless captcha (for a few months already) and opening the said wiki from home network, all is perfectly fine...

well at least now I know why, still does NOT makes it OK from end-users perpective

Re:The Trouble with CloudFlare by Kalium on Friday April 01, 2016 @04:13PM (#11408178)
Given how much of TOR traffic is malicious (94%), what you propose would get all TOR traffic always considered malicious.
Re:The Trouble with CloudFlare by _Codemonkeyism on Monday April 04, 2016 @03:54AM (#11420117)
Care to share a source for "TOR traffic is malicious (94%)"?

What does malicious percentage of traffic in this case mean? Malicious sessions? IPs used? Packets? Users?

Re:The Trouble with CloudFlare by Kalium on Monday April 04, 2016 @02:11PM (#11423990)
The number is in the CloudFlare blog post that started this.

> Based on data across the CloudFlare network, 94% of requests that we see across the Tor network are per se malicious. That doesn’t mean they are visiting controversial content, but instead that they are automated requests designed to harm our customers.