We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Incorrect case used when assigning IOC type in MineMeld responder.
To Reproduce
Try to use MineMeld responder, experience fail.
Expected behavior
Try to use MineMeld responder, do not experience fail.
Complementary information
diff --git a/responders/Minemeld/minemeld.py b/responders/Minemeld/minemeld.py index 84285c9..5d569bc 100755 --- a/responders/Minemeld/minemeld.py +++ b/responders/Minemeld/minemeld.py @@ -40,7 +40,7 @@ class Minemeld(Responder): elif self.observable_type == "url": indicator_type = "URL" elif self.observable_type == "domain": - indicator_type = "Domain" + indicator_type = "domain" # Check for comment if self.observable_description == "":
Work environment
Possible solutions
Accept pull request when submitted.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Refer to schema here: https://github.com/PaloAltoNetworks/minemeld-core/blob/master/docs/schema-indicator-0-1.json
In particular type node,
"type": { "description": "type of the indicator", "type": "string", "enum": [ "IPv4", "IPv6", "domain", "URL", "sha512", "sha256", "sha1", "md5", "ssdeep", "mutex", "windows-registry-value", "user-agent.fragment", "file.name", "process.command_line", "email-addr", "autonomous-system" ] },
Sorry, something went wrong.
Merge pull request #893 from colin-stubbs/master
1f0a04a
[Bug] MineMeld responder domain IOC incorrect type #892
Successfully merging a pull request may close this issue.
Describe the bug
Incorrect case used when assigning IOC type in MineMeld responder.
To Reproduce
Try to use MineMeld responder, experience fail.
Expected behavior
Try to use MineMeld responder, do not experience fail.
Complementary information
Work environment
Possible solutions
Accept pull request when submitted.
Additional context
n/a
The text was updated successfully, but these errors were encountered: