Talk:Firmware Keys/2010

From The iPhone Wiki
Jump to: navigation, search
This is an Archive Page
This page is meant for archiving purposes only, do not modify the contents of this page! To see the list of archive pages, go to the main page for this archive. If you have a reply for one of these discussion topics, move it back to the main discussion page and edit it there.
Other Archives • 2009 • 2010 • 2011 • 2012 • 2013 •

3GS 3.1.3

Where is the key for the 3GS 3.1.3 firmware? --L0g0 01:26, 26 July 2010 (UTC)

You mean these? --Dialexio 01:54, 26 July 2010 (UTC)

VFDecrypt error

When I try with the command I get a warning message.It shows that cygcrypto-0.9.8.dll was not found.I've searched this file but it seems I can't find it.Thanks for helping me in advance. --The preceding unsigned comment was added by Delstam (talk) 14:30, August 1, 2009 (UTC). Please consult this page for more info on how to sign pages, and how to fix this.

This DLL is part of Cygwin. You can get it here: [1] --Blackbox 14:45, 1 August 2009 (UTC)
Thanks --The preceding unsigned comment was added by Delstam (talk) 14:58, August 1, 2009 (UTC). Please consult this page for more info on how to sign pages, and how to fix this.
Hey, I need this file too, but the link seems to now be broken. I just got it from here instead. Just thought I'd make a note in case anyone else needs it. MaybachMan 13:17, 17 August 2010 (UTC)
...Cygwin1.dll can also be gotten here. --The preceding unsigned comment was added by MaybachMan (talk) 13:27, August 17, 2010 (UTC). Please consult this page for more info on how to sign pages, and how to fix this.
I'm working on getting my fork of VFDecrypt running on Windows. Soon as I get it compiled, I'll post the download link to a /native/ Windows binary. --dra1nerdrake 17:35, 17 August 2010 (UTC)

VFDecrypt for Mac link

The link in the article is broken, does anyone have a working one? MaybachMan 11:39, 19 August 2010 (UTC)

Use mine from github and build it with 'make linux'. It (should) work. If it does, please post back here so I can update the program. If it doesn't, post back here with the error and I'll try to debug it. --dra1nerdrake 21:13, 19 August 2010 (UTC)
vfdecrypt.c:42:22: error: byteswap.h: No such file or directory
make: *** [linux] Error 1
--MaybachMan 10:44, 20 August 2010 (UTC)
You can get a version that will compile on Mac OS X at GitHub.

Remove Request

As someone mentioned on the Firmware 3.x Beta talk page, I want to request that the whole section "Firmware" on this page here gets removed and all mentioned pages deleted as well. The information there (the VFDecrypt keys) should go into their appropriate firmware page. Or do we still need all VFDecrypt keys (only) together also? If yes, then at least it should be cleaned up and these pages should mention that these are duplicates for the sake of grouping. --http 10:17, 23 October 2010 (UTC)

