Hi Peter,

Can you send us your ossec.conf file (at least the part related to the
rules) and the error message
you are getting? I was not able to reproduce this issue in here.


The issue that Bruce reported and some other people are noticing:

> Integrity checksum changed for: '/etc/rc5.d'
> Old md5sum was: 'd41d8cd98f00b204e9800998ecf8427e'
> New md5sum is : 'xxx'
> Old sha1sum was: 'da39a3ee5e6b4b0d3255bfef95601890afd80709'
> New sha1sum is : 'xxx'

Is something I fixed that caused it. In the previous versions we were
doing the md5/sha1sum of any link
to a directory, which doesn't make any sense (directories have no
content). So on 2.0, we are not doing
it and that's why the "xxx" in the md5/sha1 sum...

Thanks,

--
Daniel B. Cid
dcid ( at ) ossec.net


On Wed, Mar 4, 2009 at 9:48 AM, Peter M. Abraham
<[email protected]> wrote:
>
> HI Dan:
>
> For me, and maybe it is because I have a number of the rules which
> mean nothing commented out, when I comment out the McAfee rules, ossec
> dies.
>
> Thank you.
>

Reply via email to