Conversation
Currently in parse_request function LdapEvent::InvalidData is not set when a request is not parsed correctly. Ticket OISF#8258
|
NOTE: This PR may contain new authors. |
|
What is the conclusion on the SV test? |
|
Information: QA ran without warnings. Pipeline = 29925 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #14913 +/- ##
==========================================
- Coverage 81.93% 81.91% -0.03%
==========================================
Files 986 986
Lines 271105 271102 -3
Branches 31005 31005
==========================================
- Hits 222139 222081 -58
- Misses 46822 46875 +53
- Partials 2144 2146 +2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
I think what @catenacyber meant is that when only a response is sent (which is the case in the test), |
|
I think the code is good now. The rustfmt part could be its own commit And it would be nice to have a SV test that exercices this code path (maybe crafting/corrupting an existing SV ldap pcap) to see the anomaly event |
|
Merged in #14931, thanks! |
Currently in parse_request function LdapEvent::InvalidData is not set when a request is not parsed correctly.
Previous PR: #14723
Link to ticket: https://redmine.openinfosecfoundation.org/issues/8258