autoruns.py not working about volatility-autoruns HOT 5 CLOSED

There seems to be conflicting options (in this case -W, inherited from the HiveList plugins) with some other plugin in your plugin folder. What happens if you run the plugin from its own directory?

from volatility-autoruns.

Aha, that seemed to work. I'll have to keep that in mind with third party
plugins, that I can't just dump them all in the same folder.

It does throw this error, though
WARNING : volatility.obj : NoneObject as string: Value data is
unreadable
but it still seems to work

On Tue, Mar 17, 2015 at 9:06 AM, Thomas Chopitea [email protected]
wrote:

There seems to be conflicting options (in this case -W, inherited from
the HiveList plugins) with some other plugin in your plugin folder. What
happens if you run the plugin from its own directory?

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

from volatility-autoruns.

I think that's a common problem when trying to read keys that don't exist.
I'll have to try/catch my way around it.

On Tue, Mar 17, 2015 at 6:43 PM, Arvandor [email protected] wrote:

Aha, that seemed to work. I'll have to keep that in mind with third party
plugins, that I can't just dump them all in the same folder.

It does throw this error, though
WARNING : volatility.obj : NoneObject as string: Value data is
unreadable
but it still seems to work

On Tue, Mar 17, 2015 at 9:06 AM, Thomas Chopitea <[email protected]

wrote:

There seems to be conflicting options (in this case -W, inherited from
the HiveList plugins) with some other plugin in your plugin folder. What
happens if you run the plugin from its own directory?

—
Reply to this email directly or view it on GitHub
<
#4 (comment)

.

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

Thomas Chopitea

from volatility-autoruns.

Yes indeed!

Thank you for the prompt help! I've been meaning to write some kind of
script to take care of this very thing... it somehow hadn't even occurred
to me to make it a plugin, duh. Always happy not to reinvent the wheel
though, glad I found this!

On Tue, Mar 17, 2015 at 11:49 AM, Thomas Chopitea [email protected]
wrote:

I think that's a common problem when trying to read keys that don't exist.
I'll have to try/catch my way around it.

On Tue, Mar 17, 2015 at 6:43 PM, Arvandor [email protected]
wrote:

Aha, that seemed to work. I'll have to keep that in mind with third party
plugins, that I can't just dump them all in the same folder.

It does throw this error, though
WARNING : volatility.obj : NoneObject as string: Value data is
unreadable
but it still seems to work

On Tue, Mar 17, 2015 at 9:06 AM, Thomas Chopitea <
[email protected]

wrote:

There seems to be conflicting options (in this case -W, inherited from
the HiveList plugins) with some other plugin in your plugin folder.
What
happens if you run the plugin from its own directory?

—
Reply to this email directly or view it on GitHub
<

#4 (comment)

.

—
Reply to this email directly or view it on GitHub
<
#4 (comment)

.

Thomas Chopitea

—
Reply to this email directly or view it on GitHub
#4 (comment)
.

from volatility-autoruns.

Glad it helped you!

from volatility-autoruns.