Ticket #25898 (closed submission: fixed)
[NEW] security/volatility
| Reported by: | jul_bsd@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | Cc: | ||
| Port: | volatility |
Description
The Volatility Framework is a completely open collection of tools, implemented in Python under the GNU General Public License, for the extraction of digital artifacts from volatile memory (RAM) samples. The extraction techniques are performed completely independent of the system being investigated but offer unprecedented visibilty into the runtime state of the system. The framework is intended to introduce people to the techniques and complexities associated with extracting digital artifacts from volatile memory samples and provide a platform for further work into this exciting area of research.
Attachments
Change History
comment:1 Changed 3 years ago by ryandesign@…
- Status changed from new to assigned
- Owner changed from macports-tickets@… to ryandesign@…
- Port set to volatility
comment:2 Changed 3 years ago by ryandesign@…
- Status changed from assigned to closed
- Resolution set to fixed
Thanks, committed in r70206 with these changes:
- whitespace / formatting
- made you the maintainer with openmaintainer
- removed the "GPL" comment and added "license GPL-2+" (since comments in the source code says it is licensed under GPL version 2 or any later version)
- tweaked long_description
- removed "depends_lib port:python26" as the python26 portgroup already adds that for you
- moved your post-build reinplaces to post-patch and fixed the shebang reinplace so it works (the backslashes needed two levels of escaping: one for tcl's double quotes and one for the regex engine)
- simplified post-destroot by removing foreach loops
- installed all the documentation files not just README.txt
- removed commented-out code in post-destroot
- added "supported_archs noarch" because this port does not install any architecture-specific files
- fixed livecheck
Note: See
TracTickets for help on using
tickets.

