We've recently switched Ruffle from rustls to the platform-native backend, for code size considerations: ruffle-rs/ruffle#23894
Then we had to allow switching back to rustls, because we didn't want to build/ship OpenSSL for Android: ruffle-rs/ruffle#23947
At fist, we tried to keep it using native certificate roots, but apparently that just silently doesn't work on Android: ruffle-rs/ruffle-android#788
So now we're moving back the Android build to rustls with bundled cert roots: ruffle-rs/ruffle#24218
So, the natural question is - would it be possible to instead make use of Android's own TLS facilities, like SSLEngine and SSLSocket through JNI?
I realize that rustls seems to be preferred nowadays, with it being the default in 0.13, but again: we'd like to keep binary size low where possible.
Don't know if this issue would be more appropriate to ask over at https://github.com/rust-native-tls/rust-native-tls, pardon me...
We've recently switched Ruffle from rustls to the platform-native backend, for code size considerations: ruffle-rs/ruffle#23894
Then we had to allow switching back to rustls, because we didn't want to build/ship OpenSSL for Android: ruffle-rs/ruffle#23947
At fist, we tried to keep it using native certificate roots, but apparently that just silently doesn't work on Android: ruffle-rs/ruffle-android#788
So now we're moving back the Android build to rustls with bundled cert roots: ruffle-rs/ruffle#24218
So, the natural question is - would it be possible to instead make use of Android's own TLS facilities, like
SSLEngineandSSLSocketthrough JNI?I realize that rustls seems to be preferred nowadays, with it being the default in 0.13, but again: we'd like to keep binary size low where possible.
Don't know if this issue would be more appropriate to ask over at https://github.com/rust-native-tls/rust-native-tls, pardon me...