Skip to content
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

Rawbytes keyword v3 #5508

Closed
wants to merge 3 commits into from
Closed

Rawbytes keyword v3 #5508

wants to merge 3 commits into from

Conversation

norg
Copy link
Member

@norg norg commented Oct 22, 2020

Make sure these boxes are signed before submitting your Pull Request -- thank you.

Link to redmine ticket:

https://redmine.openinfosecfoundation.org/issues/3017

Describe changes:

  • add rawbytes keyword documentation
  • include clang format changes
  • split commits

PRScript output (if applicable):

@norg norg requested a review from a team as a code owner October 22, 2020 20:42
This was referenced Apr 21, 2021
@victorjulien
Copy link
Member

Merged in #6071, thanks!

catenacyber added a commit to catenacyber/suricata that referenced this pull request Aug 22, 2022
As an SMB2 async response does not have a tree id, even if
the request has it.

Per spec, MessageId should be enough to identifiy a message request
and response uniquely across all messages that are sent on the same
SMB2 Protocol transport connection.
So, the tree id is redundant anyways.

Ticket: OISF#5508
benignbala pushed a commit to benignbala/suricata that referenced this pull request Nov 12, 2022
As an SMB2 async response does not have a tree id, even if
the request has it.

Per spec, MessageId should be enough to identifiy a message request
and response uniquely across all messages that are sent on the same
SMB2 Protocol transport connection.
So, the tree id is redundant anyways.

Ticket: OISF#5508
victorjulien pushed a commit to victorjulien/suricata that referenced this pull request Nov 26, 2022
As an SMB2 async response does not have a tree id, even if
the request has it.

Per spec, MessageId should be enough to identifiy a message request
and response uniquely across all messages that are sent on the same
SMB2 Protocol transport connection.
So, the tree id is redundant anyways.

Ticket: OISF#5508
(cherry picked from commit e94920b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants