Clicky

iPhone SDK key leaked?

Word out on the ‘net is that the iPhone’s "secret’ SDK key has been leaked to the general public. The SDK key is the digital signature that allows iTunes to verify the validity of a given application. As we already know, Apple has said that they will need to electronically verify and sanction any 3rd party application destined for the iPhone. If developers can figure out how to include this newly leaked key in their homebrew apps, however, we could see 3rd party software installation without the need for Apple’s blessing (and without Apple’s pay-per-app scheme). No word on just how this leaked, but anyone interest should hit the link for more info on the key itself, or take a long hard look at the image above.

[Via TUAW]

Read

12 comment(s) for this post.

  1. On Jan 28, 2008 @ 7:54 pm, Ghengis Said:

    man, we are just trying hard ( of course its a good thing) to get some FREE apple stuff . May be someday it will come true and we can use iphone the way we want to

    Permalink | Reply

  2. On Jan 28, 2008 @ 9:00 pm, john Said:

    Can’t Apple just change to a new key with a software update?

    Permalink | Reply

  3. On Jan 28, 2008 @ 10:54 pm, Dtest5477 Said:

    i think more paraphrasing and less word for word would be good.

    also pay per app scheme? come on. Joshua your better than this, I would have expected this crap from Gregory.

    Permalink | Reply

  4. On Jan 28, 2008 @ 11:41 pm, Bla1ze Said:

    Yayyy!! just what every iPhone user needs….a good dose of unverified malicious code running on their iPhone…Bring on the malware.

    Permalink | Reply

  5. On Jan 29, 2008 @ 12:14 am, leetgnnr Said:

    does not having the SDK prevent users from developing apps for the iPhone?

    Permalink | Reply

  6. On Jan 29, 2008 @ 2:45 am, Galvatron Said:

    well th sdk pobaly contans all the commnd tags an the phones simultor to test your apps all iwill say is MORE POWER TO THE HAXORS AN DEV TEAM. jobs is trying to pull an m$ too little to late. screw apples must verify this and that an py to run this an that. please.

    I supose apple will make activation keys one use too? if so bad call even M$ lets you use activation keys 8-12 times befor you have to buy a new one

    Permalink | Reply

  7. On Jan 29, 2008 @ 6:49 am, blah Said:

    Don’t get so excited… more than likely that is just the public key. The actual private key is most likely buried in the application, encrypted.

    Personally, I like the idea of a central application certification authority. The last thing we need is a bunch of virii ladden applications sending our locations and addressbooks around.

    Permalink | Reply

  8. On Jan 29, 2008 @ 8:15 am, Martin Said:

    Just out of curiosity did apple ever say it would be using a pay per app scheme? They will probably just have a data base like they do for dashboard widgets and charge for certain apps like games created by EA and such.

    Permalink | Reply

  9. On Jan 29, 2008 @ 9:49 pm, Christopher Cox Said:

    Public key or not, releasing it prior to the release is extremely idiotic. If this is indeed the private key, what makes you think they won’t hold back the SDK release so they can rectify the situation? Most likely, the release of the private key will only set back the release of the SDK, which will only frustrate more people.

    Permalink | Reply

  10. On Jan 29, 2008 @ 10:28 pm, blah Said:

    @Martin, They haven’t said anything in public about how applications get loaded onto devices. One would guess that iTunes would be a good method. If they choose to do it that way, then they would more than likely offer some sort of revenue sharing with the developers.

    I hope they do it that way.

    Permalink | Reply

  11. On Jan 30, 2008 @ 1:02 am, Kevin Said:

    YAY!! Finally someone smart enough to bring apple to it’s knees. Unfortunately, this is only one small area of their bloated domain, but every hit counts!! :)

    GO APPLE DESTROYERS!!!

    Permalink | Reply

  12. On Jan 31, 2008 @ 4:33 am, Jimmy D Said:

    Apple should have given each developer their own key. That way when it leaks they can trace it to the developer.

    Permalink | Reply

Leave a comment on this post.