Robin Vossen wrote:
Hello,
I am wondering..
Will most of the functions from LordPE be in Radare2? Eg the Section
Enlarger?
I would like to see that since I am planning of slimming down my
toolchain. :)
Section resizer is already implemented in r1 and r2 for ELF.
Nibble has been working on the refactoring of r_bin library for elf and
pe and
managed to remove about 700LOC and keeping the functionality. But the new
api has not been tested, and needs some more work to refactor the resizing
stuff that has changed.
The new r_bin api allows to read binary structures from any backend
supported
by r_io. this is local files, mapped files, process memory, remote
files, sockets, etc..
For this reason we need to work a bit more on the r_io library to
properly support
the resizing for non-files (like allocating memory on child processes,
etc..).
The plans for r_bin are to split the reading and writing functionalities
for binary
formats in two separate layers (we already decided to break the API as much
as possible to do it well) so no plans for backporting to r1 at this point.
The writting api will allow to add/remove/resize sections,symbols,
imports, libraries,
etc. in a simple and portable way between file formats and architectures.
The main reason why this is not yet done is because the lack of free time :)
The need to split all the writting stuff in a separate module is because
the bin
library will need more information from external sources to properly
reallocate
sections and symbols, this is, the r_anal (code analysis module), and so on.
If you look at rabin -o help you will get something like:
$ rabin -o help
Operation string:
-o r/.text/1024
-o d/s/10
-o d/S/.text
These operations are:
'r' : resize section
'd/s' : dump symbol
'd/S' : dump section
They are also implemented in rabin2.
Which other kind of features would you like to have in radare2 for binary
manipulation?
--pancake
_______________________________________________
radare mailing list
[email protected]
http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org