Skip to content

UNIX-like reverse engineering framework and command-line toolset

License

Notifications You must be signed in to change notification settings

rlaemmert/radare2

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

 ____  ___  ___  ___ ____  ___   ____
|  _ \/   \|   \/   \  _ \/ _ \ (__  \
|    (  -  | |  ) -  |   (   _/ /  __/
|__\__|_|__|___/__|__|_\__|___| |____|

             https://www.radare.org

                             --pancake
Build&Test Tests Status CII Best Practices
CodeQuality Build Status Total alerts
Packaging status

Introduction

r2 is a rewrite from scratch of radare in order to provide a set of libraries and tools to work with binary files.

Radare project started as a forensics tool, a scriptable command-line hexadecimal editor able to open disk files, but later added support for analyzing binaries, disassembling code, debugging programs, attaching to remote gdb servers...

Scripting

It is possible to script and extend r2 using native plugins written in C. Dynamic programming languages can be also used via the r2pipe interface or using the rlang r2pm packages which make the pythonvm run inside radare2.

Some of the languages supported by r2 are: Python, Ruby, JavaScript, Lua, Perl, PHP, Go, Rust, Swift, C#, Java, Shell, OCaml, Haskell, Scheme (Guile), Common Lisp, Clojure, Erlang, D, Vala/Genie, Prolog, Nim, Newlisp...

Documentation

To learn more about r2 we encourage you to watch youtube talks from r2con. As well as reading blogposts, slides or read the official radare2 book, You can reach us in the following chats:

Operating Systems

Windows (since XP), GNU/Linux, GNU/Darwin, GNU/Hurd, Apple's {Mac,i,iPad,watch}OS, [Dragonfly|Net|Free|Open]BSD, Android, QNX, Solaris, Haiku, FirefoxOS.

Architectures

i386, x86-64, ARM, MIPS, PowerPC, SPARC, RISC-V, SH, m68k, m680x, AVR, XAP, System Z, XCore, CR16, HPPA, ARC, Blackfin, Z80, H8/300, V810, V850, CRIS, XAP, PIC, LM32, 8051, 6502, i4004, i8080, Propeller, Tricore, CHIP-8, LH5801, T8200, GameBoy, SNES, SPC700, MSP430, Xtensa, NIOS II, Java, Dalvik, WebAssembly, MSIL, EBC, TMS320 (c54x, c55x, c55+, c66), Hexagon, Brainfuck, Malbolge, whitespace, DCPU16, LANAI, MCORE, mcs96, RSP, SuperH-4, VAX, AMD Am29000.

File Formats

ELF, Mach-O, Fatmach-O, PE, PE+, MZ, COFF, OMF, TE, XBE, BIOS/UEFI, Dyldcache, DEX, ART, CGC, Java class, Android boot image, Plan9 executable, ZIMG, MBN/SBL bootloader, ELF coredump, MDMP (Windows minidump), WASM (WebAssembly binary), Commodore VICE emulator, QNX, Game Boy (Advance), Nintendo DS ROMs and Nintendo 3DS FIRMs, various filesystems.

Install / Update

The recommended way to install or update radare2 from git for single-user systems:

$ sys/install.sh

If you don't have root, or just want to install it in your home use:

$ sys/user.sh

Note that those scripts will install using configure+make using symlinks, so you don't need to reinstall every time you change something in the builddir.

  • If you don't like symlinks use sys/install.sh --install
  • To use capstone5 use the --with-capstone5 flag.

Alternatively you can also build with meson + ninja:

$ sys/meson.py --prefix=/usr --shared --install

Or install in your home with meson + ninja:

$ sys/meson.py --prefix=$HOME/r2meson --local --shared --install

Uninstall

In case of a polluted filesystem, you can uninstall the current version or remove all previous installations:

$ make uninstall
$ make purge

To remove all stuff including libraries, use

$ make system-purge

Package Manager

Radare2 has its own package manager - r2pm. Its packages repository is on GitHub too. To start to using it for the first time, you need to initialize packages:

$ r2pm init

Refresh the packages database before installing any package:

$ r2pm update

To install a package, use the following command:

$ r2pm install [package name]

Development

Coding Style

Look at CONTRIBUTING.md.

Tests

Running make tests will fetch the test binaries repository and run all the tests in order to verify that no changes break any functionality.

We run those tests on every commit, and they are also executed with ASAN and valgrind on different platforms to catch other unwanted 'features'.

About

UNIX-like reverse engineering framework and command-line toolset

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 96.5%
  • C++ 1.0%
  • Makefile 0.9%
  • Shell 0.5%
  • Meson 0.4%
  • HTML 0.2%
  • Other 0.5%