Hello, i encountered your same problem. Seems the path it's hardcoded in a
strange way when doing binary installation.
One of the way that worked for me, instead of change source code, is to:
1) build and install ossec, in an operative system target (in example
ubuntu), and choose the /opt/ossec
It's surely a reference to ZeroMQ, while syslog have another type of format.
But that's was confusing me :)
Thx for the answer as always.
2014-11-06 17:48 GMT+01:00 dan (ddp) :
> On Thu, Nov 6, 2014 at 11:36 AM, Mario d'Aniello
> wrote:
> > I
I've read here
(http://ossec-docs.readthedocs.org/en/latest/formats/json.html) in the
documentation, that we have a JSON format for alerts.
But it refer to what?
We can have standard alert (in /var/ossec/logs/alert/alert.log) in JSON
format, or it refer to the system via syslog?
I have this d
Hi everyone, i tried to seek in whole mailing list for this info, but i
found nothing. So i started a new topic.
I need to know, if ossec-server, ossec-agent and ossec-local, during the
runtime, write some temporary files.
If yes, it ossec places in standard /tmp directory of every linux distro?
5 GMT+02:00 dan (ddp) :
> On Fri, Oct 24, 2014 at 9:32 AM, Mario d'Aniello
> wrote:
> > What you mean with "manager" and how can i check if manager respond?
> >
>
> The manager is the OSSEC server. I try to say manager most of the time
> because some
What you mean with "manager" and how can i check if manager respond?
2014-10-24 14:52 GMT+02:00 dan (ddp) :
> On Fri, Oct 24, 2014 at 8:43 AM, Mario d'Aniello
> wrote:
> > Yes... here's my ossec.log in attachment.
> >
>
> So, no. Nothing interesting i
Yes... here's my ossec.log in attachment.
2014-10-24 14:17 GMT+02:00 dan (ddp) :
> On Fri, Oct 24, 2014 at 8:16 AM, Mario d'Aniello
> wrote:
> > Ok i verified with a working ossec server, that list_agent wont show the
> > agent if hadn't a first access.
> &g
scritto:
On Fri, Oct 24, 2014 at 6:54 AM, Mario d'Aniello
wrote:
> Hi all.
> I recently installed Ossec-hids-2.8.1 downloaded from main site, on
openSUSE
> 13.1.
> First i did a Server installation and seems that all gone fine. Then i
added
> an agent with ./manage-agent, extrac
Hi all.
I recently installed Ossec-hids-2.8.1 downloaded from main site, on
openSUSE 13.1.
First i did a Server installation and seems that all gone fine. Then i
added an agent with ./manage-agent, extracted the key and imported to an
agent.
But when i try to connect the agent, the agent wont c
Ok i'll wait for future fix of this issue. Meanwhile i'll try to figure out
where the problem is. Thx for the answer, i'd really appreciate your
kindness and availability
Il 21/ott/2014 18:28 "dan (ddp)" ha scritto:
> On Tue, Oct 21, 2014 at 11:59 AM, Mario d'An
Ok, i give it a try another time and there's no way to change path
directory in binary installation. I guess should be exist a bug somewhere
in makefile or make.
So the only viable choice to let it work is to:
- Download ossec.* from the site and untar.
- Perform a new "total" installation (respon
stuck to search
/var/ossec folder.
I'm currently build ossec in Ubuntu 12.04 LTS, 64bit and next, exported the
bin to OpenSuse 13.1 64 bit
2014-10-21 15:45 GMT+02:00 dan (ddp) :
> On Tue, Oct 21, 2014 at 9:24 AM, Mario d'Aniello
> wrote:
> > Hello, i'm currently
Hello, i'm currently using ossec-hids-2.8.1 and still have this problem in
the exact path (/opt/ossec/).
I try to change LOCATION file but still don't work any ideas?
Il giorno mercoledì 9 novembre 2011 22:10:51 UTC+1, alsdks ha scritto:
>
> Hello,
>
> I was testing binary installations ,
13 matches
Mail list logo
