0x06b - Upgrade Jailbreak section #1943
Merged
Conversation
This file contains 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
Collaborator
cpholguera
commented
Oct 15, 2021
cpholguera
commented
- update basic testing setup
- upgrade the jailbreak section to make it more up-to-date and at the same time timeless (include most complete sources for jailbreakable devices/versions)
- include links to other relevant chapters
…it more up-to-date and at the same time timeless. Include links to other relevant chapters.
TheDauntless
requested changes
Jan 23, 2022
| @@ -103,31 +66,77 @@ There are *tethered*, *semi-tethered*, *semi-untethered*, and *untethered* jailb | |||
|
|
|||
| - Semi-untethered jailbreaks allow the device to boot on its own, but the kernel patches (or user-land modifications) for disabling code signing aren't applied automatically. The user must re-jailbreak the device by starting an app or visiting a website (not requiring a connection to a computer, hence the term untethered). | |||
|
|
|||
| - Untethered jailbreaks are the most popular choice for end users because they need to be applied only once, after which the device will be permanently jailbroken. | |||
| - Untethered jailbreaks are the most popular choice for end users because they need to be applied only once, after which the device will be permanently jailbroken. They are very rare and usually benefit from hardware-based vulnerabilities, such as the [limera1n exploit](https://www.theiphonewiki.com/wiki/Limera1n "limera1n exploit") which directly affected the BootROM of the iPhone 4 and iPad 1. | |||
There was a problem hiding this comment.
Isn't the fact that it's untethered because there are additional vulnerabilities that allow you to write persistent code somewhere that is not part of the secure boot chain? (rather than the fact that the vulnerability itself is in HW, because Checkra1n is also in bootrom, but non persistent)
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
Co-authored-by: Jeroen Beckers <info@dauntless.be>
cpholguera
commented
Jan 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.