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

Output notx 6846 backport7 v3 #11126

Closed

Conversation

catenacyber
Copy link
Contributor

Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/6848
https://redmine.openinfosecfoundation.org/issues/6975

Describe changes:

No backport of #11064 other commits as they bring in features (specifying transaction ids for frames), instead of fixing the bug that we were logging tx id 0 when irrelevant

First Commit 910f6af needed a small conflict fix in detect-engine-alert.c AlertQueueSortHelper, because of style

if (a) 
    return x;
else
    return y;

was turned into

if (a) 
    return x;
return y;

#11082 rebased to get green CI

Ticket: 6846

This led to packet rules logging irrelevant app-layer data

(cherry picked from commit 910f6af)
Ticket: 6846
(cherry picked from commit 2b4e102)
When we only have stream matches.

Ticket: 6846

This solves the case where another transaction was created
by parsing data in the other direction, before running the
detection.

Like
1. get data in direction 1
2. acked data: parse it, but do not run detection in dir 1
3. other data in direction 2
4. other data acked : parse it and create new tx,
then run detection for direction 1 with data from first packet

(cherry picked from commit 7274ad5)
Ticket: 6973

Completes commit 2b4e102

(cherry picked from commit 9e01956)
@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 20750

@victorjulien
Copy link
Member

Merged in #11135, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants