Re: [ossec-list] ossec-remoted not running

On Sat, Mar 4, 2017 at 2:36 PM, Eduardo Reichert Figueiredo wrote: > Hi All, > i killed de process and take command "ossec-control start" and the process > of remoted stay up. > But my agents "Windows" display "never connected" but the port 1514 stay up > and with

Re: [ossec-list] ossec-remoted not running

Hi All, i killed de process and take command "ossec-control start" and the process of remoted stay up. But my agents "Windows" display "never connected" but the port 1514 stay up and with tcpdump i see my agents send logs to server. strange... Em quarta-feira, 1 de março de 2017 15:37:55

Re: [ossec-list] Enable only syscheckd for FIM

On Fri, Mar 3, 2017 at 5:29 PM, Sam Gardner wrote: > Thanks for the info - I'd like to explore what I can actually do with OSSEC > and do my due diligence before exploring other options. > > I've spun up the following conf file and am running ossec-analysisd and >

Re: [ossec-list] Corresponding user ossec, ossecm don't exist

On Sat, Mar 4, 2017 at 12:21 PM, wrote: > > I am having the problem that within the installation of the OSSEC client the > corresponding user/groups (that OSSEC use within its executable files and > directories) are not created. > I am running the

[ossec-list] Corresponding user ossec, ossecm don't exist

I am having the problem that within the installation of the OSSEC client the corresponding user/groups (that OSSEC use within its executable files and directories) are not created. I am running the software over a Debian machine with all the privileges. I realized it because, for example,