-
Notifications
You must be signed in to change notification settings - Fork 125
checkra1n patches not applied after booting with KTRW #8
Comments
Unfortunately this is currently expected behavior: pongo_kextload disables the checkra1n kernel patches. If you'd like to try booting with checkra1n kernel patches enabled, then you'll need to make the following changes:
Note that I haven't tested this configuration yet; it's possible it may work, but it's also possible it will break in weird and unanticipated ways. |
Thank you, I'll try it out and let you know how it goes. |
Initial results is that unsigned code execution is working, as is KTRW (although SSH isn't). Thank you for your help :) |
Excellent, I'll plan to incorporate more well-defined support for using KTRW with checkra1n kernel patches. Please do let me know if you encounter any issues in the meantime. |
Thank you again, I'll let you know if I spot anything |
Make sure you’re exposing the SSH port properly over USB by using iProxy to forward port 22 to port 44. & make sure you run it with sudo! |
After booting with KTRW, checkra1n's kernel patches don't appear to have been applied meaning that you can't SSH into a device and you can't launch unsigned applications.
Is this expected behaviour? Would it be possible to enable checkra1n's patches? It would be extremely useful to be able to launch unsigned applications in order to debug kexts that are denied access by the app sandbox.
The text was updated successfully, but these errors were encountered: