DomainToolsIris config cleanup #714
Merged
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
Extend pull request TheHive-Project#312 Fixes code issues and long report template Improve naming for folder and files
added IntezerCommunity analyzer
…5-develop Revert "added IntezerCommunity analyzer"
…g values that could be confusing.
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.
Small changes to the json config files that clean up extraneous config values that could be confusing. For instance both responder json configs had all settings even though one needed
high_risk_thresholdand the other responder didn'tSome of these files have already been pulled into the 2.6.0 release, but because develop has not merged back those files, I thought it prudent to include the python and requirements files for both responders even though they should not have changed from the already accepted PRs.