tking2 / volatility

Automatically exported from code.google.com/p/volatility
GNU General Public License v2.0
0 stars 1 forks source link

Easier way to determine a plugins available output formats #499

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Current output renderings/formats are included within individual plugins.  
Without looking at the code of the plugin(s) it's not obvious as to which 
formats you're able to output the results into.

What is the expected output? What do you see instead?
- More centralized method for output formats.  This would make it easier for 
plugin creation and ensuring consistency on output formats so a plugin can just 
return its data to an output function located outside its own code instead of 
having to rewrite an output function on a per plugin basis.

- When doing a (-h) on a plugin, have it list which output formats the plugin 
can produce.  

What version of the product are you using? On what operating system?
2.3.1/2.4_beta

Please provide any additional information below.
JSON output would be helpful

Original issue reported on code.google.com by hiddenil...@gmail.com on 9 May 2014 at 1:46

GoogleCodeExporter commented 9 years ago
Hi Glenn,

I agree and there have added an issue to the 2.4 branch to address listing 
output options.  

A more centralized output method is currently on the roadmap, but may not 
actually materialize until 3.0.

Original comment by jamie.l...@gmail.com on 12 May 2014 at 2:01

GoogleCodeExporter commented 9 years ago
This has now been done in 2.4.

Original comment by jamie.l...@gmail.com on 10 Jun 2014 at 9:58