Skip to content
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

bitlocker already defined #26

Closed
JamesHabben opened this issue Feb 6, 2018 · 1 comment
Closed

bitlocker already defined #26

JamesHabben opened this issue Feb 6, 2018 · 1 comment
Labels

Comments

@JamesHabben
Copy link

Trying to run current volatility with community plugins on OSX and getting this error. Is it a conflict with one of the plugins?

Traceback (most recent call last): File "/usr/local/bin/vol.py", line 4, in <module> __import__('pkg_resources').run_script('volatility==2.6', 'vol.py') File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 750, in run_script self.require(requires)[0].run_script(script_name, ns) File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 1527, in run_script exec(code, namespace, namespace) File "/usr/local/lib/python2.7/site-packages/volatility-2.6-py2.7.egg/EGG-INFO/scripts/vol.py", line 192, in <module> main() File "/usr/local/lib/python2.7/site-packages/volatility-2.6-py2.7.egg/EGG-INFO/scripts/vol.py", line 162, in main cmds = registry.get_plugin_classes(commands.Command, lower = True) File "/usr/local/lib/python2.7/site-packages/volatility-2.6-py2.7.egg/volatility/registry.py", line 152, in get_plugin_classes raise Exception("Object {0} has already been defined by {1}".format(name, plugin)) Exception: Object bitlocker has already been defined by <class 'volatility.plugins.ThomasWhite.bitlocker.Bitlocker'>

@iMHLv2
Copy link
Contributor

iMHLv2 commented Feb 6, 2018

Hi James, yes it looks like two plugins have the same name. There's a note in the "usage" section of the README.md that discusses how to avoid conflicting command line arguments, and the same thing applies to plugins with conflicting names.

@gleeda gleeda added the invalid label May 23, 2018
@gleeda gleeda closed this as completed May 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants