adhdproject / buildkit-ng Goto Github PK

Create and test installation script for Jar-Combiner

Low priority item. Change the adhd-install.sh script to assume -i if no argument is specified. Include a message along the lines of "No argument specified. Assuming -i" when this happens.

Create and test installation script for Kippo

Document the minimum system requirements for installation, including supported operating systems, minimum RAM and minimum disk space.

Create and test installation script for Sweeper

All scripts and wrapper scripts need to be tested for functionality and formatted output.

Create and test installation script for Portspoof

Create and test installation script for Decloak

Create and test installation script for DenyHosts

Create and test installation script for Web Bug Server

dev branch commit fixes this by setting the Bashe's cwd to where the installation script is located.

dev commit that fixes: e54c0d9

Create and test installation script for HoneyBadger

Create and test installation script for Docz.py

Create and test installation script for Invisiport

Our gamification solution may live in a different repo, but I'll open the issue here for now.

This is assuming we have time remaining, but we appear to still be on track.

Create and test installation script for OpenBAC

Create and test installation script for HoneyBadger Red

Create and test installation script for Sqlite Bug Server

Create and test installation script for OsChameleon

Create and test installation script for PHP-HTTP-Tarpit

Create and test installation script for Bear Trap

Create and test installation script for Lockdown

Create and test installation script for Gcat

Create and test installation script for PSAD

Create and test installation script for Java-Web-Attack

Create and test installation script for Ghostwriting.sh

Create and test installation script for TALOS

Add intelligent error handling to scripts.

My current plan is to use the following function:

runcmd() {
        $1 2>/dev/null;
        s=$(($s+$?));
}

where $s is a local variable for status code (subject to change), and $1 is the command to be executed. This is a concise way to keep track of return codes, because most errors that can be encountered are not fatal to the script. This way, we can simply return $s from the end of both install and uninstall functions and the caller can handle the output.

Create and test installation script for Simple-Pivot-Detect

Create and test installation script for Recon-ng

Create and test installation script for Pushpin

Create and test installation script for Cryptolocked

Create and test installation script for TcpRooter

Create and test script for Artillery

Create and test installation script for Wordpot

Create and test installation script for Rubberglue

When each package finishes installing, include the full path to the binary or install directory in the output. For example, change the message "ExamplePackage installed!" to "ExamplePackage installed to /opt/bin/example!"

Create and test installation script for Spidertrap

Create and test installation script for SET

A wrapper script to install all tools needs to be created.

It would also be very cool to incorporate a CLI-GUI version of the old installer where individual tools/tool groups can be selected, but that isn't the top priority.

Hopefully, all scripts can be called relatively simply.

Create and test installation script for Beef

Create and test installation script for Honey Ports

Create and test installation script for Human.py

Add binaries for each package to $PATH.

Create and test installation script for Weblabyrinth