search

michelle-joudrey / volatility

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

[refactor render_* methods] Feature: Create 'global' output structure; star to vote for this feature! #311

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I recently wanted a plugin to output in CSV format, so created the necessary 
code to do so. When submitting the patch to the author, it was pointed out that 
while it's fine and well to have the output option for this particular plugin, 
it would be best to have an overarching structure for handling plugins, so that 
every plugin doesn't have to recreate CSV format.

I agree with the author's points, and would like to cast my vote for seeing 
this put on the roadmap! If you agree, please star this issue so that the 
authors can see that there is a desire for this feature...Just think, you could 
have a flexible system to output your volatility results in anything you can 
come up with like html, json, csv, etc!

Original issue reported on code.google.com by jessebow...@gmail.com on 24 Jul 2012 at 2:00

GoogleCodeExporter commented 8 years ago 
Jesse,
  We are already building support for this. We currently have json output and text output. This can be done generically for all the plugins:

http://code.google.com/p/volatility/source/browse/branches/scudette/volatility/u
i/renderer.py#599

This mechanism is experimental at the moment but hopefully can be integrated 
into trunk soon.

re csv - the csv is pretty easy to generate for tables but what about free 
formatting? How do you output several tables (e.g. dlllist produces a table per 
pid). I think csv in itself is pretty limited but could be useful in some cases.

Original comment by scude...@gmail.com on 24 Jul 2012 at 3:42

GoogleCodeExporter commented 8 years ago

Original comment by mike.auty@gmail.com on 29 Jul 2012 at 9:28

GoogleCodeExporter commented 8 years ago

Original comment by michael.hale@gmail.com on 7 Mar 2014 at 9:20

GoogleCodeExporter commented 8 years ago 
Issue 392 has been merged into this issue.

Original comment by michael.hale@gmail.com on 7 Mar 2014 at 9:22

GoogleCodeExporter commented 8 years ago

Original comment by michael.hale@gmail.com on 7 Mar 2014 at 9:22

GoogleCodeExporter commented 8 years ago 
Would it be possible to have a csv output which could be directly used with 
tools like afterglow, picviz or maltego?
Because for now, you have to do your own cooking to merge informations. Of 
course, you adapt depending on context but something in base would be cool.

Thanks

Original comment by julien....@gmail.com on 5 May 2014 at 12:00

GoogleCodeExporter commented 8 years ago 
being implemented in the "unified-output" branch on github: 
https://github.com/volatilityfoundation/volatility

closing out

Original comment by jamie.l...@gmail.com on 20 Nov 2014 at 8:26