feat(modules): add encoded word matcher option#325
Open
TBX3D wants to merge 1 commit into
Open
Conversation
pr summary4 files changed (+126 -12)
|
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #325 +/- ##
=======================================
Coverage ? 54.88%
=======================================
Files ? 81
Lines ? 6902
Branches ? 0
=======================================
Hits ? 3788
Misses ? 2845
Partials ? 269 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
word matchers gain an optional encoding of hex or base64. when set, each configured plaintext word is rendered into that encoding before matching, so a marker that appears encoded in a response (a base64 blob, a hex dump) can be matched by its known plaintext form. an unset encoding keeps the existing literal behaviour byte for byte. an unknown encoding value is rejected at module load.
ce7df9c to
fa716bc
Compare
This file contains hidden or 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
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.
word matchers gain an optional encoding of hex or base64. when set, each
configured plaintext word is rendered into that encoding before matching,
so a marker that appears encoded in a response (a base64 blob, a hex dump)
can be matched by its known plaintext form. an unset encoding keeps the
existing literal behaviour byte for byte. an unknown encoding value is
rejected at module load.