Behind the Scenes of iOS Security
Black HatYouTube ↗
Further reading 1
Caption notes
Ivan Krstić explains three mechanisms from the iOS 10 period: separating writable and executable JIT mappings, binding data-protection keys to the Secure Enclave, and using cloud HSMs for recoverable secrets. Recovery attempts reveal a subtle design issue: adding redundant devices can multiply the guessing budget, so counter updates require a majority. The Q&A also exposes the cost of immutable code. After signing cards are destroyed, patched fleets accept new enrollments; existing escrow records remain decryptable only by their original club. This is the vendor’s account of its design at the time, not an independent audit of current systems or absolute security.
Public machine transcript (may contain transcription errors) ↗Original passages · 2
every new unit you escrow to increases that maximum failure counta majority quorum is required to proceed