Offensive Security Kali Linux ARM build scripts. We use these to build our official Kali Linux ARM images, as can be found at http://www.kali.org/downloads/
-
These scripts have been tested on a Kali Linux 32 and 64 bit installations only, after making sure that all the dependencies have been installed.
-
Make sure you run the build-deps.sh script first, which installs all required dependencies.
-
You will need to use the cross compilers from our github account.
armel images (RPi) will use https://github.com/offensive-security/gcc-arm-eabi-linaro-4.6.2
armhf images will use https://github.com/offensive-security/gcc-arm-linux-gnueabihf-4.7
A sample workflow would look similar to (armhf):
mkdir ~/arm-stuff
cd ~/arm-stuff
git clone https://github.com/offensive-security/gcc-arm-linux-gnueabihf-4.7
export PATH=${PATH}:/root/arm-stuff/gcc-arm-linux-gnueabihf-4.7/bin
git clone https://github.com/offensive-security/kali-arm-build-scripts
cd ~/arm-stuff/kali-arm-build-scripts
./build-deps.sh
./chromebook-arm-samsung.sh 1.0
If you are on 32bit, after the script finishes running, you will have an image file located in ~/arm-stuff/kali-arm-build-scripts/chromebook-1.0/ called kali-1.0-chromebook.img and a sha1sum file for it. You will need to use your own preferred compression if you want to distribute it.
On 64bit systems, after the script finishes running, you will have 3 files located in ~/arm-stuff/kali-arm-build-scripts/chromebook-1.0; the sha1sum for the uncompressed image file, the image file compressed via xz, and the sha1sum file for the compressed image file.
Note from Tyler: I've moved my work to https://bitbucket.org/mchineboy007/kali-arm-build-scripts My reasons for this are numerous. But the biggest reason is the recent changes within the GitHub organization itself. When they pull their collective heads out of their asses, maybe I'll come back. I wasn't a big "enterprise" customer, so they likely won't care. But I couldn't justify giving my money to these people anymore.