Release note on BitNinja 1.5 | DoS Detection update

Boglarka Angalet

We’ve been through some busy weeks again, full of excitements and DoS-improvements.

We’d like to say thank you again for all the supportive bugfix and development tickets, sent by you all. We can bring the best out of BitNinja together, no doubts about it. ;)

Let’s see the new features and bugfixes which gave birth to BitNinja 1.5.

 

Features

  • DoS Detection has been refactored. Now it supports exceptions for local and remote ports.
    • For remote port 25 the new threshold is 200 connections.
    • For local 22 port the new threshold is 40 connections.

Auto-release will be rolled out on Wednesday.

 

We released 18 bugfixes since BitNinja 1.4. Here you can read about the most important ones:

  • New log analyzer rules (Apache parnet dir denial, WordPress XmlRpc, Exim logs for connection timeout checks)
  • AntiFlood small logging bug fixes
  • Cli now supports greylist checking
  • Small fix in Linux distribution detection
  • Changed iptables requirement from 1.4.7 to 1.4.4
  • Filtering incident flood
  • Redirection fix in the Captcha module
  • Improvements for SenseLog module stability and memory leak
  • Now BitNinja client utilizes http cookie based session in communication with the central server
  • Captcha challange page extended with honeypot juice and e-mail honey
  • Log detection now supports cPanel and Plesk apache access and error logs

 

Upcoming updates

  • IpFilter module refactoring to support OpenVZ based virtual servers and Net based ipsets
  • ProxyFilter module to enable correct filtering of proxy traffic (like CloudFlare, Incapsula, etc … yes, they need BitNinja filtering, too, as many malicious requests bypass them)
  • Placing the basics of the BitNinja WAF

Share your ideas with us about this article

Previous posts

BitNinja success on server security
We just launched BitNinja a little more than a month ago. It has been already demonstrated for 1 year in our own hosting environment, and success is coming from users worldwide, too. Read more and celebrate with us. BitNinja’s public beta ended on 23rd March, 2015. There were exactly 220 active BitNinja servers back then. Registrators arrived from all over the world, from Australia, through Brazil, even from Canada. Development took place in close cooperation with our beta users, and we’d really like to continue this way.   Numbers speak for themselves By the la...
Release note on BitNinja 1.4
As always, you are encouraged to tell us what you think about BitNinja. Everything is welcome from bugs to development suggestions. That’s how version 1.4 was born, too. We’d like to extend a special thank you to all of the Ninjas who contributed to this version by contacting us tirelessly. Check out what’s new for this version of BitNinja below. Feature There’s no further issues about newly installed servers with our greylist. It happened occasionally that if someone installed BitNinja on his server with a formerly greylisted IP address, BitNinja banned it out. From 1.4, if the...