ikelos

Yeah, I think you've found an issue that will be encountered by many of our plugins. I'm still debating the best of dealing with this though. I can't figure out...

> @ikelos exposing the full hex+ascii dump contents of hits is pretty critical. Right now the results of the plugins are pretty bare and useless, and its been the main...

Just to update, this is waiting on me to develop a better "data" output that will allow a UI to specify how much context should be provided to data blocks....

Hiya, I got as far as [`feature/data-renderer`](https://github.com/volatilityfoundation/volatility3/tree/feature/data-renderer) which fleshes out the idea, but I hit the stumbling point of how to define the API for getting options to the renderer....

It doesn't need to be perfect, and we don't even need to implement the ability to pull in options, we just have to get something that *could* flexibly accept any...

So I'd say going more along the lines of #1622, if you'd like to give it a review?

Thanks for your bug report, but you really haven't included enough information here to act upon it? We ask all people filing bugs to include the results of running `vol.py...

Thanks, this appears to be an issue in the pycryptodome package: ``` File "/home/osboxes/.local/lib/python3.12/site-packages/Crypto/Util/_raw_api.py", line 31, in import imp ModuleNotFoundError: No module named 'imp' ``` I'm also a little concerned...

We've found that some pdb we've retrieved in the past couple of years for old systems (win7) no longer contain all the necessary type information. This can be checked by...

You could check if the excess bytes are always `00` and therefore suggests it's padding? If there's a total length field being used, that might also make sense?