Bug#1010771: suricata: recieve erros after adding rule list

severity 1010771 normal thanks Hi Tim, I just noticed you also included your suricata.yaml configuration file in your bug report. I think I found the cause of your problem. Let's take a look at a problematic rule: 9/5/2022 -- 14:20:21 - -- [ERRCODE: SC_ERR_INVALID_SIGNATURE(39)] - error pa

Processed: Re: Bug#1010771: suricata: recieve erros after adding rule list

Processing commands for cont...@bugs.debian.org: > severity 1010771 normal Bug #1010771 [suricata] suricata: recieve erros after adding rule list Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1010771: https://bugs.debian.org

Bug#1010771: suricata: recieve erros after adding rule list

Hi, [...] 9/5/2022 -- 14:20:21 - -- [ERRCODE: SC_ERR_INVALID_SIGNATURE(39)] - Complete IP space negated. Rule address range is NIL. Probably have a !any or an address range that supplies a NULL address range This seems to indicate that in the rule below, the expression ![$SMTP_SERVERS,$DNS_S

Bug#1010771: suricata: recieve erros after adding rule list

Package: suricata Version: 1:6.0.5-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, What led up to the situation? Followed the instructions from suricata.readthedocs.io to add rules for the IDS What exactly did you do (or not do) t