Yeah. maybe the easier binding i have ever do. Please take a look on the source. I think is quite easy to understand and make you how a language binding works in radare.
http://radare.nopcode.org/hg/radare?raw-file/094b21456655/src/plug/hack/ruby.c And the python binding file: http://radare.nopcode.org/hg/radare?file/094b21456655/src/plug/hack/radare.py i'll probably write a template for translating the API to lua/perl/ruby and python in a shot. It is now possible to import the metasploit framework inside radare and use it from there to reencode assembly from memory or stuff like that.. some examples will be probably provided..but contribs are welcome (R)...so doing all this shit alone is funny but sad. (GRRR(R)) btw current hg version fixes the build with acr/make and more documentation added to the book (actually 65 pages)... Another big update is done with 'af' the analyze-function command which now processes the information of the stackop field of arch_aop, adding metadata to the function itself like analyzing the number of local variables in stack, the arguments accessed, size of function by basic block analysis of the source and much more ;) The disassembly is pretty printed with /|\ marks: http://radare.nopcode.org/img/fundbg.png btw rabin -rs is now exporting the function size properly, so it can be easily used from radare to dump functions to raw files. for example: --- $ cat extract-uxor.radare .!rabin -rs $FILE bf sym_unpack s sym_unpack pr > uxorcode.section q $ radare -i extract.uxor.radare ./a.out --- enjoy++ --pancake _______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
