fix(imagemounter): apply RestoreRequestRules when personalizing DDI#776
Open
qiuzilin wants to merge 1 commit into
Open
Conversation
Personalized Developer Disk Image mounting (iOS 17+) requests a signature from Apple's TSS server. Newer BuildManifests (e.g. iOS 26) no longer carry static EPRO/ESEC values on the trusted manifest entries; instead they ship `RestoreRequestRules` (on the LoadableTrustCache entry) that derive these fields from the request parameters. Previously getSignature read entry.EPRO/entry.ESEC directly, which decode to their zero value (false) for these manifests. Apple then rejects the request with `STATUS=94 (This device isn't eligible for the requested build)` because a production + secured Img4 device must send EPRO=true/ESEC=true. Parse RestoreRequestRules from the manifest and apply them (matching the algorithm used by idevicerestore / pymobiledevice3) so the correct EPRO/ESEC are sent. Verified end-to-end against a physical iOS 26.5 device, which now mounts successfully. Adds unit tests for applyRestoreRequestRules.
Collaborator
|
Important change, I had to add those properties manually to the manifest so it would work 😅 I'd rather @danielpaulus approve it for merging though |
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
2 participants
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.
Personalized Developer Disk Image mounting (iOS 17+) requests a signature from Apple's TSS server. Newer BuildManifests (e.g. iOS 26) no longer carry static EPRO/ESEC values on the trusted manifest entries; instead they ship
RestoreRequestRules(on the LoadableTrustCache entry) that derive these fields from the request parameters.Previously getSignature read entry.EPRO/entry.ESEC directly, which decode to their zero value (false) for these manifests. Apple then rejects the request with
STATUS=94 (This device isn't eligible for the requested build)because a production + secured Img4 device must send EPRO=true/ESEC=true.Parse RestoreRequestRules from the manifest and apply them (matching the algorithm used by idevicerestore / pymobiledevice3) so the correct EPRO/ESEC are sent. Verified end-to-end against a physical iOS 26.5 device, which now mounts successfully.
Adds unit tests for applyRestoreRequestRules.