-
Notifications
You must be signed in to change notification settings - Fork 930
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
[Bug] Path issue (probably?) with CAPA #532
Comments
This seems to be the issue reported in mandiant/VM-Packages#686 and fixed in mandiant/VM-Packages#710. To be able to help you, please provide all the information required in the bug issue template. Concretely, we need the following environment information:
Also, I am not sure what a |
I'm reporting this on behalf of students taking PMAT, so I don't have their exact builds at the ready to provide the system info. I can get it for you. In the course, lab set up basically boils down to
|
Though after reading through those other closed issues, it's more likely that the student installed FLAREVM when that bug was still live, so maybe having them reinstall CAPA would be the actual issue here and this can probably be marked as a duplicate! |
Reinstalling capa won't fix the problem, as the bug was in |
Unrelated@HuskyHacks I think you may want to update the environment variables in that config file. |
Hey thanks! I'll update that and add the new registry key items too. |
What's the problem?
Hello!
I've had a few students report that for recent FLAREVM installs, CAPA can't locate its default rules set when invoked with a relative path:
The CAPA binary definitely runs but it doesn't find its default rule set, which leads me to believe the PATH var is getting messed up somewhere during install.
Steps to Reproduce
capa [sample]
Output indicates that the binary executes but cannot find its bundled default rule set when invoked with a relative path.
Environment
Additional Information
No response
The text was updated successfully, but these errors were encountered: