Up to Speed

So, all of this sounds intimidating. Jailbreak, sign, secpack, unlock, baseband, iBoot, seczone, JailbreakMe, pwnage - there are lots of terms to learn, but most of them are defined here on the wiki. The basics:


 * Activation - to bypass the required iTunes signup.
 * Jailbreak - to allow full write and execute privileges on the iPhone, iPod touch, iPhone 3G, iPhone 3GS, iPhone 4, iPhone 4S, iPad and iPad2.
 * Unlock - to allow the use of any mobile phone carrier's SIM.

Think of iPhone as a little computer, even though Apple doesn't want you to. It has a processor, RAM, a "hard drive", an operating system, and a cellular modem on the serial port.

Ways to learn about how jailbreaks work

 * You can read about general exploitation techniques on Wikipedia, starting with software vulnerabilities and privilege escalation. Learning about types of vulnerabilities can be fun even if you don't have any background yet in programming or security research - it's like learning about how puzzles work. To learn more about security research in general (useful for the beginner), try these links: Getting Started in Information Security by /r/netsec, /r/netsecstudents resources, and Application Security and Vulnerability Analysis.


 * Read winocm's recommendations for how to get started with iOS hacking: learning ARM, understanding low-level parts of iOS, reading open source code in iOS and OS X, learning programming, learning about security/fuzzing, and then learning iOS-specific tools and tricks.


 * Read iOS Hacker's Handbook, published in May 2012: "The award-winning author team, experts in Mac and iOS security, examines the vulnerabilities and the internals of iOS to show how attacks can be mitigated. The book explains how the operating system works, its overall security architecture, and the security risks associated with it, as well as exploits, rootkits, and other payloads developed for it."


 * pod2g also recommends these books: Mac Hacker's Handbook, Mac OS X Internals: A Systems Approach, and A Guide to Kernel Exploitation: Attacking the Core. And here are even more that can be useful: Mac OS X and iOS Internals: To the Apple's Core, Hacking and Securing iOS Applications, OS X and iOS Kernel Programming, and Professional Cocoa Application Security.


 * Listen to the 25C3 presentation "Hacking the iPhone". This was in 2008, but it explains the basics in detail.


 * See the presentation "Strategic Analysis of the iOS Jailbreaking Development Community" by Dino Dai Zovi in November 2012.


 * i0n1c has given several presentations on iOS jailbreaking techniques, and there are PDFs of his slides available online, including: "iOS Kernel Exploitation", "iPhone Exploitation: One ROPe to bind them all?", and "iOS 5: An Exploitation Nightmare?". He has also recommended a couple of books: The Shellcoder's Handbook and The Art of Software Security Assessment. You may also find it interesting to read his outline for a workshop on developing kernel exploits - note the requirements (knowing ARM assembly, ROP, buffer overflows, integer overflows; having access to IDA Pro, Hexrays, BinDiff).


 * Check out this analysis of JailbreakMe 3.0 (Saffron).


 * If you're interested in baseband hacking and unofficial software unlocks, there are slides from a presentation by MuscleNerd: "Evolution of the iPhone Baseband and Unlocks" (PDF).


 * Members of the team that built Corona for iOS 5.0.1 gave presentations about it, and there are PDFs of their slides available here: Corona for A4 and Corona/Absinthe for A5.


 * Here's some analysis of evasi0n from Accuvant Labs and from Azimuth Security, along with a high-level explanation from planetbeing. The evad3rs team gave a presentation about evasi0n with slides available.


 * Study the available open source jailbreaking tools.


 * Read fuzzing for some explanation of how that technique has been used on iOS, and read how to reverse for some inspiration.


 * If you want to really get started, learn assembler for ARM processors. Open Security Training has "Introduction to ARM" materials, for example.

Now

 * Read the timeline.
 * Read the unsolved problems page to see where you can help.