-
Notifications
You must be signed in to change notification settings - Fork 0
/
info.yml
90 lines (60 loc) · 2.48 KB
/
info.yml
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
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
# Info for the schoreboard
service_name: "segnalooo"
description: "x86 assembly is crazy. I hope this challenge will help you understand it a bit better."
violates_flag_format: false # if this is not "true", the flag is verfied against the flag format
flag: "OOO{s3riously,wh4tISsigaltstack???}" # this is the flag of the service
allow_egress: False
tags:
- pwn
- --special-emoji-🤌
- --special-lat-37
- --special-lon-25
# Type can be normal or king_of_the_hill
type: normal
# This is the number of concurrent connections that a container should be able to handle.
# This will be tested by the test script
authors:
- anton00b
# These are the files that will be "public" to the teams via the scoreboard.
# The paths are relative to the repository
# They are published manually. IF YOU CHANGE THEM DURING THE GAME YELL!
public_files:
- stub
# Test scripts are heavily encouraged.
# All scripts should exit 0 if nothing went wrong.
# Scripts are automatically determined to be exploit scripts if they start with the word "exploit".
# Exploit scripts must output the flag using "FLAG: <FLAG>" and exit with 0 if the flag was captured correctly.
# The paths are absolute in the `interaction` docker container.
interactions:
- /test1.sh
- /test2.sh
- /test3.sh
- /test4.sh
- /exploit.sh
# This is how players will connect to your service
# REMOVE THIS IF YOUR SERVICE HAS NO NETWORK COMPONENT
# In the rare case that 'default' and 'guess' are not OK, you can specify your own values
game_network_info:
host: default
port: guess
healthcheck_tcp: Give me some code!
# Resources ###################################################################
# This is the number of concurrent connections that a container should be able to handle.
# Also see xinetd's instances parameter
concurrent_connections: 4
# Resource limits that will go in k8s
# request_xxx is used for scheduling (overcommitting)
# These should mesh with the xinetd's rlimit_as and number of concurrent instances
request_memory: 512m
limit_memory: 512m
# Not supported by the tester, but used by the infrastructure #################
# Spawn N containers behind the load balancer
# replicas * instances should allow everyone to play
replicas: 20
# Analogous to limit_memory / request_memory
# limit_cpu / request_cpu
# Transparent Proof-Of-Work if necessary
#we may need it later, not for nows
#pow: True
#pow_level: 23
# max_pids_per_instance: 200 # Protects against fork-bombs that take down the k8s node