https://github.com/oj/bsides-2017-ctf-docker

BSidesCBR CTF docker compose files
https://github.com/oj/bsides-2017-ctf-docker

ctf docker-compose

Last synced: 18 days ago
JSON representation

BSidesCBR CTF docker compose files

• Host: GitHub
• URL: https://github.com/oj/bsides-2017-ctf-docker
• Owner: OJ
• Created: 2017-03-19T10:14:11.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2020-06-04T03:10:54.000Z (over 4 years ago)
• Last Synced: 2024-10-14T17:17:34.396Z (about 1 month ago)
• Topics: ctf, docker-compose
• Size: 2.37 MB
• Stars: 68
• Watchers: 6
• Forks: 29
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# BSidesCBR 2017 CTF docker compose files

This repo contains all the docker-compose files that spin up the BSidesCBR 2017 CTF challenges. Each of the challenges listed here was available as part of the CTF, though unfortunately some challenges weren't able to be dockerised and released.

### Don't cheat!

See the FAQ. Don't do yourself out of the challenge!

## Running challenges

### HTTPS stuff

Each of the web challenges has a certificate for `web.shell.dance` that was generated via Lets Encrypt. Expect to see SSL errors in your browser, unless you decide to add an entry to your hosts file that points `web.shell.dance` at `127.0.0.1` (this is recommended). If you don't, the rest of the instructions won't make sense! Skipping this step means using `localhost` instead of `web.shell.dance` wherever you see it.

Should I be pushing images with the SSL certs in them? Probably not, but they'll expire soon anyway.

### Docker container execution

Each subfolder maps to a challenge. In order to run that particular challenge, simply:

1. `cd` to the folder that contains the challenge you wish to attempt.

1. run `docker-compose up`

1. Read the `README.md` inside the folder for details on where to find the challenge.

At this time, we don't have the scoreboard available, but hopefully that won't stop you from owning it!

Make sure that you give the containers enough time to spin up. The first time you run them, they have to be downloaded, so give it a while. Once they're down, some of the challenges (web in particular) take a bit of time to get running. So if they don't work the first time, just wait a bit and try connecting again.

If you have issues running the containers a second time after you've closed them off, run `docker-compose rm` before trying again.

## FAQ

> Wait.. can't I just attach to the running container and cheat?

Yes, you can. Don't do that. It's lame, it's against the spirit of this release, and you won't learn as much. Do it the proper way! You'll hopefully feel a bit of pain while figuring things out, but you'll learn something in the process.

> Can I produce a write-up for a challenge, or live-stream the process of completing it?

Yes, please do. Let us know when you publish/stream by hitting us up on [Twitter](https://twitter.com/bsidescbr).

> Can I reuse your challenge for my own CTF?

You'll have to contact us to discuss this as we'd like to know the purpose of the CTF.