Philosophy

Creating a new challenge should be as simple as possible and maintaining an existing one should be even more simple.

That's why we try to have multiple opinionated "drivers" that will match most common ecosystems:

• A web+database challenge backed by docker + docker-compose
• A static challenge (reverse, stegano) consisting of a binary or its sources + build instructions
• A shell/ssh challenge consisting of a Dockerfile
• A pown challenge mixing a shell challenge with an additional linked container

We plan to add more drivers later in order to support more advanced use-cases, including advanced networking, specific-hardware, etc. (First ideas are: k8s, VMs, hardware, lambdas, blockchains, etc)

Introduction

A Pathwar challenge is composed of:

• the challenge: container images, archives, binaries, ...
• metadata: container labels, configuration files, ...

This document describes the specifications to create an image.

If you plan to create your first challenge, we strongly encourage you to look at examples as a source of inspiration.

Docker images

The most common way of creating a challenge for Pathwar is by creating Docker images.

The minimal amount of modifications to make an existing image "pathway-ready" are:

• Adding an on-init hook that will path the challenge at runtime to put a unique passphrase.
• Define the exposed port types (HTTP, SSH, TCP, ...)

You can get a look at this minimal example: master/challenge/example/hello-world