3 commits

Author	SHA1	Message	Date
Christian Kreibich	b24c5c0e46	Order rule traversal in RuleMatcher::Match() operations by Rule index ... This ordering fixes a test failure we're seeing on Alpine for the signatures/tcp-end-of-match btest, since discrepancies in rule match traversal could lead to discrepancies in corresponding event ordering. It looks safe to rely on across platforms since the index is driven by signature load order, which shouldn't deviate. If this somehow doesn't hold in the future, we'll only wind up with a test failure, not incorrect match behavior. (Correction to 2e03fbb8b0, which I pushed accidentally.)	2024-11-18 09:45:09 -08:00
Christian Kreibich	2e03fbb8b0	Define ordering on Rule instances and use on sets in RuleMatcher ... Establishing reliable ordering fixes a test failure we're seeing on Alpine for the signatures/tcp-end-of-match btest, since discrepancies in rule match traversal could lead to discrepancies in corresponding event ordering.	2024-11-14 20:03:07 -08:00
Arne Welzel	04872d4e78	signatures: Add data_end_offset to signature_match() and custom events ... This change tracks the current offset (number of bytes fed into matchers) on the top-level RuleEndpointState such that we can compute the relative ending for matched texts individually. Additionally, it adds the data_end_offset as a new optional parameter to signature_match().	2024-10-30 13:29:58 +01:00