Project

General

Profile

Actions

Optimization #5121

closed

Bug #5124: alerts: 5.0.8/6.0.4 count noalert sigs towards built-in alert limit (5.0.x backport)

Use configurable or more dynamic @ PACKET_ALERT_MAX@ (5.0.x backport)

Added by Jeff Lucovsky 10 months ago. Updated 6 months ago.

Status:
Closed
Priority:
High
Target version:
Effort:
Difficulty:
Label:

Description

Currently, PACKET_ALERT_MAX is hardcoded to 15

This turned out to be a problem writing S-V test, with many signatures (different variations of a feature) matching on the same packet
That was HTTP keywords on HTTP2 traffic, where I had one packet containing 3 requests

It would be nice to have this value be configurable from suricata.yaml


Related issues 1 (0 open1 closed)

Copied from Optimization #4207: Use configurable or more dynamic @ PACKET_ALERT_MAX@ClosedJuliana Fajardini ReichowActions
Actions

Also available in: Atom PDF