Fri, 15 March 2019, 17:00 UTC — Sat, 16 March 2019, 01:00 UTC 


UCSB iCTF event.

Format: Attack-Defense Attack-Defense

Official URL:

This event's weight is subject of public voting!

Future weight: 11.50 

Rating weight: 35.45 

Event organizers 

This year's iCTF "Race Condition" is open to the public, again!

For registration and details, visit

Good luck, have fun, and get ready to race!

IMPORTANT: Registration closes on 3/15 1:00 UTC. No registrations will be accepted after this time.

r00t3r – Feb. 19, 2019, 11:19 a.m.

SecurisecCTF is looking for new members. Join us at

oran.majar – March 15, 2019, 5:13 p.m.

Is the CTF down?

cbmH@ck3r – March 15, 2019, 5:26 p.m.

is server down within 1min of start?? surprised!!

Jacky5112 – March 15, 2019, 5:43 p.m.


styx00 – March 15, 2019, 5:48 p.m.


R3D – March 15, 2019, 5:48 p.m.

gg ez..

Weide Hong – March 15, 2019, 5:58 p.m.

g1v3 m3 fl4g

Soaringnemesis – March 16, 2019, 3:54 a.m.

lol... I was hoping to have a good time.

Soaringnemesis – March 16, 2019, 3:55 a.m.

gg no re

Trolldemorted – March 19, 2019, 6:32 p.m.

Will the results be submitted before the vote ends?

Most of us can't vote before you do -.-

neex.emil – March 19, 2019, 10:53 p.m.

*A lot* of problems during the CTF this time.

1. This year, iCTF introduced jeopardy "cloud challenges", which were supposed to open access to AD services of other teams. Unfortunately, the check was buggy, and everyone could get access to all AD services without solving corresponding jeopardy task. This effectively reduced the number of challenges to 3. I do not think that the bug was intended because it was not possible to fix it from the teams' side.
2. Problems with the network: at some moments of the game, the game network was split into two segments, so some teams could not attack each other (this had a noticeable effect on the scoreboard during these periods). Not to mention the 20-minute interval when the game was stopped due to some scoring bugs and a 1-hour launch delay.
3. This one did not affect our team, but, according to the irc, orgas did not help to restart teams' VMs if the VM become irresponsive. Given the fact that VMs were hosted in the aws cloud and teams didn't have direct access to the them, that meant that a fork bomb was equal to game over. I can only imagine how frustrated these teams were.

Good parts:
1. The idea of scoring was interesting - there were no attack points at all, only defense <round-wise logical AND> SLA. This eliminates some of the well-known problems of traditional scoring (for example, attacking only teams that are far from the top).

I hope next year the organizers will test everything more thoroughly.