| Steps To Reproduce | Kali-Live build
- This script helps you to build kali-live for different environments from a kali live system.
NOTE: These scripts are made for my personal environment. Why that? Well, as I am building on different computers,
and need a kali environment for build, but do not want to install kali on the hard drive, I decided to
use a kali-live. To ease things up, I created some scripts, so I do not need to enter the whole commands again and again.
Additionally I want to have a German environment (as I am German) and I wanted to have packages missing in kali.
See my added "mylist.list.chroot", what I have added. Furthermore I prefer LXDE (as it is running fastest on my "slow"
EEEPC 1005HGO) which is 32-bit. I am building on a TB drive, which I mount to "/mnt" and my live-build-config is put on
kali-linux/i386/ so the full path is (as you see in the scripts) "/mnt/kali-linux/i386/live-build-config/". Keep that in mint, when checking the configfiles and scripts I sent with.
In this packed file are also several debian packages (some are not in the repo like umtsmon or eeepc-acpi-scripts, and some are from external sites) I added to the chroot. They are all GPL, but you can check licenses before installing, yourself.
The build in this configuration will be about 3540 GB big, so it fits on a FAT formatted USB-stick. NOTE: Multibootloaders like
XBOOT or YUMI need FAT formatted sticks. Thus I could not install everything I wanted (openvas is missing and veil-catapult, too).
Also metapackage "forensics-full" is missing. Each one would increase the image at about 980MB, so adding all this will increase
the resulting ISO to 6,4GB (nice, when you want just use a single boot USB-stick or a double-layer DVD).
Description how it is recommended to handle as example for 32-bit, German environment and LXDE as window-manager.
Prerequesets:
NOTE: You will need to have a ext2-filesystem (or higher) and you will need at least 25GB free space.
- Boot kali live system for your build, if you have none, download any latest version from www.kali.org.
- Mount your harddrive, where your live-build resides to your mountpath in kali-live (mine is /mnt)
- create the first live-build environment (if you do not have one) like it is described on www.kali.org
- copy "uit-update.sh" and "uit-build.sh" to your ~/live-build-config/
- now execute "lb config", which will create the configfiles for your live-build-environment
- copy "mylist.list.chroot" into ~/live-build-config/package-list/ and edit it to your needs.
- copy all packages from "packages.chroot/*" into ~/live-build-config/packages.chroot/
- copy "acng.conf" into your ~/live-build-config/ and edit it, that it points to your future local repo
Once you have done it, check the following:
-
Checck ./uit-update.sh
This script is dating your runninmg kali-live up and upgrades or installs all necessary packages for the build.
You have to make sure, that the paths especially in "acng.conf" are set correctly!
-
Check ./uit-build.sh
This script does the actual build. It shall be explained for itself, however, you have to make sure, to set all your
variables correctly. Note, that ./uit-update.sh and ./uit-build.sh are dependent. Later I might merge these two scripts,
but today I am happy with these two ones as they give me the most flexibility at the moment.
Once you have vedrified all variables, first execute ./uit-update.sh. This will update your running kali-live and installing and updating all necessary packages.
(Hint: After building your first image, use that for your next build. Makes things much easier!)
Now execute ./uit-build.sh and lean back - everything is done automatically.
Good luck and happy hunting!
Best
Hans-J. Ullrich |
|---|
| Additional Information | This is my very personal change and improvement. If you do not like them, just delete it and close this report.
For any questions, feel free to ask me, i.e. why I have added this special package or why I added this tool or what you do like or not, whatever.
As I said: It is my personal environment, and for me it is working great since years, but note: It is still in development, so things may still look ugly. You are allowed, to improve it. :) |
|---|
