amitie10g/covenant repository overview

⁠amitie10g/covenant⁠

Covenant⁠ - A collaborative .NET C2 framework for red teamers.

⁠Usage

This configuration is ephimeral. Once removed the container, everything is lost. The container-side C:\app\Data data directory must be exposed to the host, but this is not implemented in Windows, as I tested.

⁠docker

docker create `
  --name=covenant `
  -e TZ=Europe/London `
  -p 7443:7443 `
  -p 443:443 `
  -p 80:80 `
  --restart unless-stopped `
  amitie10g/covenant:<tag>

⁠docker-compose

Compatible with docker-compose v2 schemas.

version: "3.3"
services:
  covenant:
    image: amitie10g/covenant:<tag>
    container_name: covenant
    environment:
      - TZ=Europe/London
    ports:
      - 7443:7443
      - 443:443
      - 80:80
    restart: unless-stopped

⁠Tags

• latest 21H2 ltsc2022 using .NET 3.1 under Nano Server ltsc2022
• 20H2 using .NET 3.1 under Nano Server 20H2
• buster using .NET 3.1 under Debian Buster (amd64 and arm64)

⁠Parameters

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

⁠Application Setup

Access the webui at <your-ip>:7443, for more information check out Covenant⁠.

⁠Support Info

• To monitor the logs of the container in realtime: docker logs -f covenant

⁠Building locally

This image comes from the Covenant's official repository, forked to customise the Dockerfile.

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone --recurse-submodules https://github.com/cobbr/Covenant.git
cd Covenant\Covenant
docker build \
  --no-cache \
  --pull \
  -t covenant .

⁠Versions

• 10.30.19: - First Push