public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: DRAFT: Suricata services
Date: Fri, 29 Jul 2022 18:09:58 +0200	[thread overview]
Message-ID: <109ed99c12e527f0b8993109f3d4208e65bc8171.camel@ipfire.org> (raw)
In-Reply-To: <5fb81b37a74f63fc498e98cba31afcfaaff7288b.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]

Hello list followers,

today I backed a second test version which fixed an issue to proper use
the new feature and adjusted the rules to silence some more alerts.

The new test tarball can grabbed at the same location as the previous
one - Install instructions are the same.

As usual please share your feedback and opinions here - a big thanks in
advance.

Best regards,

-Stefan  
> Hello list followers,
> 
> after some reports on our community portal about a flooded IDS log
> in case the tor addon is installed and activated, I tried to solve
> this
> issue.
> (https://community.ipfire.org/t/tor-and-ips-conflict-suricata-rulset-where-does-it-come-from/
> )
> 
> The desired solution would be to load additional suricata rules to
> silence the noisy rules when tor is used. This worked pretty well so
> I
> extended the code to be more general and such rules for any kind of
> service can be written and loaded.
> 
> I collected all the changes on my personal git repository:
> 
> https://git.ipfire.org/?p=people/stevee/ipfire-2.x.git;a=shortlog;h=refs/heads/suricata-services
> 
> For an easy testing I created a test tarball, which can
> be found here:
> 
> https://people.ipfire.org/~stevee/ids-services/
> 
> As usual a README file gives deeper information and guides through
> the installation process.
> 
> Please share your opinions about this approach and in case you are
> testing please provide your feedback here.
> 
> A big thanks in advance,
> 
> -Stefan
> 



      reply	other threads:[~2022-07-29 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 13:26 Stefan Schantl
2022-07-29 16:09 ` Stefan Schantl [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=109ed99c12e527f0b8993109f3d4208e65bc8171.camel@ipfire.org \
    --to=stefan.schantl@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