commit | 8e545eee1e725cb50fb78dbcba22b4de0d1bc629 | [log] [tgz] |
---|---|---|
author | Tommi <tommi@webrtc.org> | Thu Feb 08 16:25:20 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 08 16:25:31 2018 +0000 |
tree | 4e4d11f3f7a2909dfa644db378b2e60df29090d3 | |
parent | 2018823a685f0b233e68fc21e1fa3304d4b9f352 [diff] |
Revert "Use SRTP_AES128_CM_SHA1_80 by default instead of SRTP_AES128_CM_SHA1_32." This reverts commit 6780c51b23516803dc27173d10ba98d018780447. Reason for revert: More details in crbug.com/810292 Original change's description: > Use SRTP_AES128_CM_SHA1_80 by default instead of SRTP_AES128_CM_SHA1_32. > > A field has been added to "CryptoOptions" to enable SRTP_AES128_CM_SHA1_32 > from native apps if really necessary. > > R=​deadbeef@webrtc.org > > Bug: webrtc:7670 > Change-Id: I36b6ab3e302fbf3cda2611ff196757e43a56e704 > Reviewed-on: https://webrtc-review.googlesource.com/41420 > Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> > Reviewed-by: Magnus Jedvert <magjed@webrtc.org> > Commit-Queue: Joachim Bauch <jbauch@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#21952} TBR=deadbeef@webrtc.org,magjed@webrtc.org,jbauch@webrtc.org Change-Id: I643dbe023eca526f2cda4d97df045f2533741dd4 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:7670 Reviewed-on: https://webrtc-review.googlesource.com/49880 Reviewed-by: Tommi <tommi@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21961}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.