Diff: 06-Competition.md
old (d2b87496399c)→new (836dcecb516a)
06-Competition.md
CHANGED
|
@@ -77,7 +77,7 @@ Day 3 of ECSC 2026 (Wednesday, October 14, 2026) is **not** part of the main com
|
|
|
77
77
|
|
|
78
78
|
### 6.3.1: CTF-Unplugged
|
|
79
79
|
|
|
80
|
-
CTF Unplugged will be a multi-round competition. Teams will compete to solve challenges the fastest, in an offline environment on organiser provided laptops. This event does not influence the final winners of ECSC, but will instead have
|
|
80
|
+
CTF Unplugged will be a multi-round competition. Teams will compete to solve challenges the fastest, in an offline environment on organiser provided laptops. This event does not influence the final winners of ECSC, but will instead have its own scoreboard and own mention at the awards ceremony. This competition will focus on the ability to solve complex cybersecurity related challenges in a constrained environment, under time pressure.
|
|
81
81
|
|
|
82
82
|
Note: This is the first time this format is being run, rules are subject to clarification or change in the coming weeks. Some exact numbers are still under discussion based on venue constraints and similar, and will be clarified closer to the event.
|
|
83
83
|
|
|
@@ -88,12 +88,19 @@ Note: This is the first time this format is being run, rules are subject to clar
|
|
|
88
88
|
* Teams will receive points based on how quickly they solve challenges.
|
|
89
89
|
* A top cut of teams from the four qualifying rounds will compete in the Semi-Final, and the top overall teams after the Semi-Final will compete in the Final.
|
|
90
90
|
* The final placements will be determined solely by performance in the final.
|
|
91
|
+
* Teams can send different Players each round
|
|
92
|
+
|
|
93
|
+
\
|
|
94
|
+
|
|
95
|
+
The provided laptops are Lenovo ThinkPad T490s with an Intel Core i7-8565U processor, 24 GB RAM and German QWERTZ keyboards. Players who prefer a different layout should bring their own USB keyboard. We also recommend bringing a USB mouse.
|
|
96
|
+
|
|
97
|
+
Challenges, handouts and flag submissions will be available through a local CTFd instance.
|
|
91
98
|
|
|
92
99
|
### 6.3.2 Qualifying rounds
|
|
93
100
|
|
|
94
101
|
There will be 4 qualifying rounds, one for each of Reversing, Pwn, Crypto and Web.
|
|
95
102
|
|
|
96
|
-
* All ECSC and Guest teams may participate, (up to
|
|
103
|
+
* All ECSC and Guest teams may participate, (up to 42 teams.)
|
|
97
104
|
* Each team may select up to two members to collaborate in each round
|
|
98
105
|
* Each team will have access to one shared laptop
|
|
99
106
|
* A round is planned to last \~50 minutes.
|
|
@@ -105,16 +112,22 @@ There will be 4 qualifying rounds, one for each of Reversing, Pwn, Crypto and We
|
|
|
105
112
|
|
|
106
113
|
Based on the scores from the four qualifying rounds, a top cut of teams will qualify onwards to the Semi Final
|
|
107
114
|
|
|
108
|
-
* Top
|
|
115
|
+
* Top 8 teams by points after the four qualifying rounds may participate in the semi final
|
|
109
116
|
* The semi final is expected to last \~50 minutes
|
|
110
117
|
* Teams will have access to four laptops to share
|
|
111
|
-
* Teams may each send up to
|
|
118
|
+
* Teams may each send up to 6 players to compete
|
|
112
119
|
* There will be multiple challenges across a range of categories.
|
|
113
120
|
* Teams will be scored based on challenges solved and time-to-solve
|
|
114
121
|
|
|
115
122
|
### 6.3.4 Finals
|
|
116
123
|
|
|
117
|
-
Based on overall scores from qualifiers combined with Semi Finals (with higher weighting to semi-final scores), the top
|
|
124
|
+
Based on overall scores from qualifiers combined with Semi Finals (with higher weighting to semi-final scores), the top 3 teams will qualify for the final.
|
|
125
|
+
|
|
126
|
+
* The final is expected to last \~50 minutes
|
|
127
|
+
* Each team will have access to four laptops to share
|
|
128
|
+
* Teams may each send up to 6 players to compete
|
|
129
|
+
* There will be multiple challenges across a range of categories.
|
|
130
|
+
* The final placements will be determined solely by performance in the final.
|
|
118
131
|
|
|
119
132
|
## 6.4. Day 4: Attack-Defense
|
|
120
133
|
|
|
@@ -373,4 +386,121 @@ All screen recordings will be kept onsite and will not be uploaded anywhere.
|
|
|
373
386
|
|
|
374
387
|
Any screen recordings handed over by the player will only be stored temporarily on dedicated storage media and will only be watched on a dedicated system. After the competition, both the disks of the dedicated system and the storage media will be securely wiped.
|
|
375
388
|
|
|
376
|
-
The screen recording measures are mandatory. Participation without recording all used screens will not be permitted.
|
|
389
|
+
The screen recording measures are mandatory. Participation without recording all used screens will not be permitted.
|
|
390
|
+
|
|
391
|
+
## 6.13. Screen Recording Setup
|
|
392
|
+
|
|
393
|
+
### Minimum Requirements
|
|
394
|
+
|
|
395
|
+
What we want at minimum:
|
|
396
|
+
|
|
397
|
+
* 1 fps
|
|
398
|
+
* Output resolution should match screen resolutions
|
|
399
|
+
* All screens in one video file
|
|
400
|
+
* Record mouse cursor
|
|
401
|
+
* Encoding: H.264, minimum keyframe every 5 seconds
|
|
402
|
+
* Frames should only depend on earlier frames
|
|
403
|
+
* Disable buffering
|
|
404
|
+
* Use high-quality encoding settings (CRF 16 for x264)
|
|
405
|
+
|
|
406
|
+
### How to Do It with OBS
|
|
407
|
+
|
|
408
|
+
Open OBS and cancel the setup wizard.
|
|
409
|
+
|
|
410
|
+
**Settings → Video**
|
|
411
|
+
|
|
412
|
+
* Set **Base** and **Output** resolution to your screen resolution (in this example, 1920×1080).
|
|
413
|
+
* Select **Integer FPS Value** and enter `1`.
|
|
414
|
+
|
|
415
|
+
**Settings → Audio**
|
|
416
|
+
|
|
417
|
+
* Disable all **Global Audio Devices**.
|
|
418
|
+
|
|
419
|
+
**Settings → Output → Advanced → Recording**
|
|
420
|
+
|
|
421
|
+
* **Type:** Custom Output (FFmpeg)
|
|
422
|
+
* **Output Type:** Output to File
|
|
423
|
+
* **Save location:** `Desktop/OBS Recordings`
|
|
424
|
+
* **Container:** matroska (MKV)
|
|
425
|
+
* **Video Encoder:** libx264
|
|
426
|
+
* **Rescale Output:** unchecked
|
|
427
|
+
* **Keyframe interval:** 5 frames
|
|
428
|
+
* **Audio Tracks:** uncheck all
|
|
429
|
+
* **Audio Encoder:** Disable Encoder
|
|
430
|
+
|
|
431
|
+
Paste into **Video Encoder Settings**:
|
|
432
|
+
|
|
433
|
+
```
|
|
434
|
+
crf=16 preset=medium profile=high threads=1 x264-params=scenecut=40:bframes=0:rc-lookahead=0:sync-lookahead=0
|
|
435
|
+
```
|
|
436
|
+
|
|
437
|
+
**Settings → Advanced → Recording**
|
|
438
|
+
|
|
439
|
+
* Set **File Name Formatting** to:
|
|
440
|
+
|
|
441
|
+
```
|
|
442
|
+
ECSC2026_%CCYY-%MM-%DD_%hh-%mm-%ss
|
|
443
|
+
```
|
|
444
|
+
|
|
445
|
+
**Add a Capture Source**
|
|
446
|
+
|
|
447
|
+
Add a capture source, select your monitor, and enable cursor capture:
|
|
448
|
+
|
|
449
|
+
* **Ubuntu Xorg:** Screen Capture (XSHM)
|
|
450
|
+
* **Ubuntu Wayland:** Screen Capture (PipeWire)
|
|
451
|
+
* **Windows:** Display Capture, using DXGI Desktop Duplication
|
|
452
|
+
* **macOS:** macOS Screen Capture; grant permission if prompted.
|
|
453
|
+
|
|
454
|
+
**Two Monitors**
|
|
455
|
+
|
|
456
|
+
For two monitors, arrange them in the OS display settings and add one source per monitor. Set **Base** and **Output** resolution to their combined size. For two 1920×1080 monitors side by side:
|
|
457
|
+
|
|
458
|
+
* **Canvas/output:** 3840×1080
|
|
459
|
+
* **Left source:** X=0, Y=0
|
|
460
|
+
* **Right source:** X=1920, Y=0
|
|
461
|
+
* Keep native sizes, Top Left alignment, No bounds, and cursor capture enabled on both.
|
|
462
|
+
|
|
463
|
+
**Start Recording**
|
|
464
|
+
|
|
465
|
+
Apply the settings, check the preview, then click **Start Recording**. Click **Stop Recording** when finished.
|
|
466
|
+
|
|
467
|
+
|
|
468
|
+
**Windows**
|
|
469
|
+
|
|
470
|
+
[windows.mp4 1920x1080](uploads/f57a2b0a-5149-4dbb-b4fc-31e4bd445020.mp4)
|
|
471
|
+
|
|
472
|
+
**macOS**
|
|
473
|
+
|
|
474
|
+
[macos26.mp4 1920x1080](uploads/8a3d404f-a4f3-4ed8-8c07-86594684b4ee.mp4)
|
|
475
|
+
|
|
476
|
+
**Ubuntu Wayland**
|
|
477
|
+
|
|
478
|
+
[ubuntu-wayland.mp4 1920x1080](uploads/36aad4de-276e-43c7-89ce-51c2e0c2e472.mp4)
|
|
479
|
+
|
|
480
|
+
**Ubuntu Xorg**
|
|
481
|
+
|
|
482
|
+
[ubuntu-xorg.mp4 1920x1080](uploads/409e4338-3732-4fd4-a488-49151b15318a.mp4)
|
|
483
|
+
|
|
484
|
+
**Ubuntu Two Monitors**
|
|
485
|
+
|
|
486
|
+
[ubuntu-two-monitors.mp4 1920x1080](uploads/0b9f4869-afc2-484d-a131-2b09a2aa3bbb.mp4)
|
|
487
|
+
|
|
488
|
+
### Your Responsibilities
|
|
489
|
+
|
|
490
|
+
You are responsible for making sure your recording works as expected. Therefore, please test this setup before the competition by recording your screen for a while and then rewinding through the recording. Also make sure that you have enough disk space to record the full A/D and Jeopardy competition. We expect about 1 GB/h with the example setup described above; however, it is crucial that you check this with your own settings and resolution to be sure that your disk space is sufficient.
|
|
491
|
+
|
|
492
|
+
**Alternative Setups**
|
|
493
|
+
|
|
494
|
+
If you are worried about RAM usage or have a "cursed-arch" setup, you are responsible for getting some form of screen recording working that meets these requirements. You don't have to use OBS.
|
|
495
|
+
|
|
496
|
+
You can also try piping libdrmtap into FFmpeg; that should work. You could also wire it up as a systemd service. Ideally, we would use FFmpeg with kmsgrab, but it doesn't support recording the mouse cursor.
|
|
497
|
+
|
|
498
|
+
### Frequently Asked Questions
|
|
499
|
+
|
|
500
|
+
We anticipate that people will have some questions about the screen recordings, so we want to provide some answers here:
|
|
501
|
+
|
|
502
|
+
**System crash or reboot:** If your system crashes, or you need to reboot your system, please start the recording again afterwards. To document this, please create a short ticket describing what happened and noting that there will be a short gap in your recording. There is no need to wait for an answer to the ticket.
|
|
503
|
+
|
|
504
|
+
**Corrupted or missing recordings:** If you notice that your screen recordings are corrupted or missing, please start recording your screen and open a ticket to explain the situation. This ticket will then be forwarded to the jury for review. There is no need to wait for an answer to the ticket.
|
|
505
|
+
|
|
506
|
+
**Entering sensitive data:** If you need to enter sensitive data, such as credit card information, on your system, please inform a watchdog that you will pause the recording and why. The watchdog will note down the time when the recording was stopped and will stay in your vicinity to note down, when it was started again. Please keep this time span as short as possible.
|