For those unaware, this is not the bug most jailbreakers will use for iOS 11.3.1, because I believe it requires a developer certificate. There is another, hard to exploit bug that does not.
Your jailbreak spirit lives on, a big thank you! A tweak exists for the official client to clean up a lot of the issues:
https://github.com/BandarHL/BHTwitter
Hopefully this now gets more support with the antics that Twitter has pulled with these 3rd party clients.
iOS 13 jailbreak: <a href=" ">https://ios-jailbreak.com</a> tweaks, news, and more for jailbroken iPhones, iPads, and iPod touches.
Installed anything great recently? Got an idea for a tweak? Wrote a cool tutorial? Curious about how something works? Let us know!
iOS 13 jailbreak: <a href=" ">https://ios-jailbreak.com</a> tweaks, news, and more for jailbroken iPhones, iPads, and iPod touches.
Installed anything great recently? Got an idea for a tweak? Wrote a cool tutorial? Curious about how something works? Let us know!
Any way to check if my iPhone is affected? I'm still on 12.1.2, which was released before the fix, so if I'm affected, I should still have the malware on my device.
I wrote a patch to fix it that one of the jailbreaks used. I wasn't in the scene, but wanted to protect my ipod touch. So I figured out a patch and gave it to somebody named "pumpkin" on IRC. It's been a long time, but I remember it was fun to learn ARM assembly and figure out how to rewrite the code to get enough space to insert a test and return.
reply