Talk:Firmware Keys

iKeys

I was wondering if anyone had any info on "iKeys". It's mentioned here at the bottom. I'd imagine it's like GenPass but just wondering. Any info is appreciated. --OMEGA_RAZER

Exploit?

Am I to understand that a low level exploit is needed to get the VFDecrypt key? --Shengis14 18:50, 8 October 2010 (UTC)

No, that's not completely true. :P One has to manage to get the key/IV for a ramdisk, and then use GenPass to get the VFDecrypt key. --dra1nerdrake 21:27, 8 October 2010 (UTC)

How would someone like myself go about geting the key/IV for a ramdisk? --Shengis14 22:13, 8 October 2010 (UTC)

You would need (at the very least) an iBoot exploit and a payload to upload that is able to access the AES engine of the device. --OMEGA RAZER 22:16, 8 October 2010 (UTC)

It's just that one of the reasons I'm confused is why there is a sudden jump in the number of keys for the iPod touch 3G on 4.0-4.1?

There isn't an exploit that is iBoot level or lower for that device. --Shengis14 22:50, 8 October 2010 (UTC)

New page?

I think we should make a new page detailing how to utilise Gojohnnyboi's AES payload to get the keys including screenies on opening up an img3 in a hex editor and getting the KBAG etc. Then the keys won't be left to the main devs and iH8sn0w to post. Then all these beta FWs can be decrypted faster and more keys can be posted. I myself would definitely be interested in getting the KBAG etc. and if anybody could create such a page then I would definitely be interested in posting keys myself. Once created the page shouldn't need too much housekeeping either since the process won't change until IMG4 comes along which I will dread :P Who's up to it?? blackthund3r 11:43, 20 October 2010 (UTC)

New table format.

I was thinking, because the tables do not fit into the normal view (7.x beta's for example), maybe we could think of a new design. I had an idea of maybe using device tables, so we could have something like the below (of course we would have a beta and public sections and all devices would be added);

iPhone (As a heading, since actually adding this would break the topic, making it two.)

Date	Build	4			4S	5
		iPhone3,1	iPhone3,2	iPhone3,3	iPhone4,1	iPhone5,1	iPhone5,2
10 Jun 2013	11A4372q	7.0b	7.0b	7.0b	7.0b	7.0b	7.0b
24 Jun 2013	11A4400f	7.0b2	7.0b2	7.0b2	7.0b2	7.0b2	7.0b2
8 Jul 2013	11A4414e	7.0b3	7.0b3	7.0b3	7.0b3	7.0b3	7.0b3
29 Jul 2013	11A4435d	7.0b4	7.0b4	7.0b4	7.0b4	7.0b4	7.0b4

This way, of course we would drop using "6.x" etc. This would also work well with the new format of listing "iPhone 5 GSM" and "iPhone5,1". Let me know your thoughts. --iAdam1n (talk) 23:10, 7 March 2014 (UTC)

+1. Could still overflow (that example already occupies over half of a 1024px wide window), but of course still better than the current format. kirb (talk) 02:37, 8 March 2014 (UTC)

We would also use a deprecated template so that we do not have old devices in the same table, without this, we would have a massive table. --iAdam1n (talk) 11:47, 8 March 2014 (UTC)