-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROX-26025: Sanitize UTF-8 strings in process signals #1857
Merged
Merged
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
cb7f1a2
Add SanitizeUTF8()
ovalenti b591af2
Sanitize strings before formatting the Process signal.
ovalenti 7d86e66
Unit tests
ovalenti ca9b97f
Start over fresh
ovalenti c1510c9
Handle explicitely the UTF8-sanitized strings in the Formatter
ovalenti 6226563
Tests for SanitizedUTF8()
ovalenti 8991ae8
Cleanup superfluous variable
ovalenti 2c66eba
Make the test more robust in case of failure
ovalenti 5d4b341
Proper termination of copied strings
ovalenti File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds like a lifetime nightmare. Can't we do something similar to what protobuf does and simply use pointers? Or maybe make
SanitizeUTF8
return astd::optional<std::string>
? That way if the return value is empty it would mean the original string is valid and, if it is not empty, it will hold the sanitized string.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point, I wasn't convinced myself.
The problem is with the immutability of std::string, which makes you copy and copy again. I will figure out a more maintainable way.