Our user greylisting feature is one year old
Nikoletta Szabo

Our user greylisting feature is one year old

Nikoletta Szabo

It has been exactly a year now since we released our user greylisting feature. We have received feedback from you that has helped us to develop all of our modules and features. Thank you for all of your past cooperation and for your current support, and for using BitNinja daily. The user greylisting feature has been proved quite efficient, as most of our clients are using it every day. Our support staff received lots of requests from clients to manage the greylisted IPs on their own servers before we began this development. Fortunately, we could successfully cope with this issue and our magical developers created this customization.

You can remove or add IPs to your server’s greylist, meaning that BitNinja will defend your infrastructure from those malicious IPs. What is more is that we have a customizable white and blacklist too, aiming for the highest amount of personalization for your software. However, it is important to note that any IP you add to these lists will not be listed globally by all BitNinja enabled servers, but will only affect the settings of your private server. Although the addition of these IPs is private, we take these greylist changes as a basis for our global greylisting. Firstly, we collect enough information from each IP from the privately greylisted ones, and after sufficient attack data we add them to our global greylist. So your effort is appreciated!

We have a documentation site, which endows you with all the necessary knowledge about our listings and allows you to see how the greylisting process works from the other end, from the side of the intruder IP, and some more information about customization and BitNinja itself.

Stay tuned for the freshest developments and news!

Share your ideas with us about this article

Previous posts

The most common attacks against websites
I’m sure you’ve heard about the recent headlines about the hacked cameras with the system default passwords or how IoT (Internet of Things) devices can serve as botnets in huge DDoS attacks against the most frequently visited websites. One of these kinds of attacks was a DDoS attack against Dyn, the internet infrastructure company responsible for routing internet traffic. It caused outages in multiple large traffic websites like Twitter, Netflix, Reddit, Spotify, and Tumblr. In the case of a worse kind of black Friday, these websites were inaccessible for a couple of hours.   &n...
Release note on 1.12.5 version
Today (2016, 07 Nov) we released the newest version of BitNinja. Let’s see what has changed: SenseLog supervisors can be disabled in /etc/bitninja/SenseLog/config.ini CaptchaHttp now checks remote address at connection time From now on the BitNinja captcha is able to determine the performer of the connection in the exact moment when the connection has been established. DosDetection LocalIp filter undefined interface address bug fixed Turkish translation added to CaptchaHttp You can configure your own captcha with the use of our documentation site. Joomla Brute for...