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

detect: respect directionality for filestore #10251

Closed

Conversation

catenacyber
Copy link
Contributor

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

Describe changes:

  • detect: respect directionality for filestore

So that filestore:to_server,flow only stores the files to server and not the ones to client...

OISF/suricata-verify#1560

SV_BRANCH=pr/1560

#10248 with improved commit message

Ticket: 6617

So that rules with keyword like `filestore:to_server,flow`
only store the files to server and not the ones to client...

Directionality only worked with the default scope, ie the
current file, and not the scope tx or scope flow.
For non-default scope, tx or flow, both directions were stored
whatever the directionality specified.

For these non-default scopes, this commit keeps a default
of both directions, but use only one direction if specified.

Need to split flag FLOWFILE_STORE per direction, so that Suricata
can retain this (optional) directional info from the filestore
keyword.

Fixes: 79499e4 ("app-layer: move files into transactions")
Copy link

codecov bot commented Jan 25, 2024

Codecov Report

Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (c3b3c11) 82.28% compared to head (307882f) 82.25%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #10251      +/-   ##
==========================================
- Coverage   82.28%   82.25%   -0.04%     
==========================================
  Files         977      977              
  Lines      271950   271962      +12     
==========================================
- Hits       223784   223693      -91     
- Misses      48166    48269     +103     
Flag Coverage Δ
fuzzcorpus 63.39% <36.36%> (-0.01%) ⬇️
suricata-verify 61.40% <59.09%> (-0.13%) ⬇️
unittests 62.82% <36.36%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 17768

@victorjulien victorjulien added this to the 8.0 milestone Feb 14, 2024
@victorjulien
Copy link
Member

Merged in #10426, thanks!

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