Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Could not connect to lockdownd: SSL error (-5) #1518

Open
gotname opened this issue Dec 27, 2023 · 4 comments
Open

ERROR: Could not connect to lockdownd: SSL error (-5) #1518

gotname opened this issue Dec 27, 2023 · 4 comments

Comments

@gotname
Copy link

gotname commented Dec 27, 2023

I am encountering this SSL error -5 issue, and the situation is as follows:
Occasionally, it takes two clicks on "Trust" to establish a connection.
After clicking "Trust" for the first time, an SSL error (-5) occurs.
I need to unplug the phone, plug it in again, and click "Trust" again for everything to work normally.
There is approximately a 40% chance of encountering the SSL error after the first "Trust" click.

When the error occurs, I checked the pairing list, and the device is listed !
Operating Environment: Windows
Versions Used: 1.3.0-174-g9a5e78f, 1.2 - both versions encounter this issue
Tested Devices:
iPhone 7 iOS 13.3.1 (Activated, password-protected, unlocked)
iPhone 11 iOS 15.4 (Activated, no password protection, unlocked)
I believe this issue might occur with other devices or systems.
SSL Version: 1.1.0e
Both "pair" and "unpair" commands fail when the error occurs.
Screenshots of cmd commands in Windows are provided below. Does anyone know where the issue might be, and how to fix it?

-5

@mexmer
Copy link

mexmer commented Jan 1, 2024

on windows libimobiledevice tools use applemobiledeviceservice that is shipped with itunes update/reinstall itunes and check if issue still persists.

@gotname
Copy link
Author

gotname commented Jan 2, 2024

@mexmer
I have tried updating/reinstalling iTunes, but the issue still persists. However, I've noticed that when the SSL error (-5) occurs, doing nothing and simply launching the third-party app 3uTools resolves the problem, and the phone being reported with an error is automatically recognized as normal.

@mexmer
Copy link

mexmer commented Jan 2, 2024

3utools internally use libimobilevice. maybe there is issue with openSSL version. we are using 1.1.1q and never observed this issue.

@AiXanadu
Copy link
Contributor

My solution is to use a third-party process (https://github.com/libxcc/xcc-rundll) to call the connection function and time out for 5 seconds.
Then wait for it to end in the main program. If it connects successfully, we will connect normally. If it times out for 5 seconds without connecting. Then an SSL error is returned, and we wait (about 3 seconds) to start the process again to connect.
This ensures that when we actually connect, we won't get an SSL error, which can take a long time to return.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants