-
Notifications
You must be signed in to change notification settings - Fork 65
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
SIFT, volatility and yarascan #218
Comments
It's because multiple plugins are conflicting with each other. You'd have to eliminate each plugin one by one to figure out which are conflicting with each other. Have you installed any custom plugins? It's possible that the community plugin repo has created conflicts. |
Nothing custom. This is a fresh install. I was having the same problem with Rob Lee's 508 version. Same error. This is a fresh ova download with no modifications. After I still had the error I did a sift update and the error remains the same. |
Right. An updating won't fix it unless we release a patch/fix for this. I'll have to confirm it's reproducible and then see where the conflict resides. |
Just to confirm: I have the same issue with a fresh install |
It’s a problem with the community volatility plugins. |
same errors received also while running yarascan plugin. from new SANS SIFT machine |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I am facing the same issue on fresh Sift Workstation v3 (OVA version). |
I just used the yarascan module for the first time (SIFT install was originally done last September). I received this exact same issue. Is there a resolution/workaround? |
I’m unsure which plugins are conflicting. That’s the fix to find and remove the conflicting one. |
I found a workaround:
Make sure to backup the original file. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
…ixed the malfind yarascan parameters error as suggested in teamdfir/sift#218 (comment)
This workaround worked for me., thank you |
I just took my two practice tests and this bug appeared in both. This is still a problem. Luckily I discovered this before my exam attempt, would suck to miss out on the points from 1-2 live VM questions... |
Anyone else having issues using volatility with the yarascan plugin with the latest SIFT? Fully updated and still getting this error:
vol.py -f mem.dat --profile=Win7SP1x64 yarascan -y "test"
Volatility Foundation Volatility Framework 2.6
Traceback (most recent call last):
File "/usr/bin/vol.py", line 192, in
main()
File "/usr/bin/vol.py", line 174, in main
command = cmdsmodule
File "/usr/lib/python2.7/dist-packages/volatility/plugins/malware/malfind.py", line 190, in init
help = 'Make the search case insensitive')
File "/usr/lib/python2.7/dist-packages/volatility/conf.py", line 363, in add_option
self.optparser.add_option("-{0}".format(short_option), "--{0}".format(option), **args)
File "/usr/lib/python2.7/optparse.py", line 1021, in add_option
File "/usr/lib/python2.7/optparse.py", line 996, in _check_conflict
optparse.OptionConflictError: option -C/--case: conflicting option string(s): -C
root@siftworkstation -> /h/s/Downloads
The text was updated successfully, but these errors were encountered: