-
Notifications
You must be signed in to change notification settings - Fork 385
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
Yara analyzer: 'can't open include file' #354
Comments
Need to take a look on it. You can replace the relative paths in the |
Hi, thanks for your feedback. Now it works, and people can use the following command line: However, the rule 'MALW_AZORULT.yar' raised an error on my side: I used the following command, as I need to automate this action: Probably dirty, but it works. Last point: where do you grab your relevant (and compatible) Yara rules? Kind regards, |
I found the yara-rules repository to be a mess, but maybe it's just me. Using the repository by florian roth often: |
I believe these repository has some fields/variables unsupported by someYara engines: |
I tested the one of @Neo23x0 and it fails:
So, I renamed all "filename" to "file_name" and I reached the same error:
Regards, |
You are absolutely right.
I guess this section is new, perhaps following the issue I mentioned above.
I also enjoy your reactivity :-)
Feedback expected tomorrow
Regards,
Julien
|
Confirmed. It works like a charm...
Thanks guys, |
Request Type
Bug / Support
Work Environment
(replace with N/A if not applicable)
Description
All jobs running Yara analyzer raised an error; while the mentioned file exists.
Due to the error message, I guess it could be a location issue or something like this; but I still can't find the root cause.
Steps to Reproduce
(keep this section only if the issue relates to a bug)
Complementary information
From the Cortex's container, the first file exists.
The second one is not found form the default path, but it is present if you are in the Yara rules folder (here: /opt/Cortex-Analyzers/analyzers/Yara/rules/).
Perhaps this issue is due to the path from where the Yara analyzer is launch.
Thank you for your help,
Kind regards,
Julien M.
The text was updated successfully, but these errors were encountered: