milkshake28
iPF Noob
- Joined
- Jun 9, 2011
- Messages
- 22
- Reaction score
- 0
By reading the tweets and @comex tweets.... I have a feeling that this is Jailbreakme 3.0 coming up
Welcome to the Apple iPad Forum, your one stop source for all things iPad. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
And some bad news :-
By reading the tweets and @comex tweets.... I have a feeling that this is Jailbreakme 3.0 coming up
So what does that mean for us iPad 2 owners who have 4.3.3 on their iPads, does this jailbreakme.com work for that
Lakerfanalways said:So what does that mean for us iPad 2 owners who have 4.3.3 on their iPads, does this jailbreakme.com work for that
So what does that mean for us iPad 2 owners who have 4.3.3 on their iPads, does this jailbreakme.com work for that
Nobody will know what it means till it's released. That's why it's a teaser!
It has something to do with PDF exploit
It has something to do with PDF exploit
Huh. Nice guess!
If it is a userland-PDF-viewer exploit, does that mean that there would be limitations on the jailbreak? Compared to, say, getting root access from the bootrom?
If it is a userland-PDF-viewer exploit, does that mean that there would be limitations on the jailbreak? Compared to, say, getting root access from the bootrom?
If it is a userland-PDF-viewer exploit, does that mean that there would be limitations on the jailbreak? Compared to, say, getting root access from the bootrom?
No it doesn't. The only time jailbreakme.com was used in our little world was for iPad1 3.2.1 firmware, and it used a PDF exploit to deploy the jailbreak on the device. A specially malformed PDF was downloaded to the device via Mobile Safari and did it's business.
Where the exploit is has nothing to do with the functionality the jailbreak will provide. It's just a way to get through the door to gain root access and work your magic...
So the most intriguing question is... is the teaser hinting at a new PDF exploit (the old one was well and truly patched in 3.2.2), or is it saying goodbye to the old exploit in preparation for a new one???
Hope that helps.
Does an approach like that require that there be a flaw in the application as well as in the app sandbox?