Unreleased iPhone 2.0 May Already Be Hacked
The as-yet unreleased second iteration of iPhone hardware may already be compromised, reports Engadget and News.com. Members of the 'iPhone Dev Team' have (supposedly) made use of the recently released SDK to gin up a Beta 2.0 software hack. "Unlike previous hacks, this one isn't specific to the latest firmware version, it exploits the way that Apple designed the iPhone's main bootloader. According to the iPhone Dev Team, the iPhone verifies whether or not firmware code has been signed with an RSA certificate before allowing it to be written to memory. The team has apparently figured out a way to disable that check and allow unsigned code to be written to memory."
WAS...
I'm sure the iPhone 2 will be held back until this is fixed.
Jobs will pounce on this faster than a Leopard. They should have kept their mouths shut.
It's not the first time something is hacked before it's even released, but it's always funny.
What really makes this one a good example is that for once this lock used some kind of real crypto (RSA), not some security-through-obscurity stuff. And yet, of course, that defeated, by not even letting the check occured.
Because crypto scenario were Bob tries to hide something to bob, after giving Bob the key are just a bit to stupid to work.
Don't take my posts literally; it's just code to control my botnet.
They hacked firmware 2.0, which will run on current iPhones, there's no mention of new hardware for this stuff...
This thread is probably going to be full of sofware security bashing, deservedly or not. Let's get something constructive out of this... Anyone know of any way to make software security function the way business people dream of? Namely, only approved code running approved processes. I think given access to the hardware any machine can be "hacked" given enough interest and manpower. Even putting security features in the chips themselves, as I've heard they are developing, will just be a relatively minor roadblock.
Well, I guess the iPhone will die a slow death, the same as the PSP (wait a minute, people are still developing for the PSP ... maybe the iphone won't die?).
The vulnerability affects the bootloader. Apple will NEVER, EVER, EVER replace the bootloader by a user update. Any disruption while replacing the bootloader equals a truly dead iPhone. While we may have come to expect complications with our computers, cell phones are another story. If anything, we'll see an updated bootloader in new phones, but the millions already on the market will still be available to be unlocked. Though, Apple will probably have yet ANOTHER security audit so make sure the 2nd gen iPhone has no cracks for illegal activities.
First person to get windows running on the iphone 2.0 will receive a free copy of Microsoft Vista.
on any other platform... this would be called a security vulnerability
No it bloody wouldn't. It would be called "of course you can install your own firmware on an iPaq, or a Treo, or what have you". It would be called "why shouldn't you be able to install programs on your own handset". It would be called "yes, of course that's the way it works".
Of course it's a good thing. Of course it's also a waste of time. Of course you're better off getting a phone where you don't have to screw around looking for DRM backdoors. What I can't figure is how anybody who knows it's a waste of time could possibly be stupid enough to honestly think "this would be called a security vulnerability". Right?
now even hackers are releasing vaporware?
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Except for the fact that it requires hacked firmware to do it. This requires you to first put the phone into emergency restore mode and physically plug it into your PC/Mac and then run a program to alter it. That's not called a virus or a security vulnerability that's called"I have physical access to my own iPhone and I WANT it hacked"
I keep reading they hacked the firmware. So what's to stop Apple from releasing a firmware update that breaks it? They release firmware updates for their computers periodically. Firmware is not impossible to upgrade.
I work for the Department of Redundancy Department.
They could bring out something similar in specs, unlocked, able to run unsigned code, etc, all the capabilities the hacking community wants but sufficiently different in some way to distinguish it from the standard iphone (Bulkier, to add more connections, maybe?). Market it at a huge enough price difference that AT&T doesn't get upset, and everyone would be happy.
Stasis is death. Embrace change.
Given that Apple is slow to approve developers, the only way to test your OpenGL ES program is to Jailbreak the iPhone.
You are supposed to test your program with the iPhone Simulator, called Aspen. The Aspen simulator is part of the free download SDK for the iPhone. However, Aspen does not support OpenGL ES, which is hardware acceleration for cool effects & fast 2D or 3D.
To deploy to the iPhone, Apple must give you a certificate, and they only do that to those paid developers whom they select.
In other words, most game developers can not test their programs because they can not deploy their programs to the iPhone.
I want to play around/learn. I have avoided Jailbreak solutions to date, but I see no other way.
The iPhone is a better computing device than it has ever been a phone. It has bad-to-mediocre voice quality. Anything that can BE a general purpose computer IS, in effect, a general purpose computer.
+++ATH0
Given that Apple seems to have sold a huge number of iPhones to people other than American AT&T customers, I don't think it's a coincidence that Apple has released four firmware revisions now and still haven't managed to lock it down. Once June arrives and it's confirmed that the iPhone can still be unlocked, I'll happily buy one and use it on T-Mobile, as I have no interest in switching to AT&T.
How relevant is hacking the iPhone, now that we have an SDK?
What I would like to see is a hack to get around the $99 fee to run your app on the device itself. The fee annoys me. I can understand it being there for devs that want to release their app, but what about people like me, who just want to see if I can make run on it?
I know, I know, the simulator.... that's no good. I want running on my phone!
I mean, this post is talking about a hack on hardware that only exists internally to the Apple development cycle.
Huh...
Either, they hacked this themselves so as to determine how to protect against it. Or this whole story is hogwash and not worth two grains of salt.