about summary refs log tree commit diff
path: root/README.md
blob: c14ba2124f4caa15334252551b786b83d724fe45 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
# ctfdget

Ever started playing a ctf hosted using CTFd that felt like the requests were
processed manually by a goat? Not being able to access the challenges, but
being able to access the api? Just wanting to download all challenges at once
for not having to deal with CTFd until you want to submit your flags?

Here it is: ctfdget, a simple tool for fetching all challenges with their
included files.

## Building 

```
go build ./...
```

## Usage

```
./ctfdget --help                                                                                                                                                                                                                                                                                                                                             [±master ●]
Usage of ./ctfdget:
  -out string
    	The name of the folder to dump the files to (default "challdump")
  -session string
    	The session (the value of the cookie named 'session') (default "9e8831af-ce30-48c3-8663-4b27262f43f1.pjKPVCYufDhuA9GPJAlc_xh45M8")
  -url string
		The root URL of the CTFd instance (default "https://ctf.example.com")
```

## Features

- Dump all files from all challenges
- A simple directory structure get's created sorting the challenges into the corresponding categories (<ctfname>/<category>/<challengename>/<challengefiles>)

## Contribution

Just open issues, pull requests or whatever and we'll work something out