diff --git a/.github/workflows/push-to-main.yml b/.github/workflows/push-to-main.yml deleted file mode 100644 index 6aacd89..0000000 --- a/.github/workflows/push-to-main.yml +++ /dev/null @@ -1,35 +0,0 @@ -name: push-to-main -#a github action that will trigger on push to main or dev branch -# will run the build_tracelabsiso_recipe.sh script inside a kali docker container -on: - push: - branches: - - main - - dev # Added the dev branch here - -jobs: - run-docker: - # Specifies that the job runs on a macOS environment - runs-on: macos-12 - # checkout the code from the repository - steps: - - uses: actions/checkout@v4 - - # Sets up Docker environment on macOS runner - - name: Install Docker - run: | - brew install docker - colima start - - - # build docker image - - name: build docker image - run: | - cd $GITHUB_WORKSPACE - chmod +x *.sh - docker build -t tlm1-builder . - - # use docker to run the build_tracelabsiso_recipe.sh script - - name: Run Docker command - run: | - docker run --rm --interactive --net host --privileged --volume $(pwd):/recipes --workdir /recipes tlm1-builder ./build_tracelabsiso_recipe.sh \ No newline at end of file diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml deleted file mode 100644 index 80e557a..0000000 --- a/.github/workflows/release.yml +++ /dev/null @@ -1,42 +0,0 @@ -name: release -#a github action that will trigger on push to main or dev branch -# will run the build_tracelabsiso_recipe.sh script inside a kali docker container -on: - push: - tags: - - '*' - -jobs: - run-docker: - # Specifies that the job runs on a macOS environment - runs-on: macos-12 - permissions: - contents: write - # checkout the code from the repository - steps: - - uses: actions/checkout@v4 - - # Sets up Docker environment on macOS runner - - name: Install Docker - run: | - brew install docker - colima start - - - # build docker image - - name: build docker image - run: | - cd $GITHUB_WORKSPACE - chmod +x *.sh - docker build -t tlm1-builder . - - # use docker to run the build_tracelabsiso_recipe.sh script - - name: Run Docker command - run: | - docker run --rm --interactive --net host --privileged --volume $(pwd):/recipes --workdir /recipes tlm1-builder ./build_tracelabsiso_recipe.sh - - name: Release with Notes - uses: softprops/action-gh-release@v1 - with: - files: "images/*.*" - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} \ No newline at end of file diff --git a/build-in-container.sh b/build-in-container.sh index 4230d94..4f5c4d0 100755 --- a/build-in-container.sh +++ b/build-in-container.sh @@ -1,6 +1,5 @@ #!/bin/bash -# checks for either Podman or Docker, then builds the container image and runs it -# normal args can be passed to the build.sh script, e.g. --no-cache +# script that will build a kali linux image and build our iso inside set -eu IMAGE=tlm1-builder @@ -10,9 +9,6 @@ OPTS=( --volume $(pwd):/recipes --workdir /recipes ) -bold() { tput bold; echo "$@"; tput sgr0; } -vrun() { bold "$" "$@"; "$@"; } -vexec() { bold "$" "$@"; exec "$@"; } # build docker image if it doesn't exist docker build -t $IMAGE . # run the build script inside a container diff --git a/how-to-add-a-tool.txt b/how-to-add-a-tool.txt deleted file mode 100644 index 83885b1..0000000 --- a/how-to-add-a-tool.txt +++ /dev/null @@ -1,30 +0,0 @@ -There are several places in this repo you will need to modify to add a new tool -to this flavor of kali - -*** kali-config/common/hooks/normal/osint-packages.chroot *** - -Think of this file as the "install script" for all the additional tools. -This will contain the instructions to get our tools installed. -Follow the examples in the file. -Normally: pull down git repo, install dependencies, move our helper script, make helper executable - -*** kali-config/common/includes.chroot/usr/share/applications/ **** - -This folder contains the information for menu icons. -Follow the examples and add one for your new tool. -Essentially, these icons just kick off a helper script stored in /usr/bin - - -*** kali-config/common/includes.chroot/usr/bin/ *** - -This folder contains the helper scripts that kick off our tools. -You'll need to create one for the tool you are installing. -Follow the examples but essentially it's one line that runs your tool -Note: All of these helper scripts will get moved to /usr/bin/ during the install process above - - -*** /kali-config/variant-tracelabs/package-lists/kali.list.chroot *** - -Think of this file as the reference list of additional tools. -This will contain only the tool names (e.g. sherlock, maltego, etc.) -Follow the examples in the file. diff --git a/how-to-test-your-build.txt b/how-to-test-your-build.txt deleted file mode 100644 index 23fafbe..0000000 --- a/how-to-test-your-build.txt +++ /dev/null @@ -1,17 +0,0 @@ -**** Fork the Trace Labs repo **** - -*** Clone your fork on to your machine **** - -*** Make changes ***** - -*** Push changes to your repo **** - -*** Launch regular Kali in VM **** - -*** git clone the repo you just pushed to and cd to it *** - -*** modify the build script to pull from your repo, not the TL repo **** - -*** run build script *** - -*** test the resulting iso ****