summaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorGravatar Jay Freeman (saurik)2016-08-09 17:18:14 -0700
committerGravatar Jay Freeman (saurik)2016-08-09 17:18:14 -0700
commit00f8e5733f716da8032606566eac7a9e2e49514d (patch)
treeff9e6cc68681651f069f138bbaddb87f04779bbb /src
parent72643b2b83990b9cf97cc84b285b30763d44a72d (diff)
downloadlibimobiledevice-00f8e5733f716da8032606566eac7a9e2e49514d.tar.gz
libimobiledevice-00f8e5733f716da8032606566eac7a9e2e49514d.tar.bz2
lockdown: return LOCKDOWN_E_INVALID_HOST_ID when missing pair record
When the check of /var/db/lockdown was removed, lockdownd_do_pair started to always return LOCKDOWN_E_INVALID_CONF instead of usually (but not always...) returning LOCKDOWN_E_INVALID_HOST_ID for devices not currently paired. This change not only breaks some third-party code, but also breaks the other code in this library calling this function (lockdownd_client_new_with_handshake).
Diffstat (limited to 'src')
-rw-r--r--src/lockdown.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lockdown.c b/src/lockdown.c
index 904267e..cae950b 100644
--- a/src/lockdown.c
+++ b/src/lockdown.c
@@ -895,7 +895,7 @@ static lockdownd_error_t lockdownd_do_pair(lockdownd_client_t client, lockdownd_
/* use existing pair record */
userpref_read_pair_record(client->udid, &pair_record_plist);
if (!pair_record_plist) {
- return LOCKDOWN_E_INVALID_CONF;
+ return LOCKDOWN_E_INVALID_HOST_ID;
}
}
}