Automagic modules allow the framework to populate configuration elements that a user has not provided.
Automagic objects accept a context and a configurable, and will make appropriate changes to the context in an attempt to fulfill the requirements of the configurable object (or objects upon which that configurable may rely).
Several pre-existing modules include one to stack layers on top of each other (allowing automatic detection and loading of file format types) as well as a module to reconstruct layers based on their provided requirements.
Returns an ordered list of all subclasses of
The order is based on the priority attributes of the subclasses, in order to ensure the automagics are listed in an appropriate order.
Chooses which automagics to run, maintaining the order they were handed in.
run(automagics, context, configurable, config_path, progress_callback=None)¶
Runs through the list of automagics in order, allowing them to make changes to the context.
str) – The path within the context.config for options required by the configurable
This is where any automagic is allowed to run, and alter the context in order to satisfy/improve all requirements
Returns a list of traceback objects that occurred during the autorun procedure
The order of the automagics list is important. An automagic that populates configurations may be necessary for an automagic that populates the context based on the configuration information.
- volatility.framework.automagic.construct_layers module
- volatility.framework.automagic.linux module
- volatility.framework.automagic.mac module
- volatility.framework.automagic.pdbscan module
- volatility.framework.automagic.stacker module
- volatility.framework.automagic.symbol_cache module
- volatility.framework.automagic.symbol_finder module
- volatility.framework.automagic.windows module