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

Backport of 6553 to main-7.0.x #11634

Closed
wants to merge 13 commits into from
Closed

Conversation

jlucovsky
Copy link
Contributor

Link to ticket: https://redmine.openinfosecfoundation.org/issues/6555

Describe changes:

Provide values to any of the below to override the defaults.

  • To use an LibHTP, Suricata-Verify or Suricata-Update pull request,
    link to the pull request in the respective _BRANCH variable.
  • Leave unused overrides blank or remove.

SV_REPO=
SV_BRANCH=OISF/suricata-verify#2012
SU_REPO=
SU_BRANCH=
LIBHTP_REPO=
LIBHTP_BRANCH=

Needed a workaround cast for RBTREE use.

(cherry picked from commit a5a6527)
Modeled after the same option in eve/alert. Defaults to 4k.

(cherry picked from commit 829bab2)
This avoids looping over partly duplicate segments that cause
output data corruption by logging parts of the stream data multiple
times.

For data with GAPs now add a indicator '[4 bytes missing]' similar
to how Wireshark does it.

Bug: OISF#6553.
(cherry picked from commit 43858f7)
Don't init buffer to 0 size but use the desired default of 4k.

(cherry picked from commit 462a6d7)
In preparation of stream logging changes.

(cherry picked from commit a205583)
Log using stream callback API, meaning that data will also
be logged if there are GAPs.

Also implement GAP indicators: '[123 bytes missing]'.

(cherry picked from commit 6e10c66)
For better readability and type checking.

(cherry picked from commit 3ef98f2)
(cherry picked from commit 7d5b537)
@jlucovsky jlucovsky requested review from victorjulien and a team as code owners August 15, 2024 15:02
@suricata-qa
Copy link

ERROR:

ERROR: QA failed on ASAN_TLPR1_suri.

Pipeline 22128

@jlucovsky
Copy link
Contributor Author

Continued in #11637

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.

3 participants