BitNinja 3.11.6 brings valuable refinements across several subsystems to improve stability, communication, and firewall rule management. This update focuses on better integration, more accurate cleanup processes, and enhanced support tools for development and troubleshooting.
BitNinja 3.11.6
IPFilter
Fixed an issue where firewall rules could remain in IPTables after BitNinja was stopped. This change ensures cleaner shutdowns and prevents leftover rules from interfering with future firewall activity.
Enhanced CSF integration by resolving a problem with port opening reliability. This improves compatibility and ensures firewall rules align with CSF configurations more consistently across different server setups.
Malware Detection
Resolved a communication issue between the AI Scanner and the API, improving reliability in signature retrieval and scanning operations.
Fixed a bug that impacted the cleaning process of infected files, leading to smoother and more accurate malware removal.
WafManager
Corrected an anomaly that caused “/whitelested” to appear in access logs. This cleanup improves log clarity and makes tracking legitimate traffic more reliable.
Changelog:
- IPFilter
- Fixed an issue with CSF integration port opening.
- Fixed an issue where rules could stay in IPTables after BitNinja stops.
- MalwareDetection
- Fixed an issue in communication between the API and AI Scanner.
- Fixed an issue with cleaning.
- WafManager
- Fixed an issue that caused “/whitelested” to appear in access logs.
To ensure you’re running the latest version, check your update channel settings in the BitNinja Console using RAU. If you have specific configurations or applications preventing automatic updates, please refer to our documentation for instructions on manual updates and RAU configuration. If you'd like to read more about previous releases, check the Changelog anytime. Alternatively, if you would like to see your feature request show up here, don't forget to cast your vote.
