check the whitelist regex in the base plugin class (for #93)#99
Merged
Conversation
domanchi
approved these changes
Dec 7, 2018
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
3 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.
This adds a check for the
WHITELIST_REGEX(i.e.# pragma: whitelist secret) in the base plugin class, inanalyze(), see #93.This doesn't affect
HighEntropyStringsPluginbecause that class overridesanalyze(), but that class already does this regex check (inanalyze_string()). Seems reasonable to me that if a class is overridinganalyze()it should handle this whitelist check itself too.Test coverage
This actually increases test coverage slightly... I did have to add a whitelisted line to the test .ini file, otherwise the whitelist check in HighEntropyStringsPlugin loses its test coverage.