COMPETITIONS






R2 Architectures Support


Rules

Hints

For all newly written code the license should be LGPL, there should not be GPL code included, only compatible licenses allowing linking radare2 as a library.

Every newly implemented architecture should be covered with regression tests

Every improved architecture should support ESIL uplifting

Every pull request should be merged or constantly updated based on the feedback from radare2 developers.

Special prizes apply only to people who will implement specified architecture (or improve it).

Only issues marked with "r2con-hwcomp" label qualify for the competition.

For the first category it should be issue with label "New Architecture" correspondingly.

First category - Implementing new architecture

  1. Special prize - Simatic PLC (for Simatic architecture support)

  2. First place - ARM AliOS devkit

  3. Second place - RISC-V board

  4. Third place - C-SKY board (2-3 boards)

Second category - Improving architecture support

  1. Special prize - Intel TinyTILE ARC board (for ARC architecture)

  2. First place - RISC-V board

  3. Second place - C-SKY board (2-3 boards)

  4. Third place - Xtensa board (2 boards for each)

Description of the competition

Idea is to improve the support of particular architectures, or add a missing ones.

  1. Xtensa (10 cheap ESP8266 boards) #Missing ESIL #8484

  2. C-SKY (5 C-SKY OrangePi boards) #Motorola MCORE

  3. RISC-V (2 HiFive1 boards) #RISC-V assembler

  4. ARM (1 AliOS development kit board) ARM issues

  5. ARC (2 Intel tinyTILE boards) #ARC platform

  6. Simatic S7 (1 expensive S7-200 PLC board + JTAG) - no support at all currently

Additional hardware

  1. JTAG
  2. FTDI serials
  3. Wires
  4. USB cables
  5. MicroSD cards + readers

R2Crackmes


The R2Con CTF is a Jeopardy style competition. It has a couple of questions/tasks in range of different categories of RE. Player can gain some points for every solved task. Some challenges could have Hints, but there is a score penalty for using them.

Rules

  1. FEEL RADARE2 IN YOUR BONES
    It is required to use radare2 to solve the challenges. Some of them could only be solved using Radare ;)
  2. COOPERATION
    No cooperation between players is allowed. Sharing of keys or providing or revealing hints to other players is cheating, don’t do it.
  3. ATTACKING SCOREBOARD
    No attacking against the competition infrastructure is allowed. If bugs or vulns are found, please alert the competition organizers immediately.
  4. SABOTAGE
    Absolutely no sabotaging of other competing players, or in any way hindering their independent progress.
  5. BRUTEFORCING
    No brute forcing of challenge flag/keys against the scoring site.
  6. DENIAL OF SERVICE
    DoSing the CTF platform or any of the challenges is forbidden.
  7. PHYSICAL VIOLENCE
    Under no circumstances this should be used to solve the challenge.
  8. THE FIRST RULE OF R2CLUB
    You do not talk about R2CLUB

R2WARS


r2wars is a game similar to corewars, where 2 programs run on a shared memory space trying to catch each other in order to trash their code and make them crash.

This game was initially developed by pancake as a PoC in here and we have here the new version repository.

You can find here an explanation of the game in the first competition that happened during the 2nd r2con in 2017.

Rules

  1. X86 and ARM warriors support
    No mixed arena. x86 play vs all x86 warriors and ARM play vs all ARM warriors
  2. X86 rep prefix will be fixed to only allow 1 step for cycle
    No one shoot kill :)





Previous years [2017] [2016] | No rights reversed | Website done by @megabeets_ and @trufae.