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

Next/60x/20230115/v4 #8454

Merged
merged 7 commits into from
Jan 26, 2023
Merged

Conversation

catenacyber and others added 7 commits January 25, 2023 19:59
Instead of relying on the usual ordering...

Ticket: OISF#5258
(cherry picked from commit 1db8685)

Manual conflict fixes to use nom instead of nom7
The unit test for content |aa bz| transforms in place the string
str to replace the 2 characters aa by one character 0xaa
Then, when z is not recognized as a valid hexadeicmal character,
the whole modified string is printed out, inclusing the non-ascii
0xaa

Ticket: OISF#5558
(cherry picked from commit b281199)
This commit reduces the changes associated with adding the v14 api to
6.0.x

During the preparation of this commit, issues in the original backport
were corrected
- Failure to release a lock under error conditions
- Typo in an CPP ifdef
- Incorrect target for goto statement in an error handling case.

Issue: 5744
cf https://redmine.openinfosecfoundation.org/issues/4125

This allows fuzz_applayerparser_parse to fuzz one specific
app-layer protocol based on the binary name, as is done
with the environment variable FUZZ_APPLAYER
That is if we rename/copy to fuzz_applayerparser_parse_smb,
it will fuzz only SMB protocol
This way, we can easily produce different fuzz targets for
each protocol in oss-fuzz

(cherry picked from commit e9b76a0)
Inspired by commit ddf14e5

But keeping old nom version
Set the engine to ignore the stream.midstream-policy if stream.midstream
is enabled.

If we had both stream.midstream AND stream.midstream_policy enabled,
this could lead to midstream flows being dropped (or bypassed, or...)
instead of being accepted by the engine, as it was probably meant when
the user enabled midstream flows.

Bug OISF#5765

(cherry picked from commit 8e9905e)
@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 11954

@victorjulien victorjulien merged commit d47e8ff into OISF:master-6.0.x Jan 26, 2023
@victorjulien victorjulien deleted the next/60x/20230115/v4 branch January 31, 2023 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
5 participants