Firmware Keys

VFDecrypt Keys are the keys which can decrypt the files that come with the firmware. Apple uses a public-private key encryption to ensure the safety of their files. Over time Apple has changed the way to encrypt firmware files, thus the way to decrypt files as well as the way to get the VFDecrypt Keys has also. IMG3 encrypted files contain encrypted versions of the VFDecrypt Keys as part of the KBAG (key bag). These can be decrypted with the GID-key. For jailbroken iDevices the keys can be retrieved with the devices hardware AES engine. The VFDecrypt key for the root filesystem image of an iDevice (~500 MB to 800MB in the case of iOS 5) requires either a decrypted Restore Ramdisk or Update Ramdisk. Once you have a decrypted restore or ramdisk, GenPass or iKeyHelper can be used to gather the keys for the root filesystem. For the root filesystem there is one key per device model, with no IV. You can mount/this once it has been decrypted using your program of choice. (For example, 7-zip on Windows (after extracting the DMG on Windows, extract the biggest file with Template:Wp)

Notes

The Update and Restore ramdisks share the same IV and key per type of Application Processor. Here are the current choices:

• S5L8900 - iPhone, iPhone 3G, iPod touch
• S5L8720 - iPod touch 2G
• S5L8920 - iPhone 3GS
• S5L8922 - iPod touch 3G
• S5L8930 (A4) - iPad, iPhone 4, iPod touch 4G, Apple TV 2G
• S5L8940 (A5) - iPad 2, iPhone 4S

Use can use img3decrypt[1] or xpwntool[2] to decrypt these. Likewise, once this is decrypted, you can mount or extract this as well, using the tool of your choice.

You may find Ramdisk Decryption to be helpful.

For those wanting to decrypt their own keys, you must use GenPass to get the keys for 3.0+.

When posting a key page, please use the key template (IN THE CORRECT ORDER) and do NOT Template:Wp it.

For the VFDecrypt Keys of each firmware please check the builds listet at the appropiate firmware version page.

Firmware versions

Final

Main article: Firmware

Beta

Main article: Beta Firmware

Gaps

As you will notice, there may be a gap or two, or a key for a current build that is not there. Please feel free to add them, but please be sure that it is only the key for a User or Developer build, as if you gave the key for another type of build that might or may not be out there people could get in trouble, and we do not want that. Thanks for contributing!