Project

General

Profile

Actions

Bug #6710

closed

rules: failed rules after a skipped rule are recorded as skipped, not failed

Added by Jason Ish 9 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

For example:

alert tcp any any -> any any (frame:smtp.not_supported; requires: version >= 10; sid:4;)
alert asdf any any -> any any (sid:1000; rev:1;)

will result in the stats showing 2 skipped rules instead of 1 skipped, one failed. This is due to a flag not being reset for each new rule.


Subtasks 1 (0 open1 closed)

Bug #6711: rules: failed rules after a skipped rule are recorded as skipped, not failed (7.0.x backport)ClosedJason IshActions
Actions

Also available in: Atom PDF