From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Enable EVE logging
Date: Thu, 06 Jun 2019 08:54:23 +0100 [thread overview]
Message-ID: <33E7BD39-5682-490B-B9F3-070AFBC35F97@ipfire.org> (raw)
In-Reply-To: <7be56270b4f0261fe5d8d7bd13bc33139b69311e.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2827 bytes --]
Okay. Merged.
> On 5 Jun 2019, at 18:10, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> Hello Michael & Erik,
>
> when building suricata here, the build process automatically detected
> and successfully linked the final suricata binary against libjannson.
>
> I'm fine with your patch, because it hard switches libjannson support
> to on and the entire build process would be fail, if the library could
> not be linked or the include files are missing....
>
> Best regards,
>
> -Stefan
>
> Acked-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>
>> Hi Michael,
>>
>> On Mi, 2019-06-05 at 09:53 +0100, Michael Tremer wrote:
>>> Hi Erik,
>>>
>>> I believe that Stefan has already enabled this in this commit:
>>>
>>>
>>> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=616395f37c6d096607283cc17e5554cc03e9bcc6
>>
>> this is indeed a needed step to build Jansson before Suricata,
>> made the same while an experimental try with EVEbox
>> --> https://forum.ipfire.org/viewtopic.php?f=50&t=22693#p124673
>> but there was also the need to include the jansson libs in the LFS
>> too.
>>
>>> Are you saying that the library wasn’t linked before?
>> Have looked in version 'v2.23-core131-215-gc899be2fd' where Stefans
>> patch is already included but if i change to chroot and execute a
>>
>> suricata --build-info | grep jansson
>>
>> i get
>>
>> libjansson support: no
>>
>> so yes, i think the library isn´t linked even Jansson has been build
>> before Suricata.
>>
>>
>>> I am not sure what this patch is meant to achieve - assuming that
>>> Stefan’s change isn’t broken.
>> Possibly Suricata do not searches automatically for libjansson ?
>>
>>> -Michael
>>
>> Best,
>>
>> Erik
>>
>>>> On 4 Jun 2019, at 14:00, Erik Kapfer <ummeegge(a)ipfire.org> wrote:
>>>>
>>>> The EVE output facility outputs alerts, metadata, file info and
>>>> protocol specific records through JSON.
>>>> for further informations please see -->
>>>> https://suricata.readthedocs.io/en/suricata-4.1.2/output/eve/index.html
>>>> .
>>>>
>>>> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
>>>> ---
>>>> lfs/suricata | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/lfs/suricata b/lfs/suricata
>>>> index 310920606..6f779d875 100644
>>>> --- a/lfs/suricata
>>>> +++ b/lfs/suricata
>>>> @@ -80,6 +80,8 @@ $(TARGET) : $(patsubst
>>>> %,$(DIR_DL)/%,$(objects))
>>>> --enable-nfqueue \
>>>> --disable-static \
>>>> --disable-python \
>>>> + --with-libjansson-libraries=/usr/lib \
>>>> + --with-libjansson-includes=/usr/include \
>>>> --disable-suricata-update
>>>> cd $(DIR_APP) && make $(MAKETUNING)
>>>> cd $(DIR_APP) && make install
>>>> --
>>>> 2.12.2
>>>>
next prev parent reply other threads:[~2019-06-06 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 13:00 Erik Kapfer
2019-06-05 8:53 ` Michael Tremer
2019-06-05 15:27 ` ummeegge
2019-06-05 17:10 ` Stefan Schantl
2019-06-06 7:54 ` Michael Tremer [this message]
2019-06-06 17:40 ` ummeegge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33E7BD39-5682-490B-B9F3-070AFBC35F97@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox