Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
User Journal

Journal djh101010's Journal: iPhone 1.1.1 firmware jailbreak success! 4

Well, it took a couple of weeks, but the smart folks on the iPhone Dev team have succeeded with a jailbreak on iPhone firmware version 1.1.1 There's a good description here: http://www.tuaw.com/2007/10/08/announcing-a-preliminary-iphone-1-1-1-jailbreak It's "not ready for prime time" yet but, the fact is that they're in and can navigate the filesystem and deploy files to it. Springboard apparently has some tweaks to make life more difficult for 3p apps (GRRRR....) but ... this is Unix, we have the root password, and as any good sysadmin will tell you, if you have physical access to a box, _and_ especially the root password, anything can be done. So, how will Apple respond? I can see a few scenarios:

1. They give us a software development kit and acknowledge reality (30% chance)

2. They pretend that this is as good as they can do, tell AT&T "Well, we tried", shrug, and we get on with business as usual (40%)

3. They choose to continue the cat&mouse game, trying to lock us out and succeeding for a week or two per iteration. Yet in the meantime we always have 1.0.2 and now, apparently, 1.1.1 to work with. (30%).

If they choose to go with 3, it's annoying but not insurmountable. Unless they decide to get really nasty about it and use (mumblesnarf grumbly naganaga). Which would suck. But we'd _still_ have a good version to work from. Taking that thought a bit further - 1.0.2 is _completely_ open. Worst case, smart people get into 1.1.1 and friends, and back-port the good parts (double-tap home button for instance) to 1.0.2, releasing community issued patches just as happens in so many other projects. So the worst case, isn't all that bad, and I don't think it's all that likely. I think it'll be just fine, and we'll be playing tetris and PigShooter on 1.1.1 soon enough, is what I'm saying. I could be wrong though, it's happened before a time or ten.

So - how about the iPod Touch then?
This discussion was created by djh101010 (656795) for no Foes and no Friends' foes, but now has been archived. No new comments can be posted.

iPhone 1.1.1 firmware jailbreak success!

Comments Filter:
  • Isn't the method an arbitrary code execution that's triggered by a malformed TIFF image?

    If so, of course they're going to patch it. You can't leave something like that open and facing the web.
    • Isn't the method an arbitrary code execution that's triggered by a malformed TIFF image?

      If so, of course they're going to patch it. You can't leave something like that open and facing the web.

      Looks like it is, yes. So, it'll get patched, and someone will find another one. If they're smart they're looking for another one already, or already have found it and have it in reserve for when this one is patched. Then, patch comes out, smart people break into 1.1.2, backport the patch for the TIFF vulnerability from that to 1.1.1 and release it as a community patch to the unjailed 1.1.1. Lather, rinse, repeat.

      Or Apple could just give us wide open write access to the /Applications directory. Not

      • by Trillan ( 597339 )
        I'd love to see user-installable applications of some kind for the iPhone and iPod. Even just widgets would be a great start.
        • I'd love to see user-installable applications of some kind for the iPhone and iPod. Even just widgets would be a great start.

          If you're running firmware 1.0.2, you have dozens of options. If you've upgraded to 1.1.1, at this time, the option is to back out that upgrade back to 1.0.2, and then you're golden.

          Not to flog my own site but, it's got guides for both. Take a look here [ipodtouchmods.com] and scroll down to September 30th for a link to the downgrade process if you need it. Also, check out "summerboard" here [apptapp.com], which shows you the sorts of changes that you can make, today, to your iPhone running firmware version 1.0.2

          If there's anything

I've noticed several design suggestions in your code.

Working...