Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
Since LibreSSL 3.6.0 SSL_CTX_set_security_level() has been available.
|
|
In LibreSSL >= 3.5.0 many structs are defined as opaque as they are in
OpenSSL 1.1.
|
|
|
|
This allows the same connection to be used again after sbservices_set_icon_state is called.
Fixes #928.
|
|
Detect if we're talking to iOS 1 `if (connection->device->version == 0)`
and set `SSL_CTX_set_min_proto_version(ssl_ctx, 0);` to support SSL3.
iOS 1 doesn't understand TLS1_VERSION, it can only speak SSL3_VERSION.
However, modern OpenSSL is usually compiled without SSLv3 support.
So if we set min_proto_version to SSL3_VERSION on an OpenSSL instance which doesn't support it,
it will just ignore min_proto_version altogether and fall back to an even higher version.
To avoid accidentally breaking iOS 2.0+, we set min version to 0 instead.
|
|
flags across Makefiles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BundleIDs are passed as an array so we need to make sure it gets added as such.
In fact though we just copy the node from the va_arg :)
|
|
|
|
OpenSSL versions pre 3.0 do not define OPENSSL_VERSION_MAJOR etc.
|
|
Thanks @tihmstar for pointing this out.
|
|
Turns out that SSL_CTX_set_options does *not* clear options that
have been set before.
|
|
A logical bug did prevent parsing the 'Error' node since the code
path is never reached when a 'Result' node is found first. This
is mitigated by always checking for the 'Error' node first.
|
|
versions
|
|
The free would cause a use-after-free when the plist is later freed, which
eventually ends up in a crash.
Thanks @TrungNguyen1909 for catching this.
|
|
|
|
|
|
Due to an implementation detail from the past, a call to idevice_event_unsubscribe
would not cause the callback function to be called with IDEVICE_DEVICE_REMOVE
events, even though originally it was planned to be that way.
Due to the internal changes for the newer idevice_events_subscribe/unsubscribe
API, that behavior changed and it would call the callback.
Now to not break current software implementations depending on the original
behavior we modify the old API to behave the same as before the change.
|
|
Synchronous modes for `instproxy_install`, `instproxy_upgrade`, `instproxy_uninstall`, `instproxy_archive`, `instproxy_restore`, and `instproxy_remove_archive` appear to be ignoring the documented behavior that “If NULL is passed, this function will run synchronously”.
This commit fixes the advertised behavior.
|
|
The older API idevice_event_subscribe/unsubscribe can only be used
by a single instance. With the addition of a context, is is now possible
to register multiple callback functions in different threads.
For backwards compatibility the old API will still be available for a while
before being removed in a future release.
|
|
|
|
|
|
|
|
|
|
In sync with idevice_from_mux_device, line 384.
Without this fix, data size 128 (the common value) is treated as -128, resulting in incorrect allocation.
Related to #1248 but doesn't fully fix it.
|
|
|
|
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
Found with bugprone-suspicious-string-compare
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
Found with bugprone-macro-parentheses
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
Found with readability-non-const-parameter
Signed-off-by: Rosen Penev <rosenp@gmail.com>
|
|
|
|
Currently if 0 byte gets sent, it is treated as not-enough-data.
This is wrong, because with TCP, 0-byte-sent usually means the
receiver end is closed. We must set a new case for this and must
not normalize the sent-bytes to 0 in general.
|
|
functions
This allows for custom service implementations to easier switch to non-plist
communication after the service has been started.
|
|
|
|
|
|
simplify the code
|
|
|
|
|
|
debugserver_client_handle_response
|
|
|
|
Windows
|
|
|