SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 583 | Next

Shon Harris, Allen Harper, Chris Eagle, and Jonathan Ness

"Gray Hat Hacking, Second Edition"


4. Add the SDK include directory to your include directory path.
5. Link with the appropriate ida library (ida.lib, ida.a, or pro.a).
6. Make sure your plug-in is built with an appropriate extension (.plw for
Windows, .plx for Linux).
Once you have successfully built your plug-in, installation is simply a matter of copying
the compiled plug-in to IDA??™s plug-in directory. This is the directory within your IDA
program installation, not within your SDK installation. Any open databases must be
closed and reopened in order for IDA to scan for and load your plug-in. Each time a
database is opened in IDA, every plug-in in the plugins directory is loaded and its init
function executed. Only plug-ins whose init functions return PLUGIN_OK or PLUGIN_
KEEP (refer to loader.hpp) will be kept by IDA. Plug-ins that return PLUGIN_SKIP will
not be made available for current database.
The IDAPython Plug-In
The IDAPython plug-in by Gergely Erdelyi is an excellent example of extending the
power of IDA via a plug-in. The purpose of IDAPython is to make scripting both easier
and more powerful at the same time. The plug-in consists of two major components: an
IDA plug-in written in C++ that embeds a Python interpreter into the current IDA process,
and a set of Python APIs that provides all of the scripting capability of IDC.


Pages:
571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595