You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
volatility is restricted to Python2. volatility3 replaces it but the whole plugin API changed.
LiME project is archived. (tried on a recent kernel: it just hangs indefinitely). NB: I don't see why a system memory dump is necessary in the first place
Since the project is still very relevant nowadays, could one of this be realistic:
Updating to volatility3
Not relying on the volatility framework at all (only iasl)
?
The text was updated successfully, but these errors were encountered:
I already realized that volatility2 is deprecated. The API changes kept me from migrating this plugin as I have to rewrite the code entirely.
As for your remarks:
LiME is only an example. You can use winpmem or linpmem or any other RAM dumping tool compatible with volatility.
I am considering updating to volatility3 - currently busy detecting RAM injections on large scale, so migration will happen rather end of 2024 or 2025.
Do you have a suggestion of how to get the ACPI tables without volatility/RAM dumps? (dumping from mainboard is not an option because the mainboard interface is controlled by the attacker when they flash the mainboard, so the attacker could return a clean image)
LiME
project is archived. (tried on a recent kernel: it just hangs indefinitely). NB: I don't see why a system memory dump is necessary in the first placeSince the project is still very relevant nowadays, could one of this be realistic:
iasl
)?
The text was updated successfully, but these errors were encountered: