commit | 7e6290d1d25e3e113e95f87dd62d8e16e51d59de | [log] [tgz] |
---|---|---|
author | Sam Zackrisson <saza@webrtc.org> | Thu Dec 10 07:55:28 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Dec 10 07:55:40 2020 |
tree | d0a4d7309ef1a4948623f119661a65497965f482 | |
parent | 72f638a9a279e7abb5534fa66a0ade2cf18ec1a7 [diff] |
Revert "Use CRYPTO_BUFFER APIs instead of X509 when building with BoringSSL." This reverts commit 72f638a9a279e7abb5534fa66a0ade2cf18ec1a7. Reason for revert: downstream build failures Original change's description: > Use CRYPTO_BUFFER APIs instead of X509 when building with BoringSSL. > > Using CRYPTO_BUFFERs instead of legacy X509 objects offers memory and > security gains, and will provide binary size improvements as well once > the default list of built-in certificates can be removed; the code > dealing with them still depends on the X509 API. > > Implemented by splitting openssl_identity and openssl_certificate > into BoringSSL and vanilla OpenSSL implementations. > > Bug: webrtc:11410 > Change-Id: Idc043462faac5e4ab1b75bedab2057197f80aba6 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/174120 > Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> > Reviewed-by: David Benjamin <davidben@webrtc.org> > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Commit-Queue: Taylor <deadbeef@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#32811} TBR=deadbeef@webrtc.org,mbonadei@webrtc.org,davidben@webrtc.org,hta@webrtc.org Change-Id: Ib5e55cb5798a2f3d25a4460f5311d2e650d3fa82 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:11410 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/196742 Reviewed-by: Sam Zackrisson <saza@webrtc.org> Commit-Queue: Sam Zackrisson <saza@webrtc.org> Cr-Commit-Position: refs/heads/master@{#32812}
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.
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.