Skip to content

Commit 0b0be93

Browse files
authored
Update how_to_host_a_ctf.md
1 parent 2967f5f commit 0b0be93

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

main/content/post/how_to_host_a_ctf.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ For many challenges, especially for categories like rev, misc, and often crypto,
9292

9393
When hosting is required however, it will generally fall under one of 3 categories. The first is to simply put it into a single container for everyone to access. This works well when there's no (or very little) global state, and it's difficult to modify the challenge as a standard user, this is often the case for simpler web challenges and some scripting based challenges. The second is jailed challenges. In jailed challenges, individual TCP connections are given new instances of a jailed binary --- this is very common for pwn based challenges. The last is fully instanced challenges. This is most commonly seen in more complex web challenges, but is seen around in other places as well.
9494

95-
Note that this is non-exhaustive, but covers the vast majority of challanges. Notably one thing this doesn't cover is kernel pwn challenges, which require nested virtualization and some fairly complex infrastructure that I won't go into here.
95+
Note that this is non-exhaustive, but covers the vast majority of challanges. Notably one thing this doesn't cover is kernel pwn challenges, which require nested virtualization and some fairly complex infrastructure that I won't go into here (Update: Read my [write-up on kernel pwn infrastructure](https://www.emilymiller.xyz/post/how_to_host_a_ctf/)).
9696

9797
## Part 2.0: General container hosting
9898

0 commit comments

Comments
 (0)