Actions
Bug #6973
closeddetect: log relevant frames app-layer metdata
Affected Versions:
Effort:
Difficulty:
Label:
Description
Proposed patch already exists (cf https://github.com/OISF/suricata/pull/10924), but was suggested that it had its own ticket
Updated by Juliana Fajardini Reichow 8 months ago
- Related to Bug #6846: alerts: wrongly using tx id 0 when there is no tx added
Updated by Philippe Antoine 8 months ago
Current master situation :
app-layer data does not get logged for frames, since commit 2b4e10224eaebb613352e9b82556b60035d032a1
Before that, and in main7, app-layer data gets logged, but we log tx id 0 if no specific tx was specified.
Also, the lack of tests suggest that there are many protocols which do not set the tx id for their frames...
Which may be due to the unfriendliness of the rust API to create anew frame with a known tx id...
Updated by Philippe Antoine 8 months ago
- Status changed from In Progress to In Review
Updated by Philippe Antoine 8 months ago
- Related to Security #6900: http2: timeout logging headers added
Updated by Philippe Antoine 7 months ago
- Status changed from In Review to Resolved
Updated by Philippe Antoine 7 months ago
- Status changed from Resolved to Closed
Actions