Upgrading OSSEC 2.7 to 2.8 and the bro-ids rule issue

‘Tis the season for upgrading.

This hour, the target is OSSEC. Next will be a Cloud server running Ubuntu 12.04 LTS, which will be upgraded to Ubuntu 14.04 LTS

OSSEC is a cross-platform and Free Software “host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response.”

It is one of the best of its kind, and one piece of software you want on your server as soon as it’s online. Most tutorials you read advocate Fail2ban, but OSSEC brings a lot more to the table than Fail2ban. Don’t get me wrong, Fail2ban is nice to have on your server, but OSSEC is nicer.

Before the upgrade, the target server was running OSSEC 2.7.1. It was then upgraded to OSSEC 2.8, which was released on June 4 (2014). Upgrading OSSEC is a very simple operation, but I ran into a problem at the end. More on that later. For now, here’s how the upgrade was done.

Downloaded OSSEC 2.8 from here. Verified its checksums and moved the compressed tarball to the server. Unpacked it (tar zxf ossec-hids-2.8.tar.gz), changed to the OSSEC directory (cd ossec-hids-2.8), and started the installation by typing ./install.sh.

Your language is likely supported by the installation script.
Upgrade OSSEC 2.7

It wil detect that there’s an existing OSSEC installation and ask for an upgrade.
Upgrade OSSEC 2.7 to 2.8

From this screenshot, you can tell that something did not go as intended: OSSEC analysisd. Testing rules failed. Configuration error. Exiting.
Upgrade OSSEC 2.7 Linux

Querying the status of OSSEC showed that it is not running. What can the log file tell me?
Upgrade OSSEC 2.7 failed

Entries in the log file revealed the cause of the problem: The program failed to load the bro-ids rule: Invalid decoder name: ‘bro-ids’. Error loading the rules: ‘bro-ids_rules.xml’.
Upgrade OSSEC 2.7 logs

I found out that the issue with bro-ids rules is a longstanding one and that the recommended fix, if you can call it that, is to uncomment the bro-ids_rules.xml line in OSSEC’s main configuration file. And that did the trick
Upgrade OSSEC 2.7 bro-ids rule

Now, OSSEC is up and running, monitoring the system and sending email alerts when it detects bad traffic.

Related Posts

Usability, user-friendliness and the Linux desktop A point I've been trying to convey about the Linux desktop through my reviews and tutorials is that distribution developers are doing a bad job of giv...
KDE 5 Application Dashboard: A fullscreen app launcher that beats the competition Fullscreen applications launchers are my favorite kind of application menus, of which there are several to choose from on the K Desktop Environment, o...
How to install Steam Client on Fedora 20 This tutorial shows how to install Steam on Fedora 20 (install Steam on Fedora 20). Fedora 20 is the latest edition of the popular, multi-purpose Linu...
3 minutes with GNOME 3.4 built-in desktop recorder GNOME 3.4 was released a couple of days ago. A summary of the new features and screen shots have been posted here and here. Two features that I pro...
Cairo-Dock 3.3 released. Install it on Linux Mint 15 Cinnamon Cairo-Dock 3.3, the latest version of the application that provides a dock interface for Free Software desktop environments, has been released. This a...
Linpus 9.6 Tips If you read our review of Linpus 9.6, and are thinking about installing it or recommending it to friends and family, we have a few tips for you. Th...

We Recommend These Vendors

Launch an SSD VPS in Europe, USA, Asia & Australia on Vultr's KVM-based Cloud platform starting at $5:00/month (15 GB SSD, 768 MB of RAM).

Deploy an SSD Cloud server in 55 seconds on DigitalOcean. Built for developers and starting at $5:00/month (20 GB SSD, 512 MB of RAM).


Leave a Comment

Your email address will not be published. Required fields are marked *

*