The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "GID Key"
(fixed wikipedia link; corrected “fancy quotes” to "ASCII quotes") |
(linking UID key) |
||
Line 3: | Line 3: | ||
This key is different on each [[Application Processor|processor, or SoC, model]] ([[wikipedia:System on a chip|system on a chip]]) - in other words, the [[S5L8900]] (chip for iPhone 3G for example) has a different key compared to the [[S5L8930]] (A4 chip for iPhone 4, iPod touch 4G, etc.). |
This key is different on each [[Application Processor|processor, or SoC, model]] ([[wikipedia:System on a chip|system on a chip]]) - in other words, the [[S5L8900]] (chip for iPhone 3G for example) has a different key compared to the [[S5L8930]] (A4 chip for iPhone 4, iPod touch 4G, etc.). |
||
− | Apple explains GID keys in its official [https://www.apple.com/br/privacy/docs/iOS_Security_Guide_Oct_2014.pdf iOS security guide] (page 9, chapter "Encryption and Data Protection"): |
+ | Apple explains GID keys in its official [https://www.apple.com/br/privacy/docs/iOS_Security_Guide_Oct_2014.pdf iOS security guide] (page 9, chapter "Encryption and Data Protection"), along with [[UID key]]s: |
<blockquote>"The device’s unique ID (UID) and a device group ID (GID) are AES 256-bit keys fused (UID) or compiled (GID) into the application processor during manufacturing. No software or firmware can read them directly; they can see only the results of encryption or decryption operations performed using them. The UID is unique to each device and is not recorded by Apple or any of its suppliers. The GID is common to all processors in a class of devices (for example, all devices using the Apple A8 processor), and is used as an additional level of protection when delivering system software during installation and restore. Integrating these keys into the silicon helps prevent them from being tampered with or bypassed, or accessed outside the AES engine. The UID and GID are also not available via JTAG or other debugging interfaces."</blockquote> |
<blockquote>"The device’s unique ID (UID) and a device group ID (GID) are AES 256-bit keys fused (UID) or compiled (GID) into the application processor during manufacturing. No software or firmware can read them directly; they can see only the results of encryption or decryption operations performed using them. The UID is unique to each device and is not recorded by Apple or any of its suppliers. The GID is common to all processors in a class of devices (for example, all devices using the Apple A8 processor), and is used as an additional level of protection when delivering system software during installation and restore. Integrating these keys into the silicon helps prevent them from being tampered with or bypassed, or accessed outside the AES engine. The UID and GID are also not available via JTAG or other debugging interfaces."</blockquote> |
||
Revision as of 22:20, 10 March 2015
The GID key (Group ID key) is the AES 256-bit key shared by all devices with the same application processor. The GID key is part of how iOS encrypts software on the device (more explanation).
This key is different on each processor, or SoC, model (system on a chip) - in other words, the S5L8900 (chip for iPhone 3G for example) has a different key compared to the S5L8930 (A4 chip for iPhone 4, iPod touch 4G, etc.).
Apple explains GID keys in its official iOS security guide (page 9, chapter "Encryption and Data Protection"), along with UID keys:
"The device’s unique ID (UID) and a device group ID (GID) are AES 256-bit keys fused (UID) or compiled (GID) into the application processor during manufacturing. No software or firmware can read them directly; they can see only the results of encryption or decryption operations performed using them. The UID is unique to each device and is not recorded by Apple or any of its suppliers. The GID is common to all processors in a class of devices (for example, all devices using the Apple A8 processor), and is used as an additional level of protection when delivering system software during installation and restore. Integrating these keys into the silicon helps prevent them from being tampered with or bypassed, or accessed outside the AES engine. The UID and GID are also not available via JTAG or other debugging interfaces."
On S5L8900, the GID key was used to generate AES Key 0x837, used as the encryption key for IMG2 files. With the introduction of IMG3 in iOS 2.0, iOS started using KBAGs instead of the 0x837 key. iOS 7.0.1 introduced the IM4P File Format and IMG4 File Format for A7 and newer devices.
In iOS 3.0GM/3.0, a pseudo GID Key was used, which allowed getting firmware decryption keys for these firmwares without the device and with tools such as GitKeys or OpenSSL. See Decrypting Firmwares#S5L8900.
Potential attacks
A hypothetical way to extract this key could be to perform some sort of side-channel attack (see also Talk:GID Key for more speculation about potential attacks).
A presentation from May/June 2011 that explains a variety of attacks aiming to get this kind of information out of a chip: Fault attacks on secure chips: from glitch to flash (Part 1) and Side-channel attacks: new directions and horizons (Part 2).
Research into AES key extraction using side-channel analysis, done from 2010 to 2012: developing new technology for efficient side-channel analysis - using a tool from Quo Vadis Labs.
CIA research into attacks
According to this March 2015 article based on documents provided by Edward Snowden, the CIA has been particularly interested in figuring out how to extract GID keys as part of their efforts to get access to modifying iOS to insert spy software and to research further vulnerabilities:
"At the 2011 Jamboree conference, there were two separate presentations on hacking the GID key on Apple’s processors. One was focused on non-invasively obtaining it by studying the electromagnetic emissions of — and the amount of power used by — the iPhone’s processor while encryption is being performed. Careful analysis of that information could be used to extract the encryption key. Such a tactic is known as a "side channel" attack. The second focused on a "method to physically extract the GID key.'"(The first document and the second one.)
"According to the 2011 document describing the Jamboree presentations on Apple's processor, the researchers asserted that extracting the GID key could also allow them to look for other potential gateways into Apple devices. 'If successful, it would enable decryption and analysis of the boot firmware for vulnerabilities, and development of associated exploits across the entire A4-based product-line, which includes the iPhone 4, the iPod touch and the iPad.'"
The 2011 timing is interesting, since geohot had publicly released a powerful bootrom exploit (limera1n) for A4 devices in October 2010, which presumably the CIA was already using (probably one of the "very small number of security flaws, many of which are public, which Apple eventually patches" they mentioned). If a person has a bootrom exploit like limera1n, they can decrypt firmwares by generating the firmware keys from the KBAGs (since they can use the GID keys on-device even if you can't extract them) - see Firmware Keys. It's possible this talk had been written earlier and presented as still relevant for A5 and future chips.
Related tools
- IOCryptoAcceleratorFamily - "a collection of kernel extensions that provide hardware-accelerated cryptographic functions, e.g. SHA1, AES, pseudo-random number generator (PRNG), etc."
- crypto by planetbeing - "This package allows you to directly access the iPhone's AES engine from userland. You may encrypt and decrypt with the UID and GID keys, as well as any custom keys you provide."
- iphone-dataprotection - wiki includes a list of types of encryption keys used for data protection, including a chart of key hierarchy on iPhone 4.