Replies

To my earlier point, here is an excerpt from Apple's iOS Security document. See pp 5, "Secure Boot Chain". Note that this is exactly the process I summarized in my earlier post, and which SwordMaker then said was not the way things worked with Apple devices (an assertion he apparently just pulled out of his nether regions).

When an iOS device is turned on, its application processor immediately executes code from read-only memory known as the Boot ROM. This immutable code, known as the hardware root of trust, is laid down during chip fabrication, and is implicitly trusted.
The Boot ROM code contains the Apple Root CA public key, which is used to verify that the Low-Level Bootloader (LLB) is signed by Apple before allowing it to load. This is the first step in the chain of trust where each step ensures that the next is signed by Apple. When the LLB finishes its tasks, it verifies and runs the next-stage bootloader, iBoot, which in turn verifies and runs the iOS kernel.
This secure boot chain helps ensure that the lowest levels of software are not tampered with and allows iOS to run only on validated Apple devices.

To my earlier point, here is an excerpt from Apple's iOS Security document. See pp 5, "Secure Boot Chain". Note that this is exactly the process I summarized in my earlier post, and which SwordMaker then said was not the way things worked with Apple devices (an assertion he apparently just pulled out of his nether regions).

Which is exactly what I said. . . and posted to you, including the same quotation from the same link. My point has always been that a lot of this is in the Silicon. Not just in the Boot ROM. The Secure Enclave (iPhone 5s and above) or the Encryption Engine (iPhone 4S, 5C) has a lot etched in the silicon which you keep disputing. . . but Apple has described how it is done, what's in there, when it is put there, which I have also quoted to you. It is NOT all controlled merely by the Boot ROM.

Your assertion has been that it should be simple to get around it by writing code. . . to bypass all of this. Mine is that it is NOT so simple as you claim.