Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mobile App Reverse Engineering

You're reading from   Mobile App Reverse Engineering Get started with discovering, analyzing, and exploring the internals of Android and iOS apps

Arrow left icon
Product type Paperback
Published in May 2022
Publisher Packt
ISBN-13 9781801073394
Length 166 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Abhinav Mishra Abhinav Mishra
Author Profile Icon Abhinav Mishra
Abhinav Mishra
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Section 1: Basics of Mobile App Reverse Engineering, Common Tools and Techniques, and Setting up the Environment
2. Chapter 1: Basics of Reverse Engineering – Understanding the Structure of Mobile Apps FREE CHAPTER 3. Chapter 2: Setting Up a Mobile App Reverse Engineering Environment Using Modern Tools 4. Section 2: Mobile Application Reverse Engineering Methodology and Approach
5. Chapter 3: Reverse Engineering an Android Application 6. Chapter 4: Reverse Engineering an iOS Application 7. Chapter 5: Reverse Engineering an iOS Application (Developed Using Swift) 8. Section 3: Automating Some Parts of the Reverse Engineering Process
9. Chapter 6: Open Source and Commercial Reverse Engineering Tools 10. Chapter 7: Automating the Reverse Engineering Process 11. Chapter 8: Conclusion 12. Other Books You May Enjoy

Understanding the binary format

For systems that are based on the Mach Kernel, such as macOS and iOS, Mach-O is the format that's used for the executable files and shared libraries. Mach-O stands for Mach object file format. The applications are expected to run on different processor types, for the most part. Owing to this, the executable code should be native to different instruction sets.

Depending on the instruction sets it contains, a binary file is called a thin binary if it contains a single executable file for one architecture; it's called a fat binary if it contains code for different CPU instruction sets in a single file – that is, it has been fattened (or expanded).

Each binary file begins with a header (called a mach header) that contains a magic number that can be used to identify it. For a thin binary file, the header contains one magic number; however, for a fat binary, the header is a fat header. The fat header contains the locations of the mach...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime