PythEch
commented
10 years ago I think I found the problem, half of these are assumptions though.
It seems openssl doesn't care about verification, and we forgot to include the 2nd certificate, the root certificate. ca.py doesn't generate this, unlike common/userpref.c, which is included in libimobiledevice.
idevice.c:
idevice_error_t idevice_connection_enable_ssl(idevice_connection_t connection)
{
if (!connection || connection->ssl_data)
return IDEVICE_E_INVALID_ARG;
idevice_error_t ret = IDEVICE_E_SSL_ERROR;
uint32_t return_me = 0;
#ifdef HAVE_OPENSSL
key_data_t root_cert = { NULL, 0 };
key_data_t root_privkey = { NULL, 0 };
userpref_error_t uerr = userpref_device_record_get_keys_and_certs(connection->udid, &root_privkey, &root_cert, NULL, NULL);
// it seems root private key and certificate are enough for openssl
[...]
#else
ssl_data_t ssl_data_loc = (ssl_data_t)malloc(sizeof(struct ssl_data_private));
/* Set up GnuTLS... */
debug_info("enabling SSL mode");
errno = 0;
gnutls_global_init();
gnutls_certificate_allocate_credentials(&ssl_data_loc->certificate);
gnutls_certificate_client_set_retrieve_function (ssl_data_loc->certificate, internal_cert_callback);
gnutls_init(&ssl_data_loc->session, GNUTLS_CLIENT);
gnutls_priority_set_direct(ssl_data_loc->session, "NONE:+VERS-SSL3.0:+ANON-DH:+RSA:+AES-128-CBC:+AES-256-CBC:+SHA1:+MD5:+COMP-NULL", NULL);
gnutls_credentials_set(ssl_data_loc->session, GNUTLS_CRD_CERTIFICATE, ssl_data_loc->certificate);
gnutls_session_set_ptr(ssl_data_loc->session, ssl_data_loc);
gnutls_x509_crt_init(&ssl_data_loc->root_cert);
gnutls_x509_crt_init(&ssl_data_loc->host_cert);
gnutls_x509_privkey_init(&ssl_data_loc->root_privkey);
gnutls_x509_privkey_init(&ssl_data_loc->host_privkey);
userpref_error_t uerr = userpref_device_record_get_keys_and_certs(connection->udid, ssl_data_loc->root_privkey, ssl_data_loc->root_cert, ssl_data_loc->host_privkey, ssl_data_loc->host_cert);
// but it needs everything with gnutls
[..]userpref.c:
static userpref_error_t userpref_device_record_gen_keys_and_cert(const char* udid)
{
userpref_error_t ret = USERPREF_E_SSL_ERROR;
key_data_t root_key_pem = { NULL, 0 };
key_data_t root_cert_pem = { NULL, 0 };
key_data_t host_key_pem = { NULL, 0 };
key_data_t host_cert_pem = { NULL, 0 };
debug_info("generating keys and certificates");
[...]
if (NULL != root_cert_pem.data && 0 != root_cert_pem.size &&
NULL != host_cert_pem.data && 0 != host_cert_pem.size)
ret = USERPREF_E_SUCCESS;
/* store values in config file */
userpref_device_record_set_keys_and_certs(udid, &root_key_pem, &root_cert_pem, &host_key_pem, &host_cert_pem);
// it generates everything, doesn't matter if system has openssl or gnutls
[...]I cannot use libimobiledevice.dll on my computer, for some reason it crashes with stack overflow. And there are UNIX socket problems on linux, so I need to find another script to generate these certificates.
Since ca.py doesn't generate the root certificate, I tried to use iTunes generated certificates, and it worked. Normally, when I want Python to verify the certificates generated by ca.py it gives this error:
Connecting to device: 0aa4cc366c959a9057b91b91b5e8e70c46d04057
Found pairing record for device 0aa4cc366c959a9057b91b91b5e8e70c46d04057
Error: Pairing failed!
_ssl.c:334: No root certificates specified for verification of other-side certif
icates.
Error: Unexpected error with mobile installation_proxy!
libapp instance has no attribute 'lockdown'#plist_service.py
def ssl_start(self, keyfile, certfile, ca_cert):
self.s = ssl.wrap_socket(self.s, keyfile, certfile, ca_certs=None, cert_reqs=ssl.CERT_REQUIRED, ssl_version=ssl.PROTOCOL_TLSv1)In original pymobiledevice, root certificate = host certificate:
pair_record = {"DevicePublicKey": plistlib.Data(self.DevicePublicKey),
"DeviceCertificate": plistlib.Data(DeviceCertificate),
"HostCertificate": plistlib.Data(certPem), #<--
"HostID": self.hostID,
"RootCertificate": plistlib.Data(certPem), #<--
"SystemBUID": "30142955-444094379208051516"
}
So with this way, I get this error:
Connecting to device: 0aa4cc366c959a9057b91b91b5e8e70c46d04057
Found pairing record for device 0aa4cc366c959a9057b91b91b5e8e70c46d04057
Error: Pairing failed!
[Errno 1] _ssl.c:507: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:ce
rtificate verify failed
Error: Unexpected error with mobile installation_proxy!
libapp instance has no attribute 'lockdown'def ssl_start(self, keyfile, certfile, ca_cert):
self.s = ssl.wrap_socket(self.s, keyfile, certfile, ca_certs=certfile, cert_reqs=ssl.CERT_REQUIRED, ssl_version=ssl.PROTOCOL_TLSv1)Setting caPem = pair_record["RootCertificate"].data and using that as:
cafile = writeHomeFile(HOMEFOLDER, self.identifier + "_ca.txt", caPem)
self.c.ssl_start(sslfile, sslfile, cafile)def ssl_start(self, keyfile, certfile, ca_cert):
self.s = ssl.wrap_socket(self.s, keyfile, certfile, ca_certs=ca_cert, cert_reqs=ssl.CERT_REQUIRED, ssl_version=ssl.PROTOCOL_TLSv1)works.
alexhulbert
So apparently there was a python implementation of libimobiledevice here: pymobiledevice
It is written in Python meaning that you won't even need to compile it as that is an interpreted langauge. Downside is, we need to use PyInstaller for Windows distribution because Python is not included in Windows, unlike Mac and Linux.
Anyways, if you don't want cross-language development (in other words, if you want just pure Java), we can look at that code and use it as reference to figure out how mobile installation_proxy is used. Since Python is a high-level language, it'll be easier to understand how things can be ported to Java.
I did those on a Windows machine, though it is relatively easier to get this done on Unix.
Requirements: Python 2.7 M2Crypto Construct
After the installation, head over to pymobiledevice and download the zip package. Extract pymobiledevice-master to C:\Python27 rename it to something like pymobiledevice otherwise Python will give syntax error. After that, fire up IDLE (Python GUI) from Start.
Now welcome to the Python Shell. You'd be surprised because all we need is 3 lines of code:
Or you can just: