FIX: report Unicode tag presence correctly when decoding - #2552
Closed
Sylvester Kaczmarek (sylvesterkaczmarek) wants to merge 2 commits into
Closed
Conversation
Contributor
|
Duplicate of #2540 |
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
2 participants
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.
Description
Fixes the logging-only Unicode-tag detection defect described in #2539.
AsciiSmugglerConverter.decode_messagecurrently infers whether hidden Unicode tags were present by comparing decoded and input string lengths. This can report that no hidden tags were found for a fully hidden payload.This change tracks whether a Unicode Tag code point was actually encountered and uses that signal for logging.
Tests
Adds regression coverage for fully hidden payloads and ordinary plaintext.