Design Phase Flags¶
During the Design Phase, teams can show that they are staying on track and earn some points by submitting Design Phase Flags. Teams will earn full points for submitting flags by the deadline. Flags submitted after the deadline will earn half points.
Milestone |
Flag Format |
Due Date |
Points |
Description |
|---|---|---|---|---|
Read Rules |
|
January 22 |
100 |
If you read all the rules, you’ll know |
Boot Reference Design |
|
January 24 |
100 |
Provision and boot the Reference Design to receive a flag |
Design Document |
|
January 31 |
100 |
Submit an initial design document containing high-level descriptions of how each host tool and system function will work. It should be clear from your descriptions how your system meets the Functional Requirements and Security Requirements. Your design may change after submitting this draft, but we recommend updating this as your design changes and including it in your final submission for documentation points. |
Debugger |
|
February 7 |
100 |
Show that you can use a debugger. More information about capturing this flag will be released soon. |
Testing Service |
|
February 14 |
100 |
Use the Testing Service and read the results. |
Attack the Reference Design |
See: Attack Phase Flags |
February 21 |
100 |
Capture flags by attacking a deployment of the Reference Design. More information about capturing these flags will be released soon. |
Final Design Submission |
|
April 16 |
1,000 |
Pass Handoff to earn points and enter the Attack Phase |
Bug Bounty |
April 16 |
Up to 200 |
See Bug Bounty below |
Bug Bounty¶
If your team happens to find a bug in the reference design, you can earn points for it! Your team will receive 100 points for each bug found, and another 100 points if you submit a corresponding fix. If multiple teams find the same bug, points will be distributed on a first come, first serve basis.
Sometimes whether an issue is truly a bug (or a feature!) is a matter of opinion - the eCTF organizers reserve the right to reject bug reports for trivial issues and combine multiple similar reported bugs into one. Submitted bugs will be accepted if there is a violation of the functional requirements in the reference design that prevents it from working correctly.
Submissions for typos or clarifications on documentation provided by the organizers will not be considered for additional points, although we appreciate being notified about these mistakes so we can make the appropriate edits and provide further explanation where it is necessary.
Please submit Bug Bounty requests through your private team channel on
Slack tagging @organizers.
