RuCTFE 2017 is over /
02 dec 2017

First place: Bushwhackers
Second place: Eat Sleep Pwn Repeat
Third place: c00kies@venice
Thank you for a good game!
Please, leave us feedback

Today is the 2nd of December. Today is RuCTFE /
02 dec 2017

You can download vulnerable image from our team's server or from torrent. Recommended system requirements for it is 4 CPUs, 4GB RAM, 4GB HDD.

From now registration is closed. The RuCTFE Cloud console and image's decryption key will be available at 10:00 UTC. The network will be opened at 11:00 UTC.

Have a nice day and a good game!

Network scheme, config files and RuCTFE Cloud instruction /
01 dec 2017

We sent configuration files to all teams (we apologize to some teams for letters with second recipient, we re-sent the new version which no one except for you have seen, please get info from the second letter, if you got both). If you haven't received the letter, you can request it again.

Also you can have a look at page and find out there everything about the network and learn how to use RuCTFE Cloud.

Developers asked us to tell about one more innovation: apart from the ordinary TCP flag submission system, now there is an alternative one, working through HTTP. Here is an example of usage.

Oh, also check out the legend :)

RuCTFE Cloud 2017 /
26 nov 2017

Q: What is RuCTFE Cloud?

A: Before now all RuCTFE participants had to deploy vulnerable image on their own servers and PCs. This year we thought that for some teams it might actually be a problem. That is why now you can deploy the image on our servers! No more pain with lingering ping, unstable internet, search for a server and its first setup. And, of course, it is convenient for geographically dispersed teams, which is more or less what our developers' team looks like :)

Q: But it's better to set everything up on your own server, and also it's not clear what the hardware will be. Is it still possible to take part in RuCTFE on your own server?

A: Certainly it is! We really support this idea :) But for those who don't have an opportunity (or desire) we try to create a comfortable interface for fast connection to game network and setup.

Q: But couldn't the teams with their own servers have advantages because of more powerful computers?

A: We provide the amount of computing powers enough for comfortable playing during 9 hours. At the same time, services are developed in a way that the difference in computing powers for teams could not crucially affect the final game results.

Q: How much will that cost?

A: Absolutely nothing!

Q: Are there any restrictions?

A: Unfortunately, yes. We can provide image hosting on RuCTFE Cloud only for 100 teams. First 100 teams which set the images up in our cloud will be playing on it, the others will have to use their own servers. Therefore, if you prefer your own server solutions, we ask you to not deploy an extra image in RuCTFE Cloud.

And, for sure, better not break the RuCTFE rules :)

Q: I do like that! What I need to do to deploy an image in RuCTFE Cloud?

A: Follow the news, soon there will be a detailed instruction.