SHSH blob

SHSH blobis a term for a small piece of data that is part ofApple's digital signatureprotocol foriOSrestores and updates, designed to control theiOS versionsthat users can install on their iOS devices (iPhones,iPads,iPod touches, andApple TVs), generally only allowing the newest iOS version to be installable. Developers interested iniOS jailbreakinghave made tools for working around this signature system in order to install jailbreakable older iOS versions that are no longer being signed by Apple.[1][2]

Contents

[hide]

1Technical details

2Exploits and countermeasures

3See also

4References

Technical details[edit]

"SHSHblobs" (also called "ECID SHSH"[3]) is an unofficial term referring to thedigital signaturesthat Apple generates and uses to personalize IPSW (iOS software) files for each device; they are part of Apple's protocol designed to ensure that trusted software is installed on the device.[4]Apple's public name for this process is System Software Personalization (System Software Authorization as of iOS 7+).[5]

SHSH blobs are created by ahashing formulathat has multiple keys, including the device type, the iOS version being signed, and the device's ECID (a unique identification number embedded in its hardware).[6]When Apple wishes to restrict users' ability to restore their devices to a particular iOS version, Apple can refuse to generate this hash during the restore attempt, and the restore will not be successful (or at least will require bypassing the intended function of the system).[7][8]

This protocol is part ofiPhone 3GSand later devices.[9]

Exploits and countermeasures[edit]

A major contributor to this article appears to have aclose connectionwith its subject.It may requirecleanupto comply with Wikipedia's content policies, particularlyneutral point of view. Please discuss further on thetalk page.(December 2012)(Learn how and when to remove this template message)

For iOS 3 and 4, SHSH blobs were made of static keys (such as the device type, iOS version, and ECID), which meant that the SHSH blobs for a specific iOS version and device would be the same upon every restore. To subvert that system using aman-in-the-middle attack, server requests the unique SHSH blobs from Apple for the jailbroken device and caches those SHSH blobs on servers, so that if a user changes thehosts fileon a computer to redirect the SHSH blobs check to cache instead of Apple's servers,iTuneswould be tricked into checking those cached SHSH blobs and allowing the device to be restored to that version.[9][10]

iOS 5 and later versions of iOS implement an addition to this system, a random number (acryptographic nonce) in the "APTicket",[11]making that simplereplay attackno longer effective.[12][13]Versions ofredsn0wafter 0.9.9b9 include a way to bypass the nonce requirement for iOS 5, allowing the SHSH blobs and APTicket to both be replayed by "stitching" them into custom firmware.[14]

First released in 2009 (as TinyTSS and Umbrella),[15][16][dubious–discuss]TinyUmbrella is a tool for finding out information about SHSH blobs saved on third party servers, saving SHSH blobs locally,[17]and running a local server to replay SHSH blobs to trick iTunes into restoring older devices to iOS 3 and 4.[18][19]In June 2011, iH8sn0w released iFaith, a tool that can grab partial SHSH blobs from a device for its currently-installed iOS version (limited to iPhone 4 and older devices).[20][21]In late 2011, the iPhone Dev Team added comprehensive SHSH blob management features toredsn0w, including the ability to save SHSH blobs with APTickets and stitch them into custom firmware in order to restore a device to iOS 5 or later.[22]

Replaying SHSH blobs for newer devices (iPad 2 and later) is not always possible, because there are noboot ROM(hardware level) exploits available for these devices. As of October 2012, redsn0w includes features for restoring newer devices between different versions of iOS 5,[23]but it cannot downgrade newer devices from iOS 6 to iOS 5.[24][25]

SHSH blob

推荐阅读更多精彩内容