-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
next/632/70x/20241108/v1 #12106
next/632/70x/20241108/v1 #12106
Conversation
Ticket: 7366 Ticket: 6186 (cherry picked from commit dd71ef0)
Ticket: 7326 Having a lower progress than one where we actually can get occurences of the multibuffer made prefilter bail out too early, not having found a buffer in the multi-buffer that matiched the prefilter. For example, we registered http_request_header with progress 0 instad of progress HTP_REQUEST_HEADERS==2, and if the first packet had only the request line, we would consider that signatures with http_request_header as prefilter/fast_pattern could not match for this transaction, even if they in fact could have a later packet with matching headers. Hence, we got false negatives, if http.request_header or http.response_header was used as fast pattern, and if the request or response came in multiple packets, and the first of these packets did not have enough data (like only http request line), and the next packets did have the matching data. (cherry picked from commit cca59cd)
The returned event_id was being set to -1, but the function wasn't returning -1 to indicate error. Ticket: OISF#7361
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main-7.0.x #12106 +/- ##
==============================================
- Coverage 83.42% 83.27% -0.15%
==============================================
Files 922 922
Lines 260795 260794 -1
==============================================
- Hits 217558 217177 -381
- Misses 43237 43617 +380
Flags with carried forward coverage won't be shown. Click here to find out more. |
Information: ERROR: QA failed on SURI_TLPW2_autofp_suri_time. ERROR: QA failed on SURI_TLPR1_suri_time.
Pipeline 23295 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks consistent with the approved PRs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- All CI checks passed
- Has all commits from original PRs
- Line changes match
- All original PRs approved
Information: QA ran without warnings. Pipeline 23297 |
Staging:
SV_BRANCH=OISF/suricata-verify#2126