Seen a couple of these myself, particularly on /etc/rc*.d directories after an upgrade.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bruce Martins Sent: Tuesday, March 03, 2009 2:20 PM To: [email protected] Subject: [ossec-list] Re: Version 2.0 Released I have seen the following after an upgrade from 1.6.1 to 2.0 where it complains that the hash value for certain directories have changed Please see below Integrity checksum changed for: '/etc/rc5.d' Old md5sum was: 'd41d8cd98f00b204e9800998ecf8427e' New md5sum is : 'xxx' Old sha1sum was: 'da39a3ee5e6b4b0d3255bfef95601890afd80709' New sha1sum is : 'xxx' -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ddp Sent: Tuesday, March 03, 2009 1:07 PM To: [email protected] Subject: [ossec-list] Re: Version 2.0 Released I successfully restarted ossec 2.0 with the mcafee rules commented out on both OpenBSD and Centos. dan On Tue, Mar 3, 2009 at 12:20 PM, Peter M. Abraham <[email protected]> wrote: > > Greetings: > > There is a bug in ossec 2 server where if you comment out the > "<include>mcafee_av_rules.xml</include>" in /var/ossec/ossec.conf > ossec will then not restart properly. > > Please fix this bug. > > Also, I've reported in the past that all upgrades to date absolutely > destroy customizations of what rules are included in ossec.conf > > This makes upgrading harder because you then have to go back in to > comment out inapplicable rules. > > Thank you. >
