With this version, arm firmware are excluded from x86 isos, and the
other way round. In practice, it means that raspi-firmware won't be
installed on amd64 isos, and that's something we need.
The package exploitdb-papers was removed from kali-tools-identify in
src:kali-meta 2023.1.11, so there's no need to exclude it here anymore.
As a consequence, no need for the network during installation anymore.
Other things that I tried, but that didn't work, below:
I tried adding the preseed to simple-cdd/profiles/kali-purple.preseed,
however that didn't work, I guess that this preseed file is loaded only
later during installation, and that at this point the GUI was already
loaded and it's too late to set the theme.
I also tried to do this in simple-cdd.conf:
# Theming
if echo " $profiles " | grep -q " kali-purple "; then
export KERNEL_PARAMS="${KERNEL_PARAMS} debian-installer/theme=Clearlooks-Purple "
fi
But it doesn't work, seemingly 'profiles' is not set when simple-cdd
loads the conf, and even though we build with the command:
build-simple-cdd [...] --profiles "$profiles" [...]
Given the fact that uppercase variables are exported, and what we
actually want to change is KERNEL_PARAMS, it seems that the most
straightforward is just to preset it from build.sh.
build.sh:
Note that the installer-purple variant does NOT include the offline
profile, that's on purpose. There's no requirement for this installer to
work offline, and on top of that, we can't include all the packages in
the iso at the moment (the package exploitdb-papers is too big). So we
very much expect to have network, and to download big packages during
the installation.
See next commits for more details.
kali-config/installer-purple/packages:
Unlike other variants, the "base" metapackage is kali-system-core,
which is a very stripped down metapackage with no offensive tools.
(kali-system-core is basically what used to be kali-linux-core, minus
the few offensive tools that were in there).
With this change, we do NOT set profiles based on DISKTYPE anymore.
Instead, we set profiles (and auto_profiles) in build.sh, depending on
the variant.
This change is in preparation for next commit, where we'll introduce a
new installer variant.
On a Debian unstable system, the file `/etc/debian_version` contains
only `11.0`, so the script `build.sh` gives me this kind of log:
OS: 11.0
Not super informative. However the file `/usr/lib/os-release` provides
more details, and by using it we can get the following log:
OS: Debian GNU/Linux 11 (bullseye)
For a Kali system:
OS: Kali GNU/Linux 2021.2
The DVD size limit has been reached and the build currently fails due to
this. We don't really want to burn DVD as ISO images are written on USB
keys and the exact size doesn't really matter for use in virtual
machines. So let's instruct debian-cd to build a bluray image so that
we no longer are annoyed with the size limit.
At least everywhere where we can end up with the output of "pwd"
in the variable so that we don't break when some directory has
spaces or other unusual characters in it.
This reverts commit d2b4645fb4.
Initial commit said “run_and_log doesn't like redirects, but I don't
think thats an issue” but it is a real issue when the whole point of the
command is to modify/overwrite a file with a redirection.
Keep only run_and_log for the final file moves.
g0t mi1k
Arnaud Rebillout
Ben Wilson
Raphaël Hertzog
Daniel Ruiz de Alegría
g0t mi1k
Steev Klimaszewski
Kevin Chevreuil - Kaisen