public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IDS with support for multiple ruleset providers
Date: Sat, 10 Apr 2021 14:01:36 +0100	[thread overview]
Message-ID: <8C32ADE0-E57C-4A61-B543-58FBF793EA34@ipfire.org> (raw)
In-Reply-To: <f73c259b47b3e9b21a6e9b1fb9ebff890f3c5779.camel@ipfire.org>

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

Hello,

I just tried to install this on my c156 test system and I have found the following issues:

The converter script was not executable:

[root(a)fw01 ~]# convert-ids-multiple-providers
-bash: /usr/sbin/convert-ids-multiple-providers: Permission denied

But that could be easily fixed:

[root(a)fw01 ~]# chmod a+x /usr/sbin/convert-ids-multiple-providers

But then it fails with another error; probably a typo:

[root(a)fw01 ~]# convert-ids-multiple-providers
Can't locate /var/ipfire/ids-functions.pl1 at /usr/sbin/convert-ids-multiple-providers line 25.

Fixing that gives me this:

[root(a)fw01 ~]# convert-ids-multiple-providers
Could not write to /var/ipfire/suricata/oinkmaster-emerging-modified-sids.conf. No such file or directory

Creating that file makes the converter exit without any errors:

[root(a)fw01 ~]# touch /var/ipfire/suricata/oinkmaster-emerging-modified-sids.conf
[root(a)fw01 ~]# convert-ids-multiple-providers
[root(a)fw01 ~]#

But it didn’t convert anything and the file is empty.

However, the CGI loads and shows the new functionality.

Clicking the checkbox to disable a ruleset shows this:

Smartmatch is experimental at /srv/web/ipfire/cgi-bin/ids.cgi line 288.
Smartmatch is experimental at /srv/web/ipfire/cgi-bin/ids.cgi line 288.
Smartmatch is experimental at /srv/web/ipfire/cgi-bin/ids.cgi line 288.
Could not write to /var/ipfire/suricata/suricata-used-providers.yaml. Permission denied

That file exists but is owned by root:

-rw-r--r-- 1 root   root       0 Apr 10 13:42 suricata-used-providers.yaml

Changing permissions to nobody:nobody brings me one step further:

Could not write to /var/ipfire/suricata/oinkmaster-provider-includes.conf. Permission denied

After fixing the ownership, I can enable and disable the rule provider.

However, when I click “customise ruleset”, no rules are selected which suggests that the converter did not work correctly.

I could also add a new provider and found it confusing that no categories are enabled automatically. It could happen, that you add a couple of providers, but then there are still no rules enabled. That would be potentially dangerous. Thoughts on this?

Apart from that, this seems to work solidly even with the new perl release.

-Michael

> On 9 Apr 2021, at 20:27, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Hello Development Team and list followers,
> 
> there are a lot of different vendors out there which offers different
> IDS rules for suricata. Some of them offers a complete set of rules and
> other ones some very specialized rules for different tasks.
> 
> Unfortunately it only was possible to select only one ruleset provider
> at the same time, so it usually wasn't an option to use one of them and
> keep a lot of traffic uninspected by the IDS.
> 
> Today I'm very happy to announce a testing version of a reworked
> Intrusion Detection System which supports the usage of multiple
> different providers and rulesets at the same time.
> 
> In total up to 15 different ruleset providers now can be used and mixed
> together to fit your personal requirements. They easily can be managed
> and configured via the WUI. Of course each one individually can be
> disabled or re-enabled at each time.
> 
> The section for customizing the entire ruleset has been moved to a
> subpage, which allows to enable a certain amount of ruleset files or
> enabling / disabling single rules inside them.
> 
> This helps to speed up the CGI if you want to mange your whitelist,
> manage your ruleset providers or change basic settings of your IDS. 
> 
> If you liked this short introduction, please help us testing to get
> this cool stuff as soon as possible into the core distribution and to
> find bugs or other improvements.
> 
> The test versions and some screenshots can be found here:
> 
> https://people.ipfire.org/~stevee/ids-multiple-providers/
> 
> To join testing, please download the latest tarball and place it on
> your IPFire test machine.
> 
> Execute the archive by using "tar -xvf ids-multiple-providers-
> XXX.tar.gz - C /" on your local console or via SSH remote session.
> 
> The next steps would be to regenerate the language cache by executing
> "update-langs-cache" and to launch "convert-ids-multiple-providers".
> 
> The converter will convert all your existing settings into the new
> format and also will take care about your used rules and their
> settings.
> 
> As usual, please report back any kind of feedback on this list and
> submit any found bugs to our bugtracker (https://bugs.ipfire.org).
> 
> Thanks in advance,
> 
> -Stefan
> 
> 


  reply	other threads:[~2021-04-10 13:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 19:27 Stefan Schantl
2021-04-10 13:01 ` Michael Tremer [this message]
2021-04-10 17:15   ` Stefan Schantl
2021-04-10 13:06 ` Adolf Belka
2021-04-10 13:15   ` Adolf Belka
2021-04-10 17:18   ` Stefan Schantl
2021-04-10 18:25 ` Stefan Schantl
2021-04-10 20:56   ` Adolf Belka
2021-04-10 21:17     ` Adolf Belka
2021-04-11  6:59       ` Stefan Schantl
2021-04-11  7:07     ` Stefan Schantl
2021-04-11  8:46       ` Stefan Schantl
2021-04-11  9:49         ` Adolf Belka
2021-04-11 10:18           ` Adolf Belka
2021-04-11 12:27             ` Michael Tremer
2021-04-13 18:57             ` Stefan Schantl
2021-04-14  9:12               ` Michael Tremer
2021-04-14 19:01                 ` Stefan Schantl
2021-04-14 19:16               ` Stefan Schantl
2021-04-14 19:25                 ` Stefan Schantl
2021-04-15 11:08                 ` Michael Tremer

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=8C32ADE0-E57C-4A61-B543-58FBF793EA34@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