Files
Juliana Fajardini f839581dba pgsql: bound tx.responses (configurable)
Since the PostgreSQL protocol doesn't impose any clear limits to how
many responses a backend could send, add one to the app-proto parser.

Using 21-64 as the accepted values, and 64 as the default:

The Start-up phase may have up to 17-18 ParameterStatus messages, plus
AuthOk, BackendKeyData and ReadyForQuery: 20, with extra room to be on
the safer side: 21

And 64 as upper limit, because as we currently summarize query
responses, we already don't get flooded by DataRow and Copy responses
messages, so we don't expect to see that many responses in a single
transaction for the pgsql, with the current implementation.

Ticket: #7263
2026-09-09 14:23:41 +02:00
..
2026-05-16 20:42:15 +02:00
2023-05-06 14:50:43 +02:00
2026-06-11 14:36:03 +00:00
2025-06-21 21:32:53 +02:00
2026-06-11 14:36:03 +00:00
2026-09-04 21:20:24 +00:00
2026-06-10 20:57:38 +00:00
2026-06-11 14:36:03 +00:00

Suricata Reserved SID Allocations

See https://sidallocation.org/ for more information.

Unless otherwise noted, each component or protocol is allocated 1000 signature IDs.

Components

Component Start End
Decoder 2200000 2200999
Firewall 2201000 2201999
Stream 2210000 2210999
Generic App-Layer 2260000 2260999

App-Layer Protocols

Protocol Start End
SMTP 2220000 2220999
HTTP 2221000 2221999
NTP 2222000 2222999
NFS 2223000 2223999
IPsec 2224000 2224999
SMB 2225000 2225999
Kerberos 2226000 2226999
DHCP 2227000 2227999
SSH 2228000 2228999
MQTT 2229000 2229999
TLS 2230000 2230999
QUIC 2231000 2231999
FTP 2232000 2232999
POP3 2236000 2236999
LDAP 2237000 2237999
SNMP 2238000 2238999
SCTP 2239000 2239999
DNS 2240000 2240999
PGSQL 2241000 2241999
mDNS 2242000 2242999
Bittorent 2243000 2243999
MODBUS 2250000 2250999
DNP3 2270000 2270999
SIP 2280000 2280999
HTTP2 2290000 2290999