From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Automatically enable JA3 fingerprinting.
Date: Tue, 27 Oct 2020 12:54:08 +0000 [thread overview]
Message-ID: <DE7FA39C-9491-4B72-B4DF-E00C3916D9C0@ipfire.org> (raw)
In-Reply-To: <4f5cdabfc604c9e0ea3bf103586e3545f4f66110.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
Hello Stefan,
okay. I merged this into next which will eventually become Core Update 153.
Everyone, please test and send feedback :)
Best,
-Michael
> On 27 Oct 2020, at 11:06, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
>
> Hello Michael,
>
> this change is not tested very well (I only tested on my productive
> system and got no errors), so there are definitely more testing should
> be done until we can ship them.
>
> I'd suggest to bundle it with suricata 6 so we have more time for
> testing and collecting feedback.
>
> Best regards,
>
> -Stefan
>> Good morning Stefan,
>>
>> Thanks for submitting this patch.
>>
>> Is this tested and peer-reviewed and should this be merged into c152
>> with suricata 5.0.4, or is this to be merged with suricata 6?
>>
>> Best,
>> -Michael
>>
>>> On 27 Oct 2020, at 09:49, Stefan Schantl <stefan.schantl(a)ipfire.org
>>>> wrote:
>>>
>>> Enable JA3 fingerprinting if any rules are enabled which are using
>>> this
>>> kind of feature.
>>>
>>> Fixes #12507.
>>>
>>> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
>>> ---
>>> config/suricata/suricata.yaml | 4 +---
>>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>>
>>> diff --git a/config/suricata/suricata.yaml
>>> b/config/suricata/suricata.yaml
>>> index 743a4716c..4e9e39967 100644
>>> --- a/config/suricata/suricata.yaml
>>> +++ b/config/suricata/suricata.yaml
>>> @@ -387,9 +387,7 @@ app-layer:
>>>
>>> # Generate JA3 fingerprint from client hello. If not
>>> specified it
>>> # will be disabled by default, but enabled if rules require
>>> it.
>>> - #ja3-fingerprints: auto
>>> - # Generate JA3 fingerprint from client hello
>>> - ja3-fingerprints: no
>>> + ja3-fingerprints: auto
>>>
>>> # Completely stop processing TLS/SSL session after the
>>> handshake
>>> # completed. If bypass is enabled this will also trigger flow
>>> --
>>> 2.20.1
>>>
>
prev parent reply other threads:[~2020-10-27 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 9:49 Stefan Schantl
2020-10-27 9:54 ` Michael Tremer
2020-10-27 11:06 ` Stefan Schantl
2020-10-27 12:54 ` Michael Tremer [this message]
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=DE7FA39C-9491-4B72-B4DF-E00C3916D9C0@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