Developer documentation

Welcome to the developer documentation! This section serves as a reference for people willing to contribute to the project. First of all, thank you for wanting to make Manalyze better! During the course of this chapter, we will discuss considerations which should be taken into account before submitting code. Then we’ll look at how the code is organized and formatted in the project. Finally, we’ll look at the two ways this project can be extended: by writing a plugin to add analysis capabilities and by improving the core of the tool.

In this chapter, it is assumed that you have obtained a copy of the program’s source code and know how to build it. If it is not the case, please refer to the obtaining the tool page.

• Before contributing
  • About the GPLv3 license
  • Coding style
  • Getting Help
• How the code is organized
  • The root folder
  • The bin folder
  • The external folder
  • Source folders
  • Other folders
• Writing plugins
  • Internal and external plugins
  • A sample plugin
    • Internal plugin skeleton:
    • External plugin skeleton:
  • Plugin results
    • Threat level
    • Summary
    • Information
  • PE objects
    • DOS Header
    • PE Header
    • Optional Header
    • Sections
    • Imports
    • Exports
    • Resources
    • Debug Information
    • Thread Local Storage
    • Load Configuration
    • Delay Load Table
    • RICH Header
    • Miscellaneous
  • Section objects
    • Finding a section
    • Accessing the raw bytes
  • Resource objects
    • Accessing the underlying resource
    • Extracting resources
  • Using the configuration file
  • Anything missing?
• Writing Yara rules
  • Introduction
  • Supported commands
  • Sample rule
• Reusing the PE parser
  • Embedding the code
  • Reusing binaries
    • On Linux
    • On Windows