https://github.com/opa334/darksword-kexploit

Unlike other repos, this one was not written by generative AI.

WIP

GitHub - opa334/darksword-kexploit: iOS <=26.0.1 DarkSword Kernel Exploit reimplemented in Objective-C (WIP)

iOS <=26.0.1 DarkSword Kernel Exploit reimplemented in Objective-C (WIP) - opa334/darksword-kexploit

GitHub
@opa334 With all these exploits, we’re kind of lost because we don’t know anymore whether the Coruna exploit will lead to a jailbreak in the near future, or if it will be Darksword instead… What are the chances that a jailbreak based on Darksword gets released before Coruna?
@etas0n @opa334 Opa can’t just use Darksword because it doesn’t contain a PPL/SPTM bypass. It’s either just Coruna or both.
@etas0n DarkSword is missing a PPL/SPTM bypass. We still need a reverse engineered version of the bypasses in Coruna to jailbreak (maybe) up to 17.3.1 on arm64e devices. arm64 updates will come sooner.
@opa334 @etas0n I suppose there are some extra challenges besides implementing the exploits when going to iOS 17 or 18, correct?
@opa334 @etas0n Then keeping the 17.0 system is the right choice for me.
@opa334 @etas0n My 15 Pro Max. iOS 17.3.1 seems to have some hope.
@opa334 @etas0n I'm currently reverse-engineering the ppl/smtp bypass section; I think I should be able to rebuild the whole thing in a few weeks. If you're interested, I'll share the GitHub link with you so you can create a rootless JB on iOS 17.x.
@Renero @opa334 Keep iterating on it and share it once it’s in a usable state
@opa334 do you think iPhone 17 models will be compatible due to new memory integrity enforcement ? Even if we get PPL/SPTM bypasses
@opa334 I've been sticking with the 17.0 version since I bought it, and I'm still using the Demon YYDS right now
@opa334 incredible! Happy to see jailbreaking still kicking it!
@opa334 github gone, it is time for gitlab? #migration #gitlab
@opa334 how about 18.7.5?