Update Jailbreak detection bypasses #658
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added many functions and paths for bypassing jailbreak detection. There are many because the app I was testing had a lot of detections. This should also bypass much of the iosSecuritySuite project detections. Most of these functions have been verified to work by me on a few apps. Two functions are commented out as they could potentially break legit application functionality. I tried to follow the flow with the functions that was already implemented. I realize I added a lot of changes, which may make it harder to test, and also made the file huge. I plan to streamline the file down the road. The second commit was to remove one line.