I’m proud to announce the availability of the first public testing release of the upcoming installer. We’re in final stages of testing now, and tho there are still known issues it’s time to get community feedback on it. Many many thanks to anybody willing to help test this iso. Please keep in mind that it’s a testing version, not intended for production. We can’t even ensure that at the end of the testing period there will be a seamless upgrade into the stable distribution ;-)
First a quick note on versioning. The new installer will have two versions, one for each architecture:
Installer 1.2: amd64 (that is, most of the 64bit capable processors out there, including Xeons).
Installer 1.1: i386 (old 32bit).
Our intention, right now, is to maintain the 1.1 as long as needed and focus on the 1.2(64bit). Functionality will be exactly the same (if it doesn’t involve too much work, we’ve got limited resources. Jasper/Tomcat integration for example will be limited to 1.2) on both but our development platform is entirely 64bit based due to performance reasons, so there might be a slight delay.
We’re not excluding anyone tho, we’re going to maintain updates for 32bit while there is a large enough user base on it and 32bit users can test the 64bit version on vmware without problems.
The installer testing version can be found at http://data.alienvault.com/ossim-installer_1.2.beta1.iso. Next I’ll list how to install it (along with update guidelines), known issues right now (and how to report new ones) and a short list of some of the stuff included in this release.
Highlighting the download: http://data.alienvault.com/ossim-installer_1.2.beta1.iso.
Grab the iso, install it. After installation, in order to get a clean testing and updating environment (we’re working on solving this right now) issue an:
apt-get remove ossim-cd-setup
This will erase the monstrous package we used before, leaving the files tho (since they’re uncompressed from within a .tgz). More on this later.
apt-get update; apt-get upgrade
You might get an gpg inoxious error; I’m working on getting the packages gpg signed, thanks Jonathan for the script when it arrives :-))
We did setup a specific forum for this. Please post any discovered bugs in there, and please check the rest of the 1.2 forum in case somebody might have reported the issue before.
Before reporting a bug please issue an “apt-get update; apt-get upgrade”, your bug might have been fixed.
There are several issues that I’m aware of right now, which I’m working on:
- Jasperserver password change might break jasperserver.
- SEM doesn’t work out of the box (haven’t commited the code to the cvs yet).
- /home/ossim/dist/ doesn’t get cleaned up.
- Creating new tabs breaks existing tabs at executive panel.
- Memory issues (adding tomcat to the mix didn’t help the already large memory requirements)
- Passwords doesn’t get changed / adapted for everything.
- the reconfig bug when passwords contain “&, ‘, ; or \”" is still present.
- repository is missing gpg signatures
There are many things we’ll be proud of this new release, just to name a few (all of them will be provided before the final release via updates):
- Completely new forensics console. Based on ACID and BASE we decided to incorporate the code into our own cvs; we just have too many specific needs and need to cover them. Check out the following screenshots:
- Disk based event storage (a.k.a. SEM) (will be updating a screenshot asap)
- Interactive risk maps (seen them before)
- Reporting plugins using JasperServer. This will be a major breakthrough, allowing for easy to share reporting plugins, scheduled reports, auto-emailing of reports and much more.
- Shellcode interpretation plugin for forensics.
- OSSEC 2.0
- Many new plugins.
- Updated directives, cross correlation and inventory correlation tables.
- Complete debian package based update/upgrade mechanism, including offline updates. No more custom ossim-updates.
- Many more…
We want this release to be as good as possible, and your feedback is crucial for that. Please download it, throw it into a VM, make your evil tests and report back on the forum thread mentioned above.