XF 2.3 My site is dealing with 70,000 guests which I'm assuming are mostly bots
- Thread starter Pepe2012
- Start date
I'm building a competing product that is general purpose but i gotta give you kudos for throwing your hat into the ring. The problem we are solving is increasingly difficult to solve, and diversity in the security ecosystem is a good thing. So GL!
And GL to you, too! All of the old-guard / ideas are these days being easily beat. I felt it was time to put some of that experience gained over 20 years to some good and proper use!
BTW by general purpose, do you mean like an edge-type product or something closer to the edge?
Yes, i'm personally still butthurt that my run with fail2ban is almost over.
Next generation problems need next generation solutions.
The solution is a delivered as a single php file that's inserted ahead of app load and should work on anything that runs PHP ( ~half the internet ).
It uses memcached as the database to provide very high performance.
Kind of a 'for nerds only' option
For modern web scraping / residential proxy abuse, yes: Fail2ban-style defence is basically obsolete as a primary control. Still important, not something you should just rm -rf because it can't catch a sophisticated bot, but definitely no longer the whole solution. I would say: "Fail2ban is not dead. It is just not a serious answer to modern scraping."
So, basically application level... but pre-heavy-application. Sounds good, general purpose, and ambitious, of course! I wish you luck. If you want an experienced eye to glance over / offer ideas, let me know. Happy to help where I can.
I still get good numbers out of fail2ban compared to the average cloudflare setup. A decade of experience tuning it helps achieve that.
Almost useless when it comes to residential proxy attacks though.
It has plenty of other security uses.
Yeah, you could stick it in front of a pig like magento or wordpress and it would be better than fail2ban because it intercepts the hit instead of looks at the results afterwards. With memcached we are looking at 0.03ms of database read time per hit on an average cpu core, so we can make the decision on whether to yeet the traffic faster than the application can boot up.
It would be cool to collaborate actually. I have no profit motive in mind and know a lot about optimization and low level. You have a head start on frontend detection. Maybe there is tag team potential.
Almost useless when it comes to residential proxy attacks though.
It has plenty of other security uses.
Yeah, you could stick it in front of a pig like magento or wordpress and it would be better than fail2ban because it intercepts the hit instead of looks at the results afterwards. With memcached we are looking at 0.03ms of database read time per hit on an average cpu core, so we can make the decision on whether to yeet the traffic faster than the application can boot up.
It would be cool to collaborate actually. I have no profit motive in mind and know a lot about optimization and low level. You have a head start on frontend detection. Maybe there is tag team potential.
That sounds like the perfect name for a support forum here lol.
