@robocoder opened this Issue on January 5th 2011 Contributor

In [3155], we added a filter based on the User-Agent.

However, BadBehaviour continues to release updates based on IP ranges (using CIDR notation), i.e.,

  • 207.46.0.0/16
  • 65.52.0.0/14
  • 207.68.128.0/18
  • 207.68.192.0/20
  • 64.4.0.0/18
  • 157.54.0.0/15
  • 157.60.0.0/16
  • 157.56.0.0/14

We need to verify that our filter still works.

@mattab commented on April 28th 2011 Member

Maybe, this is a quick fix now that CIDR notation is supported? or maybe we don't really care since it is not an issue and maybe we should not trust badbehavior db anyway!

@robocoder commented on April 28th 2011 Contributor

before adding any of the ip ranges used by badbehavior, we'll verify the netblock belongs to Google/Bing/etc

@robocoder commented on May 23rd 2011 Contributor

(In [4784]) fixes #1948 - confirmed these are Microsoft assigned netblocks; should we incubate the BotTracker in #2391 to takeover the smartbot filtering?

This Issue was closed on May 23rd 2011
Powered by GitHub Issue Mirror