Hi, I have been using this SDK recently, though after testing it a bit further a problem was encountered where an application depending on the SDK crashes while attempting to initialize OpenSSL when running in Ubuntu 22.04. It works fine on my Fedora 38 system, however.
I found that this is caused by libwebrtc-sys statically linking in BoringSSL code which conflicts with the dynamically linked OpenSSL symbols that other crates in the same application depend on. Furthermore, attempting to enable the various "vendored" features in other TLS provider crates will result in the application failing to link due to conflicting symbol names. I was able to get around the problem by modifying libwebrtc's build in a few places to prevent it from building any BoringSSL code, allowing for openssl-sys to fill that dependency. Are there any plans to un-bundle the TLS library from libwebrtc-sys or prevent the private symbols in libwebrtc from reaching outside of the libwebrtc-sys crate?
Hi, I have been using this SDK recently, though after testing it a bit further a problem was encountered where an application depending on the SDK crashes while attempting to initialize OpenSSL when running in Ubuntu 22.04. It works fine on my Fedora 38 system, however.
I found that this is caused by libwebrtc-sys statically linking in BoringSSL code which conflicts with the dynamically linked OpenSSL symbols that other crates in the same application depend on. Furthermore, attempting to enable the various "vendored" features in other TLS provider crates will result in the application failing to link due to conflicting symbol names. I was able to get around the problem by modifying libwebrtc's build in a few places to prevent it from building any BoringSSL code, allowing for openssl-sys to fill that dependency. Are there any plans to un-bundle the TLS library from libwebrtc-sys or prevent the private symbols in libwebrtc from reaching outside of the libwebrtc-sys crate?