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 search within and recover data from hard-disks. Since then, the project has grown with the new aim of providing 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, and keep it simple. Radare2 is a complete LGPL rewrite of the original project to remove design issues of the first iteration, and to make it more modular and easier to script and maintain. Radare2 features a testsuite that aims to cover as many cases as possible in order to catch regressions.
Radare2 is composed of an hexadecimal editor as central point, with several assemblers/disassemblers, code analysis capabilities, scripting features, visualization of code and data through graphs and other means, a visual mode, easy unix integration, a diff engine, a shellcode compiler, and much more.
This year Summer of Code was generously sponsored by NowSecure and KeenLab of Tencent.
Starting from 2014, we hosted our own version of Radare Summer of Code (RSoC). These were some of the successful projects:
More information can be found on the RSoC page.
Each year since 2015, we have participated in Google Summer of Code and accomplished many important tasks:
If you have questions or comments, visit our IRC channel #radare on Freenode.
Members of radare2 core team have volunteered to guide students for RSoC’19. They were already guiding the students for previos GSoCs and RSoCs. Please feel free to reach out to any of them in case you need any help in selecting a project.
Currently, all repositories are hosted on GitHub main organization and community accounts, bugs are tracked on GitHub issues too. We are mostly using HackMD, IRC, and Telegram (telegram#radare) for communication. We have a testsuite (that is running on Travis CI, AppVeyor and our Jenkins instance) to test and verify that all the features are still working and that a pull requests or commits don't break anything, and to find regressions. We encourage contributors to write test cases and documentation in order to verify the implementation and ensure that everything fits well together. There is also a Coverity instance to catch obvious defects. For complex bugs and examples we're using our own asciinema
See also our Contributing Guide and Developers Intro.
For those who want to get introduced to the radare2 codebase and practices, we recommend to pick one of the easy issues to start with.
Radare2 is modular: this means that it aims to make all the elements and features easily reusable from other projects. The choice of LGPL3 as a license is the minimum requirement to get code merged in r2. Contributors can choose Apache, BSD, MIT, Public Domain, or other similar licenses. The reason to exclude GPL as a valid license for the project is because we aim to support proprietary software that uses r2, while protecting our free codebase.
It is a requirement that students who want to apply to the radare2 project for the Radare Summer of Code 2019 should submit a small pull request accomplishing one of the microtasks as part of their application. Though you can also choose any of the GitHub issues for radare2 if they are big enough to be a qualification task, and still small enough to be finished no more than in a couple of weeks.^
Most of radare2 is written in C and hence we expect students to be familiar with C programming language. For some of our tasks or microtasks, such as collaborative RE, students should know the Go programming language.^