From: Jay Lubomirski <jaylubo@gmail.com>
To: development@lists.ipfire.org
Subject: Re: IDS / Snort/VRT GPLv2 Community-Rules : Error parsing signature... - but I can't deactivate specific rule(s)
Date: Sun, 10 May 2026 21:04:03 -0400 [thread overview]
Message-ID: <CAPvyjOq=8LQDn6ZLNf6dart_Cdzk0-8zu_RdQF50DWL4V6wz2A@mail.gmail.com> (raw)
In-Reply-To: <a7834fd5-1537-498c-ac69-01c353d1c8c1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2527 bytes --]
Hi Matthias,
I've been using this patch to fix the can't uncheck a rule problem:
# /var/ipfire/ids-functions.pl
#
--- ids-functions.pl.old
+++ ids-functions.pl.new
@@ -614,8 +614,8 @@
# Check if the Provider is set so IPS mode.
if ($providers_mode{$provider} eq "IPS") {
# Replacements for sourcefire rules.
- $line =~
s/^#\s*(?:alert|drop)(.+policy balanced-ips alert)/alert${1}/;
- $line =~
s/^#\s*(?:alert|drop)(.+policy balanced-ips drop)/drop${1}/;
+ $line =~ s/^(?:alert|drop)(.+policy
balanced-ips alert)/alert${1}/;
+ $line =~ s/^(?:alert|drop)(.+policy
balanced-ips drop)/drop${1}/;
# Replacements for generic rules.
$line =~
s/^(#?)\s*(?:alert|drop)/${1}drop/;
Can you see if that helps in your situation?
Jay Lubomirski
On Sat, May 9, 2026 at 12:12 PM Matthias Fischer <
matthias.fischer@ipfire.org> wrote:
> Hi list,
>
> IDS is running with several rulesets, no seen problems, but one set
> always throws this error:
>
> ***SNIP***
> [1433] <Error> -- error parsing signature "drop tcp $EXTERNAL_NET
> $HTTP_PORTS -> $HOME_NET any (msg:"MALWARE-OTHER Win.Trojan.Zeus Spam
> 2013 dated zip/exe HTTP Response - potential malware download";
> flow:to_client,established; content:"-2013.zip|0D 0A|";
> fast_pattern:only; content:"-2013.zip|0D 0A|"; http_header; content:"-";
> within:1; distance:-14; http_header; file_data; content:"-2013.exe";
> content:"-"; within:1; distance:-14; metadata:impact_flag red, policy
> balanced-ips drop, policy max-detect-ips drop, policy security-ips drop,
> ruleset community, service http;
> reference:url,
> www.virustotal.com/en/file/2eff3ee6ac7f5bf85e4ebcbe51974d0708cef666581ef1385c628233614b22c0/analysis/
> ;
> classtype:trojan-activity; sid:26470; rev:2;)" from file
> /var/lib/suricata/community-community.rules at line 2581
> ***SNAP***
>
> Everything is working fine - except for this error message.
>
> So I tried to deactivate this rule - but I can't. Every time I uncheck
> this rule, it gets checked again. No chance. There are others —
> apparently not every rule — who also refuse to get unchecked.
>
> Can anyone confirm?
>
> Best
> Matthias
>
>
>
[-- Attachment #2: Type: text/html, Size: 3499 bytes --]
next prev parent reply other threads:[~2026-05-11 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 16:12 Matthias Fischer
2026-05-11 1:04 ` Jay Lubomirski [this message]
2026-05-11 7:32 ` Matthias Fischer
2026-05-11 8:47 ` Adolf Belka
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='CAPvyjOq=8LQDn6ZLNf6dart_Cdzk0-8zu_RdQF50DWL4V6wz2A@mail.gmail.com' \
--to=jaylubo@gmail.com \
--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