I think we should just protect the pages VFDecrypt Keys:_1.x, VFDecrypt Keys: 2.x, VFDecrypt Keys: 3.x, and VFDecrypt Keys: 3.x BETA. And if someone discovers a key for those Firmwares we should add it to the talk page for an admin to add. --5urd 15:03, 23 October 2010 (UTC)
These pages are really chaotic. For the 1.x and 2.x pages, it is unknown if they are for the iPhone or iPod touch (or for both). We can just assume something, or try. The 3.x pages contain not only vfdecrypt keys, but some ramdisk keys as well. And some have beta mixed within, others not. I assume that all keys are on their respective firmware page already. If not, then we should create the missing pages and link them to the Firmware or Beta Firmware page. I'll start with that some time if I find the time - feel free to help. But then, if all keys are available on their firmware page, why would we still need these pages? I still request to delete them. We could add a cross table on this page with firmware vs. device and in each cell a link, so that we easily find the page with the keys. I think I'll add this table right away. Then there's no need for these pages anymore. Please discuss here if you agree to remove them afterwards. -- http 20:14, 29 October 2010 (UTC)
I don't think we should delete the key pages until the table shows all blue links so that way we don't trash any keys on accident. --5urd 15:33, 30 October 2010 (UTC)
After making sure we have all keys on their firmware pages, I went ahead and copied the text to this page and deleted the 4.x (final) page. The others will follow, after checking them also. -- http 21:25, 6 November 2010 (UTC)
Ok, now the other pages are also removed and all keys there are on its own page as discussed. Sorry for spamming the Recent changes list. I copied mostly the existing pages, but some of them were not following the standard, so this means the new pages also don't follow the standard. This means more cleanup is necessary. Also I removed the KBAGs as discussed somewhere else where I saw them. I added the Pesudo-GID on three pages (S5L8900 for 3.0 Build 7A341). I have no idea what this is for, so feel free to remove it again if you think this is not necessary. For the 1.x pages Dialexio wrote that the VFDecrypt keys are for both iPhone and iPod touch, so I copied them to both pages. I hope this is correct. For the 2.x pages there was also not mentioned for what device the keys were, so I copied them to the iPhone, or, where it was clear from the version number, only to iPod touch. For versions lower than 2.1 I copied them to both, but since 2.1 only the ramdisk keys were copied to both pages (as S5L8900 applies to iPhone, iPod touch and iPhone 3G). I hope this is all correct. (I'm not very experienced with handling these keys yet.) Because I didn't look into each ipsw, I don't know what files are in there, so I didn't create all necessary sections. This means more cleanup is necessary. Also all keys should be in lower case. I didn't change them, I just copied them over, hopefully without any copy/paste errors. There is much more work left, but I hope I didn't mess it up, but helped to improve the overall structure. Ok, now you can reply and shoot on me. -- http 00:25, 31 December 2010 (UTC)

Page split request

I think we should split this page into two. The first half deals more with the VFDecrypt program, not the keys as the title would suggest. Perhaps we can move the info related to the program to VFDecrypt (program), and make VFDecrypt a disambiguation page. --Dialexio 00:17, 7 November 2010 (UTC)

I like that, but think it should just be VFDecrypt for the program and don't make a disambiguation page, Category:Decryption is like a disambiguation page already... Also making the current page info on the keys would be more like it as that is what the page was originally... --5urd 00:25, 7 November 2010 (UTC)
Yes, VFDecrypt should be about the program or a disambiguation page and here only infos about the keys. All this stuff about the other programs don't really belong here either. That could go to the disambiguation page or small under a "see also" section. Don't forget all the links like [[VFDecrypt Keys|VFDecrypt]] have to get fixed. -- http 00:56, 7 November 2010 (UTC)
So, it's settled. I'll get to moving all of the info related to the actual program to the page VFDecrypt. --Dialexio 21:25, 10 November 2010 (UTC)

Invalid key for GenPass

I'm trying to use GenPass on an S5l8720x key, but it seems to be invalid --Qwertyoruiop 00:19, 11 April 2010 (UTC)

GenPass for 3.x isn't working on 4.0 rootfs. --Cichacz 10:40, 11 April 2010 (UTC)
Thanks --Qwertyoruiop 10:57, 11 April 2010 (UTC)
We can only try asking MuscleNerd to post the new one's code :) --Cichacz 11:05, 11 April 2010 (UTC)
iH8sn0w has some scripts too. Maybe try asking him? --pjakuszew 13:34, 11 April 2010 (UTC)
I think it's better to keep the scripts private. If there's a public script for getting the VFDecrypt keys, Apple developers could just move the keys again, and we will then have to find yet another method for getting them. --pjakuszew 15:41, 11 April 2010 (UTC)
Is there a manual way to acquire the keys? Looking at GenPass' source, it looks like OpenSSL could be involved. Although asking someone for their script wouldn't hurt. --Jimmy.M
Reversing asr could be a solution. --Qwertyoruiop 15:37, 11 April 2010 (UTC)