4:22 p.m.
Topic says it...here's what I'm looking at:
Volatile Systems Volatility Framework 2.2
Traceback (most recent call last):
File "/usr/local/bin/vol.py", line 186, in <module>
main()
File "/usr/local/bin/vol.py", line 168, in main
command = cmds[module](config)
File "/opt/volatility-2.2/volatility/plugins/malware/malfind.py",
line 347, in __init__
help = 'Match wide (unicode) strings')
File "/opt/volatility-2.2/volatility/conf.py", line 364, in
add_option
self.optparser.add_option("-{0}".format(short_option),
"--{0}".format(option), **args)
File "/usr/lib/python2.7/optparse.py", line 1020, in add_option
self._check_conflict(option)
File "/usr/lib/python2.7/optparse.py", line 995, in _check_conflict
option)
optparse.OptionConflictError: option -W/--wide: conflicting option
string(s): -W
Any hints on how to get yarascan to run? Thank you.
James
4:40 p.m.
Hi James,
It looks like you might have a semi-broken installation. In your output I
see "/usr/local/bin/vol.py" and also "/opt/volatility-2.2". When you
installed, did you run setup.py or did you just extract the archive you
downloaded from https://code.google.com/p/volatility/downloads/list and
copy vol.py to /usr/local/bin? Is this the only version of volatility you
installed or have you used older versions in the past that might not have
been removed properly?
I'm positive the error doesn't occur in "normal" installations. You
might
try running "make clean" inside the /opt/volatility-2.2 directory to remove
any stale/old compiled .pyc files and then re-running yarascan.
Let us know how it goes,
MHL
On Wed, Apr 3, 2013 at 4:22 PM, James Lay <jlay(a)slave-tothe-box.net> wrote:
Topic says it...here's what I'm looking at:
Volatile Systems Volatility Framework 2.2
Traceback (most recent call last):
File "/usr/local/bin/vol.py", line 186, in <module>
main()
File "/usr/local/bin/vol.py", line 168, in main
command = cmds[module](config)
File "/opt/volatility-2.2/**volatility/plugins/malware/**malfind.py",
line 347, in __init__
help = 'Match wide (unicode) strings')
File "/opt/volatility-2.2/**volatility/conf.py", line 364, in add_option
self.optparser.add_option("-{**0}".format(short_option),
"--{0}".format(option), **args)
File "/usr/lib/python2.7/optparse.**py", line 1020, in add_option
self._check_conflict(option)
File "/usr/lib/python2.7/optparse.**py", line 995, in _check_conflict
option)
optparse.OptionConflictError: option -W/--wide: conflicting option
string(s): -W
Any hints on how to get yarascan to run? Thank you.
James
______________________________**_________________
Vol-users mailing list
Vol-users(a)volatilityfoundation.org
http://lists.volatilesystems.**com/mailman/listinfo/vol-users<http://lis…
4:51 p.m.
On 2013-04-03 14:40, Michael Hale Ligh wrote:
Hi James,
It looks like you might have a semi-broken installation. In your
output I see "/usr/local/bin/vol.py" and also "/opt/volatility-2.2".
When you installed, did you run setup.py or did you just extract the
archive you downloaded
from https://code.google.com/p/volatility/downloads/list [3] and copy
vol.py to /usr/local/bin? Is this the only version of volatility you
installed or have you used older versions in the past that might not
have been removed properly?
Im positive the error doesnt occur in "normal" installations. You
might try running "make clean" inside the /opt/volatility-2.2
directory to remove any stale/old compiled .pyc files and then
re-running yarascan.
Let us know how it goes,
MHL
Thanks Michael for the quick response. I suspect I have a hosed
install. I have an old version, but I've never done the setup part.
I've done setup and make clean, and here's my next response:
Traceback (most recent call last):
File "./vol.py", line 5, in <module>
pkg_resources.run_script('volatility==2.2', 'vol.py')
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 499,
in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1229,
in run_script
raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'vol.py'
Looks like I'm having a bad go of it today...thank you.
James
4:57 p.m.
On 2013-04-03 14:51, James Lay wrote:
On 2013-04-03 14:40, Michael Hale Ligh wrote:
After completely nuking and re-extracting the tarball I have success :)
Thanks again all.
James
Hi James,
It looks like you might have a semi-broken installation. In your
output I see "/usr/local/bin/vol.py" and also "/opt/volatility-2.2".
When you installed, did you run setup.py or did you just extract the
archive you downloaded
from https://code.google.com/p/volatility/downloads/list [3] and
copy
vol.py to /usr/local/bin? Is this the only version of volatility you
installed or have you used older versions in the past that might not
have been removed properly?
Im positive the error doesnt occur in "normal" installations. You
might try running "make clean" inside the /opt/volatility-2.2
directory to remove any stale/old compiled .pyc files and then
re-running yarascan.
Let us know how it goes,
MHL
Thanks Michael for the quick response. I suspect I have a hosed
install. I have an old version, but I've never done the setup part.
I've done setup and make clean, and here's my next response:
Traceback (most recent call last):
File "./vol.py", line 5, in <module>
pkg_resources.run_script('volatility==2.2', 'vol.py')
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 499,
in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
1229, in run_script
raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'vol.py'
Looks like I'm having a bad go of it today...thank you.
James
_______________________________________________
Vol-users mailing list
Vol-users(a)volatilityfoundation.org
http://lists.volatilityfoundation.org/mailman/listinfo/vol-users
5:03 p.m.
Ah, it probably can't find vol.py because someone moved it to
/usr/local/bin. Is this a pre-built VM you're working with? Its hard to
tell you how to "uninstall" because I don't know who installed or where
they manually moved things to.
MHL
On Wed, Apr 3, 2013 at 4:51 PM, James Lay <jlay(a)slave-tothe-box.net> wrote:
On 2013-04-03 14:40, Michael Hale Ligh wrote:
Hi James,
It looks like you might have a semi-broken installation. In your
output I see "/usr/local/bin/vol.py" and also "/opt/volatility-2.2".
When you installed, did you run setup.py or did you just extract the
archive you downloaded
from
https://code.google.com/**p/volatility/downloads/list<https://code.googl…
and copy
vol.py to /usr/local/bin? Is this the only version of volatility you
installed or have you used older versions in the past that might not
have been removed properly?
Im positive the error doesnt occur in "normal" installations. You
might try running "make clean" inside the /opt/volatility-2.2
directory to remove any stale/old compiled .pyc files and then
re-running yarascan.
Let us know how it goes,
MHL
Thanks Michael for the quick response. I suspect I have a hosed install.
I have an old version, but I've never done the setup part. I've done
setup and make clean, and here's my next response:
Traceback (most recent call last):
File "./vol.py", line 5, in <module>
pkg_resources.run_script('**volatility==2.2', 'vol.py')
File "/usr/lib/python2.7/dist-**packages/pkg_resources.py", line 499,
in run_script
self.require(requires)[0].run_**script(script_name, ns)
File "/usr/lib/python2.7/dist-**packages/pkg_resources.py", line 1229,
in run_script
raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'vol.py'
Looks like I'm having a bad go of it today...thank you.
James
5:10 p.m.
On 2013-04-03 15:03, Michael Hale Ligh wrote:
Ah, it probably cant find vol.py because someone moved
it to
/usr/local/bin. Is this a pre-built VM youre working with? Its hard
to
tell you how to "uninstall" because I dont know who installed or
where
they manually moved things to.
MHL
Hi Michael,
Truth be told I symlinked the vol.py to /usr/local/bin/vol.py ;) Looks
like I'll just get used to running it from /opt/volatility-2.2 instead
:) Thank you.
James
4243
days inactive
4243
days old
vol-users@lists.volatilityfoundation.org
5 comments
2 participants
participants (2)
-
James Lay -
Michael Hale Ligh