Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In very rare cases the changes introduced by commit can actually cause
an invalid free. Reverted those changes. Also, plist_free() will check
for NULL before doing anything, so an extra check for that is not needed.
|
|
|
|
Also, set libplist requirement to 1.12
|
|
|
|
|
|
|
|
|
|
libimobiledevice version
|
|
|
|
to add digest for Trusted items.
|
|
identity to make sure we use correct values.
|
|
|
|
versions.
|
|
|
|
|
|
|
|
|
|
Only send an empty reply but this seems to be enough to restore
devices that already have valid data.
|
|
|
|
|
|
|
|
otherwise.
|
|
|
|
|
|
|
|
The corresponding message was also "This device isn't eligible for the
requested build" with this status code.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Some devices don't have an SEPNonce so this message just sounds fatal
while it isn't.
|
|
and sound less harmful
|
|
Since we can grab tss records in normal mode and these depend on
nonce values that are valid only for the first reboot, we should not
extract the filesystem after putting the device into recovery mode.
If the filesystem extraction takes longer (e.g. on a network filesystem)
the recovery mode device might reboot while the file system is still
extracting. In that case the TSS record that has been grabbed in normal
mode would be invalid.
|
|
|