CryptoOptions: add boolean to prefer SRTP GCM cipher suites When prefer_gcm_crypto_suites is set, GCM crypto suites are listed before kSrtpAes128CmSha1_80 in the SRTP cipher preference order, so GCM is selected whenever both peers support it. Based on Threema's patch: https://github.com/threema-ch/webrtc-build-docker/blob/master/patches/srtp-cipher-suites.patch Co-Authored-by: lgr@threema.ch Bug: webrtc:42221827 Change-Id: Ia513c84d94fffa51c530f49d1de61932059ad62d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/474280 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Cr-Commit-Position: refs/heads/main@{#47780}
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.