[UPDATE #01 11/12/2015]: Volatility 2.5 was released recently. A standalone Linux executable is included with the 2.5 release. This installer is for Volatility 2.4. If you want to work with source code and get an idea of the dependencies needed by Volatility, review this installer's code. Otherwise, I'd recommend using the official Linux standalone executable. If you really want a working 2.5 installer update, see the fork of this project by @wzod).
What Is It?
4n6k_volatility_installer.sh is a bash script that installs Volatility 2.4 (and all dependencies) for Ubuntu Linux with one command.
Why Do I Need It?
Compiling source on Linux can be a pain. Dependency hunting wastes time and drives people away from considering Linux builds of cross-platform software. With this script, you can (1) skip all of the dependency frustration, (2) get right into using the newest version of Volatility, and (3) leverage the arguably more powerful and versatile *nix shell. No longer do you have to worry about whether or not you "have everything."
An internet connection and an APT-based Linux distribution [for the time being]. This script has been tested on stock Ubuntu 12.04 and Ubuntu 14.04. Some testing has been done to support SIFT Workstation 3.0.
What Does It Do?
Specifically, 4n6k_volatility_installer.sh does the following:
- Downloads, verifies, extracts, and installs source archives for everything you will need to complete a full installation of Volatility 2.4:
- Volatility 2.4
- Yara (+ magic module) + Yara-Python
- Python Imaging Library + Library Fixes
- Adds "vol.py" to your system PATH so that you can run Volatility from any location.
- Checks to see if you are using SIFT 3.0 and applies some fixes.
- From a terminal, run:
- sudo bash 4n6k_volatility_installer.sh /home/dan
- Contains dependency source code and the install_log.txt file.
- Contains the Volatility 2.4 install.
You can download the script from my Github page.
Check the Github page for the script's SHA256 hash.
Don't be afraid of the terminal. Read the source for this script and understand how it works. Automation is acceptable only after you understand what is happening behind the scenes.
I'm open to making this script better. If you see a problem with the code or can suggest improvements, let me know and I'll see what I can do.
Thanks to the Volatility team for writing an amazing tool. Go to http://www.volatilityfoundation.org for more info. Thanks to @The_IMOL, Joachim Metz, @dunit50, and @iMHLv2 for feedback.