From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 3/5] convert-snort: Adjust code to use changed modify_sids_file function.
Date: Wed, 05 Jun 2019 20:56:34 +0200 [thread overview]
Message-ID: <20190605185636.9952-3-stefan.schantl@ipfire.org> (raw)
In-Reply-To: <20190605185636.9952-1-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
---
config/suricata/convert-snort | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)
diff --git a/config/suricata/convert-snort b/config/suricata/convert-snort
index 83931fa5b..5ed36954f 100644
--- a/config/suricata/convert-snort
+++ b/config/suricata/convert-snort
@@ -196,18 +196,8 @@ if (-f $guardian_meta) {
## Step 5: Generate and write the file to modify the ruleset.
#
-# Converters default is to only monitor the traffic, so set the IDS action to
-# "alert".
-my $IDS_action = "alert";
-
-# Check if the traffic only should be monitored.
-if ($idssettings{"MONITOR_TRAFFIC_ONLY"} eq "off") {
- # Swith IDS action to alert only.
- $IDS_action = "drop";
-}
-
# Call subfunction and pass the desired IDS action.
-&IDS::write_modify_sids_file($IDS_action);
+&IDS::write_modify_sids_file();
# Set correct ownership.
&IDS::set_ownership("$IDS::modify_sids_file");
--
2.20.1
next prev parent reply other threads:[~2019-06-05 18:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 18:56 [PATCH 1/5] suricata: correct rule actions in IPS mode Stefan Schantl
2019-06-05 18:56 ` [PATCH 2/5] ids-functions.pl: Rework function write_modify_sids_file() Stefan Schantl
2019-06-05 18:56 ` Stefan Schantl [this message]
2019-06-05 18:56 ` [PATCH 4/5] convert-ids-modifysids-file: Adjust code to use changed write_modify_sids_file function Stefan Schantl
2019-06-05 18:56 ` [PATCH 5/5] Core 133: Add suricata related converters to the update Stefan Schantl
2019-06-05 20:34 ` [PATCH 1/5] suricata: correct rule actions in IPS mode Tim FitzGeorge
2019-06-06 7:53 ` 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=20190605185636.9952-3-stefan.schantl@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