suricata
suricata copied to clipboard
Flow bytes pkts syntax + either support/v1
Link to ticket: https://redmine.openinfosecfoundation.org/issues/5646
SV_BRANCH=https://github.com/OISF/suricata-verify/pull/2017
Feedback requested on:
- The new syntax for
flow.pktsandflow.bytes. This new syntax is in between the proposed syntax https://redmine.openinfosecfoundation.org/issues/5646 (for simplicity and compatibility) and the currently implemented one (so the commonuintoperations can be performed easily). - The keyword is only in
masterso8.0.0-beta1, if these changes seem fit, this may be an ok time to get these in w/o any issues.
Known issues:
- Doc update hasn't been done yet.
- Prefilter fn has not been updated yet so it may not work as intended.
- Tests for the parsing of arguments need to be done.
Codecov Report
Attention: Patch coverage is 82.40000% with 22 lines in your changes missing coverage. Please review.
Project coverage is 82.61%. Comparing base (
304271e) to head (1c57201). Report is 122 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #11653 +/- ##
==========================================
- Coverage 82.61% 82.61% -0.01%
==========================================
Files 919 919
Lines 248997 249018 +21
==========================================
+ Hits 205717 205732 +15
- Misses 43280 43286 +6
| Flag | Coverage Δ | |
|---|---|---|
| fuzzcorpus | 60.83% <12.80%> (-0.05%) |
:arrow_down: |
| livemode | 18.64% <12.80%> (-0.02%) |
:arrow_down: |
| pcap | 44.15% <12.80%> (+<0.01%) |
:arrow_up: |
| suricata-verify | 61.89% <82.40%> (-0.01%) |
:arrow_down: |
| unittests | 58.98% <12.80%> (-0.03%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
Information:
ERROR: QA failed on SURI_TLPR1_suri_time.
| field | baseline | test | % |
|---|---|---|---|
| SURI_TLPR1_stats_chk | |||
| .uptime | 642 | 668 | 104.05% |
Pipeline 22213
Information:
ERROR: QA failed on SURI_TLPW2_autofp_suri_time.
ERROR: QA failed on SURI_TLPR1_suri_time.
| field | baseline | test | % |
|---|---|---|---|
| SURI_TLPR1_stats_chk | |||
| .uptime | 642 | 691 | 107.63% |
Pipeline 22215
I'd like to suggest using a different keyword than either.
We have
- to_server
- to_client
I'd like to suggest
anyinstead ofeither. We useanyin other contexts and it's well understood and part of Suricata. It seems appropriate for this usage.
The new syntax for flow.pkts and flow.bytes.
Maybe just add a new keyword flow.pkts_any as we do not want to break existing rules using flow.pkts_toclient
The new syntax for flow.pkts and flow.bytes.
Maybe just add a new keyword
flow.pkts_anyas we do not want to break existing rules usingflow.pkts_toclient
Ok. JFYI, this keyword is only present in master so far so not really being used anywhere that's why I proposed that if the syntax has to be changed, it should be before the release.
Ok. JFYI, this keyword is only present in master so far so not really being used anywhere that's why I proposed that if the syntax has to be changed, it should be before the release.
It is used by paw pat rules (SSH exfiltration)
Ok. JFYI, this keyword is only present in master so far so not really being used anywhere that's why I proposed that if the syntax has to be changed, it should be before the release.
It is used by paw pat rules (SSH exfiltration)
oh. Didn't know anybody did keywords from master. Thank you! TIL