Bug 1767228 - Review Request: b'python-volatility3' - b'Volatility 3: The volatile memory extraction framework'
Summary: Review Request: b'python-volatility3' - b'Volatility 3: The volatile memory e...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: Package Review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-30 23:09 UTC by Michal Ambroz
Modified: 2019-10-30 23:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-10-30 23:14:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Ambroz 2019-10-30 23:09:32 UTC
Spec URL: https://rebus.fedorapeople.org//python-volatility3.spec
SRPM URL: https://rebus.fedorapeople.org//python-volatility3-1.0.0-0.1.beta.1.fc30.src.rpm

Description:
b'Volatility is the world\xe2\x80\x99s most widely used framework for extracting digital\nartifacts from volatile memory (RAM) samples. The extraction techniques are\nperformed completely independent of the system being investigated but offer\nvisibility into the runtime state of the system. The framework is intended\nto introduce people to the techniques and complexities associated with\nextracting digital artifacts from volatile memory samples and provide a\nplatform for further work into this exciting area of research.\n\nIn 2019, the Volatility Foundation released a complete rewrite of the\nframework, Volatility 3. The project was intended to address many of the\ntechnical and performance challenges associated with the original\ncode base that became apparent over the previous 10 years. Another benefit\nof the rewrite is that Volatility 3 could be released under a custom\nlicense that was more aligned with the goals of the Volatility community,\nthe Volatility Software License (VSL).'


Note You need to log in before you can comment on or make changes to this bug.