It's a bug that pops up now and then. I believe it's been fixed in the current source. Ignore them or look at the latest fix for inspiration. On Apr 8, 2012 2:00 PM, "Steven Stern" <[email protected]> wrote:
> This just arrived as an alert: > > OSSEC HIDS Notification. > 2012 Apr 08 10:40:50 > > Received From: breadboard->ossec-keepalive > Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system." > Portion of the log(s): > > --MARK--: > > OVb32WA]wUjCqjo.b.X0iIeAuuD^c[)RQ_omKOioQ5Q6w4mxk9=6Z]OB4*k6#.r!z)-9CMFAm-bIcn60Ef^LPx#nj=)DCfh2;L)8;tdeXS[h5iqRo?,3w8&)h3q;q@UXr > +zji&1nCV9P4'aA;K.21vQ8Go0X[2ola]8WuD!W;]ge_UEu?^E0S_&'R'/Ld0edd#0xXEC.z-c1K_DJm7RmeCTVvROyZaC3u,I*%!%V0y4T1b,v8,Huy]^b[@$c@Xn > ?bVy^Ah(I)Q],RGr8Ch,iQuX;?E[t,hsLlR9'gVBHU@Efldv > ]Y6RW[i.H[=0EN)&g(T?GiA$2TZqml'h9Zg%To@ > ]jkVNf-xl8yki+'E?M.pZiXoAqvWs=B1aL4,RV72@avC > +o6_ilSp8XEQ$hg?/HiNA$JzCYKVY5=]BfyJ5yhH+L=2aLk/A6'0NCIx]()b?sLA#9rLby(ErrOrkY4K$XSuI[S*#)(@f@T > *O@ > !.ReB99&I)-gx3m&GU!;)?tns#'#YHR&)Q+2tYM2M*qr,CbCEu8r7JF'qy5wn4gap]3IUXSO-95)Tp3;=_jYx,RNu5r-Dy-atb=vhJr.0=yoUKUL#3Rd0Q?Cp4sT,Xb4g;Hn&ZZK > > > > --END OF NOTIFICATION > > > According to > > http://groups.google.com/group/ossec-list/browse_thread/thread/744de4966f3824c5?pli=1 > , > this was a bug that's been fixed. Is it anything to worry about? I'm > using OSSEC 2.6 on CentOS 5 > -- > -- Steve >
