-
Notifications
You must be signed in to change notification settings - Fork 237
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
Cortex and MISP unclear and error-loop #29
Comments
Hi @crackytsi, The latest version of Cortex as of this writing (v 1.1.1) lets you invoke MISP expansion modules if you'd like, as described in the MISP Integration Guide. That is the reason why there is now a separate stanza for them. We prefer to keep the configuration of Cortex native analyzers separate from the configuration of the MISP expansion modules. I successfully reproduced your problem. It is due to the fact that the MISP modules are enabled by default and Cortex is looking for them. Please disable the MISP modules in
And restart Cortex. This should fix your problem temporarily. Now that we are aware of this issue, we are going to look for a permanent solution very soon. Thank you for your nice comments about our work. We should held ourselves to better QA standards though to prevent such errors from happening in the first place. This will be our priority in the next few weeks. |
Thank you so much. I understand it now :) |
Hi,
|
This |
Hmmm. But I disabled all except dns lookup... |
Well, When misp-modules is enabled in Cortex, the latter will try to load the list of all misp-modules available (undependently from what modules you have configured) When listing the misp modules, the operation fail because of the missing The issue is that this package is not available on PIP (it's a fork a another uwhoisd project...) To get the uwhois installed, make sure your pip is up to date:
and then run
|
Thanks, I got it. At the time time you wrote this, I finally found this commit: Lookyloo/uwhoisd@3f16d42 :) |
Request Type
Bug
Work Environment
Problem Description
Hello,
Thanks a lot for your really, really good work!!!
Sorry maybe its my fault, but I don't have any further idear, so I use this way to adress it:
AND
I'm not sure if the old configuration of MISP (as source) is still correct:
MISP {
url="https://server"
key="mykey"
certpath=["/etc/ssl/private/misp.local.crt", ""]
name="instance-1"
}
The text was updated successfully, but these errors were encountered: