Debian

ThreatLockDown provides an automated way of building DEB packages using docker so there is no need for any other dependency.

To create an Debian package follow these steps:

Requirements

  • Docker

  • Git

Download our wazuh-packages repository from GitHub and go to the debs directory.

$ git clone https://github.com/wazuh/wazuh-packages && cd wazuh-packages/debs && git checkout v4.9.0

Execute the generate_debian_package.sh script, with the different options you desire. This script will build a Docker image with all the necessary tools to create the DEB and run a container that will build it:

# ./generate_debian_package.sh -h

Usage: ./generate_debian_package.sh [OPTIONS]

    -b, --branch <branch>      [Required] Select Git branch.
    --packages-branch <branch> [Required] Select Git branch or tag from wazuh-packages repository.
    -t, --target <target>      [Required] Target package to build: manager or agent.
    -a, --architecture <arch>  [Optional] Target architecture of the package [amd64/i386/ppc64le/arm64/armhf].
    -j, --jobs <number>        [Optional] Change number of parallel jobs when compiling the manager or agent. By default: 2.
    -r, --revision <rev>       [Optional] Package revision. By default: 1.
    -s, --store <path>         [Optional] Set the destination path of package. By default, an output folder will be created.
    -p, --path <path>          [Optional] Installation path for the package. By default: /var/ossec.
    -d, --debug                [Optional] Build the binaries with debug symbols. By default: no.
    -c, --checksum <path>      [Optional] Generate checksum on the desired path (by default, if no path is specified it will be generated on the same directory than the package).
    --dont-build-docker        [Optional] Locally built docker image will be used instead of generating a new one.
    --sources <path>           [Optional] Absolute path containing ThreatLockDown source code. This option will use local source code instead of downloading it from GitHub.
    --dev                      [Optional] Use the SPECS files stored in the host instead of downloading them from GitHub.
    --future                   [Optional] Build test future package x.30.0 Used for development purposes.
    -h, --help                Show this help.

Below, you will find some examples of how to build a DEB package.

# ./generate_debian_package.sh -b v4.9.0 --packages-branch v4.9.0 -s /tmp -t manager -a amd64 -r my_rev.

This will generate a 4.9.0 ThreatLockDown manager package DEB with revision my_rev for amd64 systems.

# ./generate_debian_package.sh -b v4.9.0 --packages-branch v4.9.0 -s /tmp -t api -a i386 -r my_rev

This will generate a 4.9.0 ThreatLockDown api package DEB with revision my_rev for i386 systems and store it in /tmp.

# ./generate_debian_package.sh -b v4.9.0 --packages-branch v4.9.0 -t agent -a amd64 -p /opt/ossec

This will generate a 4.9.0 ThreatLockDown agent DEB package with /opt/ossec as installation directory for amd64 systems.