Maintenance Update

Changelog
- Add ASL Web warning pop up in gui config window for high load changes;
- Add ASL Web line break handling for event text in event and event detail window
- Add to configuration, x3 mysql admin credentials check
- Add ASL Web updater event for waf_rule_reporting, the config used to manage FP reporting behavior
- Add ASL Web version and exclusion check to false positive and false negative reporting
- Update to configuration, minor update for horde detection
- Update to hids_check to manage the expiration time for the asl-purge event based on the repeat offender timeout.
- Update to version checking routine for ASL updates. This evaluates major, minor, and subminor
- Bugfix #XXX, ASL Web, Fixed forced waf checks; Fixed overwriting window state in session
- Bugfix #XXX, Corrects newline handling in hids event detail view
- Bugfix #XXX, fix for reporting status correctly with the newer named firewall table format
- Bugfix #XXX, changes to SHUN_TIME will now restart execd

To upgrade:
yum upgrade asl asl-web

Is there any chance you could implement a function not overwriting /var/asl/data/templates/template-freshclam.conf every time an update is released to asl? It's starting to get annoying having to implement all local configurations every time asl is updated.

Or three templates in my case.
And it isn't just that - I also have to edit the actual conf file as well as the template, and restart the services, very quickly, or bad things happen.

This is, of course, a tricky situation. There may be important changes in he templates in some instances, so there has to be a mechanism that forces whatever we have at the moment to get overwritten.

Now personally I'd like to go all old-school and technical to resolve this: when there's an update like this where the template files are due to get overwritten and I've made changes to mine, I'd like to be shown a diff and asked if I want to keep the original or accept the new one. This way I'd know if there was an important change an could decide how to handle it myself.

Having said that, where there's no change in the templates then I don't see why they need to get overwritten during an asl minor version update.

Faris.

the template system isnt really implemented for you guys yet. Its really there for us right now. That being said, we're adding in all the freshclam & clamav settings in to the clamav module.

Well, you kinda forced us to use the templates. The conf files get overwritten every night so the only way to get your system running is to do the changes in the templates, isn't it?

For the moment yeah, we were going to make them more flexible but we ran out of time.

Totally understand!!!