userguide: explain rule types and categorization - v7 #12114
Closed
+227
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add documentation about the rule types introduced by 2696fda. Add doc tags around code definitions that are referenced in the docs. Task #https://redmine.openinfosecfoundation.org/issues/7031
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #12114 +/- ##
==========================================
+ Coverage 83.23% 83.28% +0.04%
==========================================
Files 906 906
Lines 257647 257647
==========================================
+ Hits 214458 214570 +112
+ Misses 43189 43077 -112
Flags with carried forward coverage won't be shown. Click here to find out more. |
victorjulien
approved these changes
Nov 12, 2024
|
Information: QA ran without warnings. Pipeline 23307 |
Closed
jufajardini
commented
Nov 13, 2024
Comment on lines
+421
to
+431
| * - Packet-Stream | ||
| - Flow, if stateful (**) | ||
| - Flow, if stateful, per-packet if not | ||
| - Against the reassembled stream. If stream unavailable, match per-packet | ||
| (packet payload and stream payload) | ||
| - 'content' with 'startswith' or 'depth' | ||
| * - Stream | ||
| - Flow, if stateful (**) | ||
| - Per stream chunk, if stateful, per-packet if not | ||
| - Against the reassembled stream. If stream unavailable, match per-packet | ||
| - 'tcp-stream' in protocol field; simple 'content'; 'byte_extract' |
There was a problem hiding this comment.
Re-review especially for these two.
This was referenced Nov 27, 2024
|
Finally followed by: #12184 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add documentation about the rule types introduced by 2696fda.
Add doc tags around code definitions that are referenced in the docs.
Task #https://redmine.openinfosecfoundation.org/issues/7031
Link to ticket: https://redmine.openinfosecfoundation.org/issues/
Built docs: https://suri-rtd-test.readthedocs.io/en/doc-sigtypes-et-properties-v7/rules/intro.html#rule-types-and-categorization
Previous PR: #12113
Describe changes:
framekeyword and rule examples to application layer transaction examples