| commit | 318166bed75dcbc00a7b79f715f9953aff9ffbc7 | [log] [tgz] |
|---|---|---|
| author | guoweis <guoweis@webrtc.org> | Wed Nov 18 19:03:38 2015 -0800 |
| committer | Commit bot <commit-bot@chromium.org> | Thu Nov 19 03:03:46 2015 +0000 |
| tree | ae81fa7e63a929c004ec71cfcaca0b7a59b83611 | |
| parent | 2764e1027a08a5543e04b854a27a520801faf6eb [diff] |
Revert of Convert internal representation of Srtp cryptos from string to int. (patchset #10 id:180001 of https://codereview.webrtc.org/1416673006/ ) Reason for revert: Broke chromium fyi build. Original issue's description: > Convert internal representation of Srtp cryptos from string to int. > > Note that the coversion from int to string happens in 3 places > 1) SDP layer from int to external names. mediasession.cc GetSupportedSuiteNames. > 2) for SSL_CTX_set_tlsext_use_srtp(), converting from int to internal names. > 3) stats collection also needs external names. > > External names are like AES_CM_128_HMAC_SHA1_80, specified in sslstreamadapter.cc. > Internal names are like SRTP_AES128_CM_SHA1_80, specified in opensslstreamadapter.cc. > > The conversion from string to int happens in one place only, SDP layer, SrtpFilter::ApplyParams(). > > BUG=webrtc:5043 > > Committed: https://crrev.com/2764e1027a08a5543e04b854a27a520801faf6eb > Cr-Commit-Position: refs/heads/master@{#10701} TBR=juberti@webrtc.org,pthatcher@webrtc.org,juberti@google.com NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5043 Review URL: https://codereview.webrtc.org/1455233005 Cr-Commit-Position: refs/heads/master@{#10702}
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. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.