-
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 v6 #11704
detect/dataset: delay set operation after signature full match v6 #11704
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. The postmatch retrieves the data and set it in the buffer. Increases postmatch capability to do applayertxmatch, and this get the data from a tx buffer. Ticket: OISF#5576
|
||
DetectEngineAppInspectionEngine *a = s->app_inspect; | ||
while (a != NULL) { | ||
if (a->sm_list == sd->list && a->alproto == f->alproto) { |
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.
Can we quickly know if sd->list is a app engine or a pkt one ?
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #11704 +/- ##
=======================================
Coverage 82.63% 82.64%
=======================================
Files 919 919
Lines 248925 248979 +54
=======================================
+ Hits 205703 205765 +62
+ Misses 43222 43214 -8
Flags with carried forward coverage won't be shown. Click here to find out more. |
Information: ERROR: QA failed on SURI_TLPR1_suri_time.
Pipeline 22328 |
Clean in #11714 |
Link to ticket: https://redmine.openinfosecfoundation.org/issues/
https://redmine.openinfosecfoundation.org/issues/5576
Describe changes:
SV_BRANCH=OISF/suricata-verify#2000
#11662 with new solution, reusing
list
to find buffer again at postmatchSo no longer the limitation described for flowvar in https://redmine.openinfosecfoundation.org/issues/7197