Dataset set postmatch 5576 v4 #2093
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
9e66688 to
c004733
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
c004733 to
61a9767
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
61a9767 to
2fdca6f
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
2fdca6f to
e842b6a
Compare
This was referenced Oct 29, 2024
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
e842b6a to
3936e33
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
3936e33 to
a502637
Compare
This was referenced Dec 2, 2024
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
a502637 to
3f7329a
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
3f7329a to
cceb634
Compare
Closed
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
3 times, most recently
from
8477867 to
a0504cf
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
a0504cf to
3d2f8d8
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
3d2f8d8 to
67362a9
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
67362a9 to
ee179ae
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
ee179ae to
b9bc201
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
b9bc201 to
8d1dc24
Compare
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
8d1dc24 to
26d742a
Compare
Thanks, fixed |
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
26d742a to
dbc1af3
Compare
This was referenced Jun 14, 2025
Ticket: 5576
Ticket: 5576 Signature full match does not happen on first packet inspected, but signature gets stored as partially matching so far, and then postmatch retrieves the buffer to set in the dataset.
catenacyber
force-pushed
the
dataset-set-postmatch-5576-v4
branch
from
dbc1af3 to
160dcde
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/5576
#2000 with more tests for complex cases
Do I get right the expected behavior of datasets-multibuf-postmatch ?
Rule
alert http any any -> any any (msg:"HTTP learning"; http.request_header; content:"toto"; dataset:set,http_match,type string,save http_match.csv; sid:1;)will save in dataset only the headers having the content
totoand (not the user agent curl for instance)