Today I told you that Pod2G has officially announced that he is looking for vulnerabilities to develop an untethered jailbreak solution for iOS 5.1. Also today Pod2G published on his blog an article describing the methods by which we can help him develop a new jailbreak solution because the help offered by several thousand/tens of thousands of users will speed up the process of discovering vulnerabilities. Pod2G needs crashes that occur while using native applications: Safari, Mail, YouTube, Maps, etc., but it is important that that crash can be repeated, so we must know how to reproduce it.
The crashes must be for iOS 5.1 because that way we would know for sure that they can be used by hackers. Perhaps the most important thing to know is that those crashes don't have to reach Apple, so you have to go in Settings / General / About / Diagnostics & Usage and choose the option Don't feel. If you discover crashes that can be repeated in one of the native iOS applications then you can send Pod2G an email at ios.pod2g@gmail.com with a description of your discovery. Finally, I recommend that you send him an email if you discover a crash that you can reproduce because you could contribute to the development of a new jailbreak solution.
- Always test on the latest iOS version before reporting a crash (at the time of writing, iOS 5.1)
- Be sure not to report crashes to Apple: on your iOS device, go to Settings / General / About / Diagnostics & Usage, and verify that "Don't Send" is checked.
- Not all crashes are interesting: aborts, timeouts or out-of-memory kind of crashes are useless. Verify the crash dump in Settings / General / About / Diagnostics & Usage / Diagnostic & Usage Data that the crash report you created is of Exception Type SIGILL, SIGBUS or SIGSEGV.
- The crash should be repeatable, which means you should know what exact steps produced it and how to reproduce it on another device.
