-
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
detect/dataset: delay set operation after signature full match #11600
detect/dataset: delay set operation after signature full match #11600
Conversation
The set operation of dataset keyword was done even if signature did not fully match. This patch changes the behavior of the dataset keyword to do a match and a post match for the set operation. In the match, the buffer data that needs to end up in the set is captured and in post match the dataset is updated (if ever the signature is fully matching). Ticket: OISF#5576
Actually, this is a bigger problem indeed because unlike flowvar, |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #11600 +/- ##
===========================================
- Coverage 82.52% 70.35% -12.17%
===========================================
Files 923 923
Lines 248808 248649 -159
===========================================
- Hits 205317 174944 -30373
- Misses 43491 73705 +30214
Flags with carried forward coverage won't be shown. Click here to find out more. |
ERROR: ERROR: QA failed on build_asan. Pipeline 21818 |
33163a6
to
d5286fd
Compare
Could we somehow delay the dataset check as the last operation before postmatch ?.. |
d5286fd
to
03e0617
Compare
Information: ERROR: QA failed on SURI_TLPW2_single_alerts_cmp. ERROR: QA failed on SURI_TLPW2_autofp_alerts_cmp. ERROR: QA failed on SURI_TLPR1_alerts_cmp. ERROR: QA failed on IPS_AFP_drop_chk.
Pipeline 21849 |
Continued in #11623 |
Link to ticket: https://redmine.openinfosecfoundation.org/issues/
https://redmine.openinfosecfoundation.org/issues/5576
Describe changes:
SV_BRANCH=OISF/suricata-verify#2000
Side note: the limitation described for flowvar in https://redmine.openinfosecfoundation.org/issues/7197 likely also applies here to dataset