-
Notifications
You must be signed in to change notification settings - Fork 0
/
info.yml
108 lines (78 loc) · 3.55 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
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
# Base service info for the scoreboard ########################################
service_name: "rad"
description: |
> The undiscovered country from whose bourn
> No traveler returns, puzzles the will
> And makes us rather bear those ills we have
> Than fly to others that we know not of?
> Thus conscience does make cowards of us all,
> And thus the native hue of resolution
> Is sicklied o'er with the pale cast of thought,
> And enterprises of great pith and moment
> With this regard their bits turn awry,
> And lose the name of action.
Use our cutting-edge graphical client to observe science in action!
Your team token is the value of your `dc29_access_token` in your browser's
local storage for https://scoreboard.ooo.
tags:
- pwn
- reversing
- --special-emoji-🛰️
- --special-lat-45
- --special-lon-24
authors:
- nullptr
# Flag info
violates_flag_format: false # if this is not "true", the flag is verfied against the flag format
flag: "OOO{tho.gh_t.is.be_m.dness_ye..t.er...s_m.th.d..n.it?}" # change it!
copy_flag_using_build_arg: True # Optionally: pass in THE_FLAG=(the flag above) using --build-arg (allows variable flags if desired for testing)
# 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.
# See the tester global constants for the default values.
game_network_info:
host: 165.22.0.163
port: 1337
# In quals this can only be 'jeopardy' (or `normal`, with the same meaning)
type: jeopardy
# Build and testing info ######################################################
# 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:
- service/public/rad_client
- service/public/rad_fw
# 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:
- /check.sh
# It's strongly suggested to have a healthcheck regex
# The infrastructure will periodically connect and alert if it doesn't match anymore
# The tester will also simulate this process (once).
#
# Example: healthcheck_tcp: awesome chall
# healthcheck_tcp_send: some intial command
# Example: healthcheck_http: Author Login
#healthcheck_tcp: awesome chall
# Resources ###################################################################
# This is the number of concurrent connections that a container should be able to handle.
# Also see xinetd's instances parameter
concurrent_connections: 64
# 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: 5
# Analogous to limit_memory / request_memory
# limit_cpu / request_cpu
# Transparent Proof-Of-Work if necessary
# pow: True
# pow_level: 22
# max_pids_per_instance: 200 # Protects against fork-bombs that take down the k8s node