mirror of
https://github.com/OISF/suricata.git
synced 2026-02-18 18:18:04 -05:00
f295cc059d
Ticket: 7556 To do so, we need to add 2 buffers (one for each direction) to the QuicState structure, so that on parsing the second packet with hello/crypto fragment, we still have the data of the first hello/crypto fragment. Use a hardcoded limit so that these buffers cannot grow indefinitely and set an event when reaching the limit
9 lines
721 B
Text
9 lines
721 B
Text
# QUIC app-layer event rules.
|
|
#
|
|
# These SIDs fall in the 2231000+ range. See:
|
|
# http://doc.emergingthreats.net/bin/view/Main/SidAllocation and
|
|
# https://redmine.openinfosecfoundation.org/projects/suricata/wiki/AppLayer
|
|
|
|
alert quic any any -> any any (msg:"SURICATA QUIC failed decrypt"; app-layer-event:quic.failed_decrypt; classtype:protocol-command-decode; sid:2231000; rev:1;)
|
|
alert quic any any -> any any (msg:"SURICATA QUIC error on data"; app-layer-event:quic.error_on_data; classtype:protocol-command-decode; sid:2231001; rev:1;)
|
|
alert quic any any -> any any (msg:"SURICATA QUIC crypto fragments too long"; app-layer-event:quic.crypto_frag_too_long; classtype:protocol-command-decode; sid:2231002; rev:1;)
|