Skip to content

Latest commit

 

History

History
75 lines (68 loc) · 3.2 KB

CONTRIBUTE.md

File metadata and controls

75 lines (68 loc) · 3.2 KB
Raw

How to contribute?

Firstly, please take the following quick survey which can help you start efficiently.

switch challenge_type:
  case 'web':
    if languge == 'PHP':
      if need_db_support:
        jump step 1
      else:
        jump step 2
    else:
      jump step 5
  case 'pwn':
    if arch == 'x86-64':
      jump step 3
    elif arch == 'x86':
      jump step 4
  default:
    jump step 5

1. PHP Challenge With DB support

  • name your challenge and create a folder under web/ directory, this directory will the your challenge root, eg: easy-injection 
    cd web
mkdir easy-injection
cd easy-injection
  • copy all file from the challenge template folder example/web/db/, eg: 
    cp -r example/web/db/* ./
  • Edit Dockerfile and docker-compose.yml to config your vulnerability environment. (Actually normally the only thing you need to change is the MAINTAINER field)
  • Copy your source code to folder source
  • Copy your database init script as database.sql
  • Run docker-compose build to make sure your Dockerfile and docker-compose.yml have no errors.
  • Run docker-compose up -d to start the vulnerability environment.
  • Test whether your challenge is set successfully, it depends on the logic of your challenge.

2. PHP Challenge

  • name your challenge and create a folder under web/ directory, this directory will the your challenge root, eg: easy-injection 
    cd web
mkdir easy-injection
cd easy-injection
  • Edit Dockerfile and docker-compose.yml to config your vulnerability environment. (Actually normally the only thing you need to change is the MAINTAINER field)
  • Copy your source code to folder source
  • Run docker-compose build to make sure your Dockerfile and docker-compose.yml have no errors.
  • Run docker-compose up -d to start the vulnerability environment.
  • Test whether your challenge is set successfully, it depends on the logic of your challenge.

3. PWN Challenge on x64 architure

  • name your challenge and create a folder under pwn/ directory, this directory will the your challenge root, eg: buffer-overflow 
    cd pwn
mkdir buffer-overflow
cd buffer-overflow
  • Edit Dockerfile and docker-compose.yml to config your vulnerability environment. (Actually normally the only thing you need to change is the MAINTAINER field)
  • Copy your source code and Makefile(Important) to folder source (Please rename your C filename as pwn.c, just for tidiness)
  • Run docker-compose build to make sure your Dockerfile and docker-compose.yml have no errors.
  • Run docker-compose up -d to start the vulnerability environment.
  • Test whether your challenge is set successfully, it depends on the logic of your challenge.

4. PWN Challenge on x86 architure

  • Please follow step 3, the only difference is that you should change Dockerfile You should change the first line from FROM ubuntu:16.04 to FROM i386/ubuntu:16.04

5. Other Challenge

  • Your are an excellent hacker, I believe that you can get things done prefectly.

Reference

Best practices for writing Dockerfiles