Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
pair_record_generate_keys_and_certs()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This refactoring is mandatory as libimobiledevice should not interact with
the pair record configuration directory which is owned by the usbmuxd user.
This change also adds compatibility for the native usbmuxd and thus pair
records saved by iTunes.
|
|
|
|
|
|
|
|
|
|
This will fix that:
lockdownd[25] <Notice>: 00484000 _receive_message: Could not receive size of message, expected 4 bytes, got -1 bytes: (54, Connection reset by peer)
|
|
Signed-off-by: Martin Szulecki <m.szulecki@libimobiledevice.org>
|
|
|
|
|
|
|
|
|
|
This reverts commit 56392428a49543bab4b12431451ec04bb799c411.
Actually I committed this because of usbmuxd complaining about a TCP RST.
But lockdownd is now complaining since it waits for the Goodbye packet
(which I apparently didn't see during testing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The internal status callback used a timeout of 30 seconds to receive status
messages about the progress of an operation. However, slow devices or large
app archives trigger this timeout causing the handler to return before
the operation was actually complete. This fixes it by removing the internal
timeout by waiting forever and only returning early in case of a real error.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|