volatilityfoundation / volatilityfoundation/volatility3
Potential support of minidump formats from processes?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.4k
- Forks
- 705
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 3
Description
First of all I would like to say thank you to all the contributors of volatility. This has by far been a fun experience diving into forensics for me!
I have a more of a question then an explicit issue and I am hoping someone can answer it.
Does volatility3 currently have the capability of dumping a process memory in the minidump file format?
There is other projects I have noted that take physical memory and create physical process memory to minidump formats by they are no longer maintained. (I.E. Rekall framework)
Thank you again!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Begin by checking Volatility 3's current process-memory dumping support and the requirements for minidump output; done would be a documented capability answer or a clearly scoped implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100