Making your own Kali Linux Metapackages

One of the numerous helpful things we can do with APT is make metapackages, which are viably unfilled bundles that announce a rundown of different bundles as conditions. Kali Linux incorporates metapackages for secret key splitting, programming characterized radio, remote, web applications, and all the more yet in the event that you have particular needs (like the vast majority), it's fast and simple to characterize your own metapackages, which we will appear in this post. Before we start, we have to introduce the devscripts bundle, which incorporates various instruments and utilities for bundle administration.

root@kali:~# apt install devscripts

In Kali, all metapackages are characterized in the suitably named kali-meta bundle so we can clone and adjust it to suit our requirements.

root@kali:~# git clone git://git.kali.org/packages/kali-meta Cloning into 'kali-meta'... remote: Counting objects: 998, done. remote: Compressing objects: 100% (809/809), done. remote: Total 998 (delta 365), reused 0 (delta 0) Receiving objects: 100% (998/998), 179.90 KiB | 570.00 KiB/s, done. Resolving deltas: 100% (365/365), done. warning: remote HEAD refers to nonexistent ref, unable to checkout.

The "unfit to checkout" message above looks troubling however it just implies that the default branch (kali/ace) should be looked at first, which should be possible as takes after.

root@kali:~# cd kali-meta/ root@kali:~/kali-meta# git checkout kali/master Branch 'kali/master' set up to track remote branch 'kali/master' from 'origin'. Switched to a new branch 'kali/master' root@kali:~/kali-meta#

To make another metapackage (or refresh a current one), we have to alter the debian/control record with the bundle data. Each metapackage is just a comma-isolated rundown of bundle conditions, similar to the one for the kali-linux-gpu demonstrated as follows.

Package: kali-linux-gpu Architecture: any Depends: ${misc:Depends}, kali-linux, oclhashcat [amd64 i386], pyrit, oclgausscrack [amd64 i386], truecrack,

Our new metapackage will be designated "kali-linux-mytools" and will introduce Vagrant, VirtualBox, LibreOffice, and Chromium. Our entrance for this metapackage in debian/control resembles this:

root@kali:~/kali-meta# tail -n 14 debian/control Package: kali-linux-mytools Architecture: any Depends: ${misc:Depends}, kali-linux, virtualbox, vagrant, libreoffice, chromium, Description: My required Kali tools This is Kali Linux, the most advanced penetration testing and security auditing distribution. . This metapackage depends on the tools I install most often.

With the new metapackage characterized, we have to knock the adaptation number with 'dch' before building the bundle. This will dispatch a supervisor for you to enter the points of interest of your progressions in debian/changelog.

root@kali:~/kali-meta# dch --local dookie root@kali:~/kali-meta# head -n 5 debian/changelog kali-meta (2018.3.2dookie1) UNRELEASED; urgency=medium * Added kali-linux-mytools -- dookie Tue, 11 Sep 2018 09:40:10 -0600

At long last, we can continue to manufacture the new bundle with the 'dpkg-buildpackage' order. Since metapackages are simply arrangements of conditions, the construct procedure is fast.

root@kali:~/kali-meta# dpkg-buildpackage -us -uc -b dpkg-buildpackage: info: source package kali-meta dpkg-buildpackage: info: source version 2018.3.2dookie1 dpkg-buildpackage: info: source distribution UNRELEASED dpkg-buildpackage: info: source changed by dookie dpkg-buildpackage: info: host architecture amd64 ... dpkg-deb: building package 'kali-linux-pwtools' in '../kali-linux-pwtools_2018.3.2dookie1_amd64.deb'. dpkg-deb: building package 'kali-linux-top10' in '../kali-linux-top10_2018.3.2dookie1_amd64.deb'. dpkg-deb: building package 'kali-linux-mytools' in '../kali-linux-mytools_2018.3.2dookie1_amd64.deb'. dpkg-genbuildinfo --build=binary dpkg-genchanges --build=binary >../kali-meta_2018.3.2dookie1_amd64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build kali-meta dpkg-buildpackage: info: binary-only upload (no source included)

At the point when the manufacture is finished, our new metapackage can be introduced with 'able' like some other bundle.

root@kali:~/kali-meta# apt install ../kali-linux-mytools_2018.3.2dookie1_amd64.deb ... root@kali:~/kali-meta# apt-cache policy vagrant virtualbox libreoffice chromium vagrant: Installed: 2.1.2+dfsg-1 Candidate: 2.1.2+dfsg-1 Version table: *** 2.1.2+dfsg-1 500 500 http://192.168.86.4/kali kali-rolling/main amd64 Packages 100 /var/lib/dpkg/status virtualbox: Installed: 5.2.18-dfsg-2 Candidate: 5.2.18-dfsg-2 Version table: *** 5.2.18-dfsg-2 500 500 http://192.168.86.4/kali kali-rolling/contrib amd64 Packages 100 /var/lib/dpkg/status libreoffice: Installed: 1:6.1.1~rc1-2 Candidate: 1:6.1.1~rc1-2 Version table: *** 1:6.1.1~rc1-2 500 500 http://192.168.86.4/kali kali-rolling/main amd64 Packages 100 /var/lib/dpkg/status chromium: Installed: 68.0.3440.75-2 Candidate: 68.0.3440.75-2 Version table: *** 68.0.3440.75-2 500 500 http://192.168.86.4/kali kali-rolling/main amd64 Packages 100 /var/lib/dpkg/status

Much the same as that, we have our own metapackage that we can store on organize offer or some other area to rapidly get our crisp Kali Linux establishments set up and arranged rapidly.