Results 1 to 6 of 6

Thread: Adding custom packages (.deb) to the Kali 2.0 live-build process

  1. #1
    Junior Member
    Join Date
    May 2013
    Posts
    4

    Adding custom packages (.deb) to the Kali 2.0 live-build process

    I'm attempting to build a custom Kali 2.0 ISO that has Nessus pre-installed on it. However, I can't locate the packages directory to place the .deb file in under the kali-config tree. I had been using the Kali documentation as a guide for this and it references a packages directory.

    Any help would be greatly appreciated!

    Thanks

  2. #2
    Junior Member
    Join Date
    Jul 2015
    Posts
    2
    config/packages.chroot for .deb packages

  3. #3
    Junior Member
    Join Date
    May 2013
    Posts
    4
    Quote Originally Posted by jezzivi View Post
    config/packages.chroot for .deb packages
    Except that when one downloads the live-build-config from git for Kali, there is no config directory. There's a kali-config directory and then various desktop variants. After build.sh is run, I see a config directory.

  4. #4
    Junior Member
    Join Date
    May 2013
    Posts
    4
    After running build.sh, the config/packages.chroot directory is there. I placed my Nessus-6.6.2-debian6_amd64.deb in that folder and reran build.sh. THe build fails and the log indicates "Unable to locate package Nessus"

    Is there another location I need to edit to allow the live build to find the package?

  5. #5
    Junior Member
    Join Date
    Jan 2017
    Posts
    1
    To add external .deb to kali repositories create a packages folder : live-build-config / kali-config / common / packages
    To add .deb from the kali repositories add the package names to the kali.list.chroot file
    Last edited by maiki; 2017-01-19 at 10:00 AM. Reason: Non English

  6. #6
    So the latest Nessus.deb is not a valid Debian package. Debian packages cannot be Upper case (Nessus), and have to be (nessus). https://bugs.debian.org/cgi-bin/bugr...cgi?bug=818907
    I have soleved the issue by renaming and repacking the Nessus.deb packages as per
    https://unix.stackexchange.com/quest...and-repack-deb

    Thanks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •