You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that response failed at line 730 of lockdown.c and the response is returning with LOCKDOWN_E_ESCROW_LOCKED (-35).
Temporarily commenting out will make ideviceinfo successful.
/* in any case, we need to validate pairing to receive trusted host status */
ret = lockdownd_validate_pair(client_loc, NULL);
The ValidatePair request was removed from iOS lockdownd, so it doesn't understand it. It will return that the command is invalid.
Commenting that line in lockdown.c out will make it work when the device is already paired, yes. Since we need to keep backwards compatibility I need to work out a solution that works in all cases.
@EliyahuStern generally yes, just need to make sure the actual pairing works with the open source usbmuxd for a new pairing.
Even for < 11 it actually works without validatepair (since starting a session only works with a correct pairing).
@nikias just installed ios 11 beta little while ago, and found that my code is not working (early disconnect after validate pair), so i checked with libimobile and same issue.
then i decided to look at github, and see you are already working on it.
i still plan to do communication capture (with hardware usb monitor), since itunes for windows seems to be working with ios11 beta.
they might have something up in the sleeves, that makes seamless communication with old and new devices possible 🐱
@mexmer as I said, ValidatePair is technically not required even for older devices. At some point IIRC it was required to gain trusted host status (ideviceinfo -k TrustedHostAttached), but at least on iOS 5.0.1 it is true without performing ValidatePair.
i would probly leave it in my app for elder devices, but seems that ios 11 works without it. will need to redo session start handling tho', (i have different workflow that libimobile tools, and some stuff is running in paralel )
i still plan to check itunes communication.
not sending validatepair saves one roundtrip tho' 😄
Activity
nikias commentedon Jun 5, 2017
Haven't tried yet. Is
ideviceinfo -s
working? Any debug output with-d
?sohgoh commentedon Jun 6, 2017
Now I tried ideviceinfo command using iPhone 7 with iOS 11(15A5278f).
ideviceinfo -s
is working, but-d
is not.nikias commentedon Jun 6, 2017
You didn't compile libimobiledevice with debug support. Re-configure with
--enable-debug-code
.sohgoh commentedon Jun 6, 2017
I retry with
--enable-debug-code
.In the following the data of DeviceCertificate, HostCertificate, RootCertificate are deleted and EscrowBag and other ids are modified by me.
nikias commentedon Jun 6, 2017
Hmm the device just disconnects early as it seems. Apple changed something apparently.
nikias commentedon Jun 6, 2017
Can you try to run
idevicepair unpair
and paste the output ofidevicepair -d pair
?rcmpayne commentedon Jun 6, 2017
Same issue here on windows with iOS 11 beta. 10.3.3 is working without issue
libplist: 2.0.0
usbmuxd: 1.1.1
libusbmuxd: 1.1.0
git clone http://git.libimobiledevice.org/libimobiledevice.git
git pull
./autogen.sh
./configure --without-cython --enable-debug-code --prefix=/c/6.6.2017_debug
Make
Make install
sohgoh commentedon Jun 7, 2017
I tried. It seems to be successful.
sohgoh commentedon Jun 7, 2017
It seems that response failed at line 730 of lockdown.c and the response is returning with LOCKDOWN_E_ESCROW_LOCKED (-35).
Temporarily commenting out will make ideviceinfo successful.
nikias commentedon Jun 7, 2017
The ValidatePair request was removed from iOS lockdownd, so it doesn't understand it. It will return that the command is invalid.
Commenting that line in lockdown.c out will make it work when the device is already paired, yes. Since we need to keep backwards compatibility I need to work out a solution that works in all cases.
EliyahuStern commentedon Jun 7, 2017
How about:
nikias commentedon Jun 7, 2017
@EliyahuStern generally yes, just need to make sure the actual pairing works with the open source usbmuxd for a new pairing.
Even for < 11 it actually works without validatepair (since starting a session only works with a correct pairing).
mexmer commentedon Jun 7, 2017
@nikias just installed ios 11 beta little while ago, and found that my code is not working (early disconnect after validate pair), so i checked with libimobile and same issue.
then i decided to look at github, and see you are already working on it.
i still plan to do communication capture (with hardware usb monitor), since itunes for windows seems to be working with ios11 beta.
they might have something up in the sleeves, that makes seamless communication with old and new devices possible 🐱
nikias commentedon Jun 7, 2017
@mexmer as I said, ValidatePair is technically not required even for older devices. At some point IIRC it was required to gain trusted host status (
ideviceinfo -k TrustedHostAttached
), but at least on iOS 5.0.1 it istrue
without performing ValidatePair.mexmer commentedon Jun 7, 2017
i would probly leave it in my app for elder devices, but seems that ios 11 works without it. will need to redo session start handling tho', (i have different workflow that libimobile tools, and some stuff is running in paralel )
i still plan to check itunes communication.
not sending validatepair saves one roundtrip tho' 😄
55 remaining items