Jump to content
Tuts 4 You

Radare Summer of Code


Recommended Posts

The radare project started in February of 2006 aiming to provide a Free and simple command line interface for an hexadecimal editor supporting 64 bit offsets to make searches and recovering data from hard-disks.


Since then, the project has grown with the aim changed to provide a complete framework for analyzing binaries with some basic *NIX concepts in mind like everything is a file, small programs that interact together using stdin/out or keep it simple.




The project is composed of an hexadecimal editor as the central point of the project with assembler/disassembler, code analysis, scripting features, graphs of code and data, a visual mode, easy unix integration, ...

It also features a diff engine, a shellcode compiler, ...


Radare2 is a complete LGPL rewrite of the original radare, to remove design concerns of the first iteration. Radare2 already gained some contributors during the last years; and with the RSoC 2014, we are aiming to gain even more.




Prospective RSoC applicants should expand on the ideas and provide specific information in the application. If you have questions or comments, visit our IRC channel #radare on irc.freenode.net.



Summer of Code


As long as we didn't get into the Google Summer Of Code we decided to organize our own program in order to achieve the tasks we wanted to get done. You may find more information about those tasks below. The RSoC have nothing to do with Google.



In order to achieve the fundings required to reward the contributors we are organizing a crowdfunding campaign in various currencies: Radare Summer of Code crowdfunding page.




As long as we are not inside the GSoC program we decided to define our own rules, starting from the funding and payment methods.

  • Everyone can participate (not only students)
  • No personal information required (totally anonymous)
  • Multiple payment methods accepted (btc/doge/transfer/paypal)
  • We will send a pack of r2 t-shirt + stickers to each participant
  • Mentors will be rewarded too (not yet specified)
  • Reward depends on difficulty



We use the same GSoC schedules:

  • 22 April - participants application open
  • 3 May - participants application closes
  • 8 May - announce applicants/tasks - start discussing specific details of the task
  • 17 Jun - start coding
  • 16 Sep - Pencils down!
  • 27 Sep - Everything must be merged in main branch



Development methodology

Currently, all repositories are hosted on github, that is also our bugtracker. The mailling list is pretty low-traffic, since we are mostly using pads instead.

We have a testsuite (That is also running on our Jenkins instance.) to test and verify that all the features are still working and that a merge or a commit don't break anything. It also tracks the broken features/functionalities.


We encourage contributors to write test cases and write minimal documentation in order to verify the implementation and ensure everything fits well together.There is also a Coverity instance to catch obvious defects.



Feel free to check the RSoC page to see suggested tasks :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...