Actions
Bug #2495
closedStream depth and filestore interaction
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Description
In the case where stream reassembly depth is set 0 and where file store stream-depth is non null, Suricata is stopping the streaming as soon as filestore is triggered resulting in truncated capture and fileinfo.
Updated by Eric Leblond over 6 years ago
Fix proposal: https://github.com/OISF/suricata/pull/3351
Updated by Victor Julien over 6 years ago
- Target version changed from 4.1rc1 to TBD
Updated by Victor Julien almost 6 years ago
- Status changed from New to Assigned
I see the PR was merged. Should this be closed?
Updated by Andreas Herz over 5 years ago
- Status changed from Closed to Assigned
waiting for an additional PR
Updated by Andreas Herz over 5 years ago
Updated by Victor Julien over 5 years ago
- Related to Bug #2264: file-store.stream-depth not working as expected when configured to a specfic value added
Updated by Victor Julien over 5 years ago
- Related to Bug #2506: filestore v1: with stream-depth not null, files are never truncated added
Updated by Victor Julien over 5 years ago
- Related to Support #2369: option force-filestore generate truncated file added
Updated by Victor Julien almost 5 years ago
- Assignee changed from Eric Leblond to OISF Dev
Updated by Victor Julien over 4 years ago
It is unclear why the ticket can't be closed. We need an explanation of this and preferably a test case. I'll close the ticket soon if there will be no further updates.
Updated by Victor Julien over 4 years ago
- Status changed from Assigned to Closed
- Assignee deleted (
OISF Dev) - Target version deleted (
70)
Actions