r/jailbreak • u/Apprehensive_Net_988 • 3h ago
Discussion downsides of tss jb
I understand most of the jb community is mad because of the gatekeepers and devs who took advantage of the tss bug that was recently patched …
But have we thought about the fact that most devs have an untethered jb right now and that plenty of them might lose interest in developing for this reason?? This is literally why jailbreak is still dying lol (and no, calif doesn’t have any jb for ios 27 as it has no sptm bypass 🤨 and there’s no guarantee something will come out either lol)
Anyways, i recommend iOS 18 users to update since next year it might start losing some app support 😍, but yea, “jailbreak is back guys” is such a realistic feeling isn’t it
1
u/Regular-Resist3581 iPhone SE, 3rd gen, 27.0 1h ago
Firstly, jailbrekaing isnt dead there is a CONFIRMED SPTM bypass that I myself have even found in my own repo (completely assited with ai in advance bc i am NOT a security analyst) as well as another post on this subreddit that also shows proof (if you can understand it) that there has been a PATCHED sptm bypass so now all we need to do is play the waiting game, again until some security firm actually reverse engineers it.
1
u/Regular-Resist3581 iPhone SE, 3rd gen, 27.0 1h ago
1
1
1
u/Nathaniel820 iPhone 12, 14.2 | 1h ago
Lmfao bro is still trying to share their random GitHub repo after literally every real dev who commented on it in the other post pointed out it was utterly useless AI jargon.
1
1
u/Regular-Resist3581 iPhone SE, 3rd gen, 27.0 36m ago
besides everyone isnt hating on the other post btw
5
u/0xjf iPhone 15 Pro Max, 17.3.1| 2h ago
There is virtually no tweak support on iOS 27. Anyone with the bug has had to put in significant work just to get older tweaks functioning. It's not a stable environment, which is why a public release wasn't worthwhile without further polish. Unfortunately, we ran out of time.
And even if it had been released, maybe 500 people would've been able to jailbreak, while everyone else would've been just as cooked.
So what's the better option? Burn the bug for 500 people, or preserve it and give developers and researchers a unique advantage in discovering future vulnerabilities, developing exploits, and building jailbreaks?
It ended up getting burned anyway, likely because someone submitted it to Apple. But most of us saw little value in rushing a public release, drawing Apple's attention, and potentially getting the bug patched sooner, especially when so few people would've benefited.