scudette's refactor of volatility/win32 stuff to plugins

[GoogleCodeExporter]

This is brought over from Issue 191: 

This might be ok in the short term. In the long term we should remove
all functions in volatility/win32/ into plugins.  The problem right
now is that plugins are not very flexible and are a real PITA to use
because we cant share code between them. Alternatively we can do:

from volatility.plugin.windows import find_module

This forces us to have a certain directory structure which might
change - but thats probably acceptable.

Ultimately we should have a mechanism to be able to invoke a plugin
for doing even a small task - for example have a plugin called
"find_module", and use it from anything else.

IMHO having specialized functions in win32/ is the wrong way to go
because we do not have the ability to tailor these per profile. We
should simply have command plugins, with the ability to provide
different implementations for different operating systems and versions
(think pslist for example).

Michael.

Original issue reported on code.google.com by michael.hale@gmail.com on 25 Jan 2012 at 4:49

[GoogleCodeExporter]

Gonna close this...it will obviously happen in the transition to 3.0 so we 
don't need a specific issue devoted to it. 

Original comment by michael.hale@gmail.com on 1 Feb 2013 at 4:40

• Changed state: Invalid