Page 11 of 14 FirstFirst ... 234567891011121314 LastLast
Results 101 to 110 of 140
Discuss [1.1.3] Firmware Image Decryption Key at the General - Hackint0sh.org; Originally Posted by slimnickyy Being that this has not been possible in the past (e.g. ...
  1. #101
    Rookie Array

    Join Date
    Sep 2007
    Posts
    24
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by slimnickyy View Post
    Being that this has not been possible in the past (e.g. - 1.1.2 apps didn't work in 1.1.1), why would you expect this to be the case now?
    Quote Originally Posted by thecompkid View Post
    It has been confirmed by NG that the 1.1.3 apps do not work on the 1.1.2 FW. He even uploaded Maps.app from 1.1.3 (don't have the link on hand, sorry) just to prove it to us. This isn't even very surprising considering the imminent release of the SDK. Apple is surely refining its Obj-C libraries, and it only takes one misplaced call to "brick" an app, so we're back at square one.
    If that is the case for the apps then why did the 1.1.2 SMS app work when it was transported to 1.1.1 or earlier?

    If you could get the link to the Maps app or if you could PM me then I could take a look at it and see whats going on. GUI apps are one of my things (cracking keys is not really my best skill as you have noticed), and I'm putting my money on Apple putting in a line of code that stops the app being run on anything but 1.1.3, as Apple knows that people will want to take the apps to earlier versions like they did with the SMS app.

    Quote Originally Posted by AriX View Post
    Brute forcing is not going to work. There are... too many possibilities. :/

    The md5 is a hash, not a key. The key has not been posted.
    Yeah, sorry that was my typo. I meant md5 hash...

    Quote Originally Posted by thecompkid View Post
    3) We expose the exploit, but the dev teams are assholes about it, and they make us wait anyway.
    That, sadly, sounds a lot more likely than the other two .
    Yep, I think that is what is going to happen as well. The dev team are not known for good decision making, and I'm not a fan of them. I donated in the start but won't again until they get their act together.


  2. #102
    Senior Professional Array slimnickyy's Avatar

    Join Date
    Sep 2007
    Location
    London
    Posts
    418
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    30

    Default

    Apple will simply have its own team whose sole task is to attempt to jailbreak the phone. Any successes will be investigated so that the method can be closed off. Arguably it'll make the phone more secure, but of course we want access!

    I think 1.1.4 is going to be a bitch of a firmware.

    No one has mentioned whether or not it's possible for Apple to include in a future firmware the updated bootloader, or is the bootloader solely a piece of hardware that can't be upgraded? I would assume it's not, as we have recently seen it can be downgraded, though only by opening the phone. I wonder if Apple, being the developer and holding all the keys (literally), if they can attach this updated BL to a future FW?

    Lastly, how is it that no one knows the way to go about decrypting this key? Are the methods used the by dev team(s) so secret that no one knows how they can decrypt a FW and extract a secpack in a relatively short time span (days, weeks, rarely a month)? Even at a month, it's many years ahead of what it's estimated to take to brute force the key.
    Last edited by slimnickyy; 01-22-2008 at 03:52 PM.

  3. #103
    Senior Professional Array xcesivemastub8ah's Avatar

    Join Date
    Dec 2007
    Posts
    139
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by slimnickyy View Post
    Apple will simply have its own team whose sole task is to attempt to jailbreak the phone. Any successes will be investigated so that the method can be closed off. Arguably it'll make the phone more secure, but of course we want access!

    I think 1.1.4 is going to be a bitch of a firmware.

    Oh no no no NO! Haven't you heard, dude? Apple only knows what the dev teams here show them. They just have a guy (maybe Steve jobs himself) on here all the time getting info. No team of pro developers/programmers can figure out what a rogue team of hackers, that just do this for fun, can. Right now they are in Cupertino running around all crazy and desperate because the dev team won't release the JB! I even had a mod imply that to me.


    Speaking of mods.... Why hasn't this thread been removed? There are about 5 of these "wha wha wha we want the JB" threads...

  4. #104
    J to the T. Shaken, not Stirred Array thecompkid's Avatar

    Join Date
    Jul 2007
    Posts
    1,152
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    75

    Default

    Quote Originally Posted by xcesivemastub8ah View Post
    Speaking of mods.... Why hasn't this thread been removed? There are about 5 of these "wha wha wha we want the JB" threads...
    Try actually reading the thread. We're working towards a JB, not whining, so nice try but STFU.

    Anyway, something occurred to me just a few minutes ago. It is common knowledge that the dev team had 1.1.3 before release, possibly longer than a month before, actually. They claim they had an anonymous leaker from "the other side" but I doubt this leaker would just cut off contact. Perhaps the dev team has knowledge of future FW upgrades and this is the reason for the complete secrecy, they don't want to let Apple know they have it.

  5. #105
    Advanced Array

    Join Date
    Jan 2008
    Posts
    37
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by thecompkid View Post
    ...
    someone who actually knows how to code.
    ...
    Coding is not really the problem. I can even code in ARM assembler. But the sad truth is I don't have any experience with MacOS or BOs.

    So for me the first step would be to get the code to decrypt the dmg. After that the arm code could be disassembled and analysed.


  6. #106
    J to the T. Shaken, not Stirred Array thecompkid's Avatar

    Join Date
    Jul 2007
    Posts
    1,152
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    75

    Default

    Quote Originally Posted by atzplzw View Post
    Coding is not really the problem. I can even code in ARM assembler. But the sad truth is I don't have any experience with MacOS or BOs.

    So for me the first step would be to get the code to decrypt the dmg. After that the arm code could be disassembled and analysed.
    Damn, that's an even suckier square one. :p

  7. #107
    Senior Professional Array slimnickyy's Avatar

    Join Date
    Sep 2007
    Location
    London
    Posts
    418
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    30

    Default

    Quote Originally Posted by thecompkid View Post
    They claim they had an anonymous leaker from "the other side" but I doubt this leaker would just cut off contact. Perhaps the dev team has knowledge of future FW upgrades and this is the reason for the complete secrecy, they don't want to let Apple know they have it.
    Knowing the ego and secretiveness of Apple's leader, Steve Jobs, I am sure some major shit hit the wall when that firmware was leaked. Either way cat is out of the bag now. Apple knows they've got a leak and will plug it.

  8. #108
    Senior Professional Array slimnickyy's Avatar

    Join Date
    Sep 2007
    Location
    London
    Posts
    418
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    30

    Default

    Quote Originally Posted by xcesivemastub8ah View Post
    Oh no no no NO! Haven't you heard, dude? Apple only knows what the dev teams here show them. They just have a guy (maybe Steve jobs himself) on here all the time getting info. No team of pro developers/programmers can figure out what a rogue team of hackers, that just do this for fun, can. Right now they are in Cupertino running around all crazy and desperate because the dev team won't release the JB!
    haha, right. If you honestly don't think Apple will actively try to pre-empt this then you're mistaken. They will do so solely in view to not look like a bunch of twats (that is if they couldn't find a hole that they now know is obviously there). So yes, they will concentrate on finding what exploits are available to jailbreak and patch accordingly before or with the SDK.

    Surely if the dev team really wanted to make sure this worked in "our" favour (didn't ask us), then they should have kept quite and not said anything about having a JB.

  9. #109
    J to the T. Shaken, not Stirred Array thecompkid's Avatar

    Join Date
    Jul 2007
    Posts
    1,152
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    75

    Default

    Quote Originally Posted by slimnickyy View Post
    Knowing the ego and secretiveness of Apple's leader, Steve Jobs, I am sure some major shit hit the wall when that firmware was leaked. Either way cat is out of the bag now. Apple knows they've got a leak and will plug it.
    I've heard that Jobs screams at his employees when he's in a good mood (relatively), I don't even want to imagine what the team had to endure the second he heard about that disaster. Still, the official iPhone development team is probably pretty large, and since the leak was never distributed, I doubt the offender was found. It would make sense that the leaker would want the leak to be more private this time around, as his bruises are probably still healing.

  10. #110
    Senior Professional Array xcesivemastub8ah's Avatar

    Join Date
    Dec 2007
    Posts
    139
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by thecompkid View Post
    Try actually reading the thread. We're working towards a JB, not whining, so nice try but STFU..
    HAHA STFU!!! Dude nobody here is 5 yrs old. This is nothing more than a "maybe we if we sound like we can do something they will say WTF and release the JB" thread. Chances are the guys could give you ALL the info on how to JB and create apps and you guys here STILL wouldn't have the knowledge OR resources to create anything usefull. If you guys did, then there would be no need for this thread in the first place. The people here that know are on the dev teams. Plain and simple. "STFU"? arent you the one who was on here claiming to have gotten an email from Steve jobs himself, giving you info?


 

 

Similar Threads

  1. 1.1.4 firmwire decryption
    By winmedia in forum General
    Replies: 8
    Last Post: 04-15-2008, 10:43 AM
  2. Firmware image signed
    By non4bidden in forum iPhone "2G" (Rev. 1)
    Replies: 3
    Last Post: 02-27-2008, 10:00 AM
  3. [1.1.3] deleting the firmware image
    By syamazing15 in forum General
    Replies: 4
    Last Post: 01-25-2008, 12:53 PM
  4. I have an idea on how to decrypt the 1.1.1 firmware image
    By ChronicProductions in forum iPhone "2G" (Rev. 1)
    Replies: 27
    Last Post: 10-01-2007, 01:04 PM
  5. Regarding new firmware image 1.1.1
    By vpr in forum General
    Replies: 0
    Last Post: 09-29-2007, 12:09 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin®
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 02:44 PM.
twitter, follow us!