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 (backport7) #10430

Conversation

catenacyber
Copy link
Contributor

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")
(cherry picked from commit 63caa0b)
Copy link

codecov bot commented Feb 15, 2024

Codecov Report

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

Comparison is base (07e0f0d) 82.44% compared to head (343e7c9) 82.47%.

Additional details and impacted files
@@              Coverage Diff               @@
##           main-7.0.x   #10430      +/-   ##
==============================================
+ Coverage       82.44%   82.47%   +0.02%     
==============================================
  Files             975      975              
  Lines          274925   274937      +12     
==============================================
+ Hits           226672   226745      +73     
+ Misses          48253    48192      -61     
Flag Coverage Δ
fuzzcorpus 63.58% <36.36%> (+0.07%) ⬆️
suricata-verify 61.61% <59.09%> (+<0.01%) ⬆️
unittests 62.88% <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 18512

@victorjulien
Copy link
Member

Merged in #10442, 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