Core: Add (optional) sanitization to the FileHandler class #1023
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
|
Merging this just to keep the history (it was a little bit naughty for the changes to have been included in #999). 5:) |
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.
This is a first cut at ensuring filename writes are safe. This completely excludes unicode filenames, which will not be useful for a large chunk of forensics, which is why it's being made optional to each plugin before we move forward with it. Whitelists are much more effective than blacklists, but I'm not certain how to allow unicode characters without potentially tripping over something a filesystem handles poorly, so for now its an explicit latin-1 whitelist.