aac19d3136
These tests were failing when building WebRTC against OpenSSL instead of BoringSSL. The reason is that OpenSSLStreamAdapter::SSLVerifyCallback in the BoringSSL mode returns the full cert_chain by calling SSL_get0_peer_certificates. This API does not exist in OpenSSL, instead only a single certificate is fetched via X509_STORE_CTX_get0_cert. ifdef out the parts of the test that assert on cert[1] and cert[2]. An alternative but more involved way to fix these tests could be to use X509_STORE_CTX_get1_chain to fetch the full chain on the OpenSSL path. Bug: webrtc:15153 Change-Id: I1ede6a3c5a63d4afd2de849f5e44fcd67592aa3c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/304400 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Mirko Bonadei <mbonadei@webrtc.org> Cr-Commit-Position: refs/heads/main@{#40022}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation