https://github.com/zynamics/ida2sql-plugin-ida

https://github.com/zynamics/ida2sql-plugin-ida

Last synced: 3 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/zynamics/ida2sql-plugin-ida
• Owner: zynamics
• Archived: true
• Created: 2010-04-12T14:20:08.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2012-01-10T11:59:37.000Z (almost 13 years ago)
• Last Synced: 2024-03-25T23:02:41.966Z (8 months ago)
• Language: Python
• Homepage:
• Size: 285 KB
• Stars: 38
• Watchers: 8
• Forks: 14
• Open Issues: 0
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

README

        
zynamics IDA2SQL IDA Pro Plugin has moved to Google Code

========================================================

This repository has moved to Google Code:

http://code.google.com/p/zynamics/source/checkout?repo=ida2sql

Introduction:

----------------------

The module is distributed as two files:

 -ida2sql.py    (the file run from IDA, it imports

                the main part of the code in the ZIP file)

 -ida2sql.zip   (A zipped module implementing all the

                functionality, it's created by zipping the

                ida_to_sql directory)

                

License:

----------------------

ida2sql is licensed under the GPL 2 license. See gpl.txt for more information.

Installation:

-------------

Drop the ZIP file inside the IDA plugins directory. That's all. Just run the

ida2sql.py script from within IDA afterwards.

The configuration file:

-----------------------

If a file named "ida2sql.cfg" is placed in the IDA top level folder the

database information will be loaded from it. Allowing to quickly export

by just calling the "ida2sql.py" from within IDA.

See the example ida2sql.cfg file included.

Special features/Notes:

-----------------

If a file named "function_set.txt" exists in IDA's root directory (where

IDA's binaries reside) it will be loaded and only functions listed on it

will be exported. 

The file should contain the hexadecimal start address of the functions

that should be exported, one per line.

Note 1: if there are any imported symbols referred to from those functions,

those will also be exported.

Note 2: The exporter might display some errors towards the end of the export.

It will complain because not all the constraints of the database are fulfilled

as there might be references to functions that are not exported. Those errors

can be ignored.