Reverse Engineering

Applied Cryptography Robust Software Quantum Safety Machine Learning Applied to Security Analysis and Exploration of Vulnerabilities Computer Systems Forensic Analysis Reverse Engineering Identification, Authentication and Authorization Secure Execution Environments Direito da Organização e da Segurança

Reverse Engineering
Introduction to Reverse Engineering
Files and Filetypes
Android – Static Analysis
Android – Dynamic Analysis
Binary Analysis
Emulation and Instrumentation
Obfuscation Techniques
Serial Communication
A interface RS-232C
Norma SPI
Norma I2C

Powered by GitBook

On this page

Typical Prologue with Stack Guard
Typical Epilogue with Stack Guard

Function detection

PreviousBinary Analysis Process NextCalling Conventions

Last updated 7 months ago

Functions frequently include known prolog and epilogues.

Prolog: set up the stack and optionally set up Stack Guard Canaries.
Epilog: optionally check the canaries and release stack.

This information may be used to determine function boundaries.

But it is architecture and compiler-dependent.

Alternatives:

Pattern matching (automatic, done by disassemblers) can also recover functions.
Exception handling code in the .eh_frame section.
gcc intrinsics to cleanup stacks with exceptions __attribute__((__cleanup__(f))) and __builtin_return_address(n).

Typical Prologue with Stack Guard

Typical Epilogue with Stack Guard