zqz/platform-external-webrtc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

By default, don't use SRTP_AES128_CM_SHA1_32 protection profile.

Browse Source 
This profile will now not be used unless the application explicitly
sets the flag in CryptoOptions to true. As a result, an 80-bit
authentication tag will be used instead of a 32-bit one. See bug for
more details.

Bug: webrtc:7670
Change-Id: I7c0a118fd7b1e7aac23b9eb8717099f055de0441
Reviewed-on: https://webrtc-review.googlesource.com/66600
Reviewed-by: Benjamin Wright <benwright@webrtc.org>
Reviewed-by: Peter Thatcher <pthatcher@webrtc.org>
Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#22757}
This commit is contained in:
Taylor Brandstetter
2018-04-03 16:29:26 -07:00
committed by Commit Bot
parent c8b90aabd5
commit fd350d74ee
6 changed files with 50 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
pc/peerconnectioninterface_unittest.cc
View File

@ -403,7 +403,7 @@ static const char kDtlsSdesFallbackSdp[] =
"a=fingerprint:sha-1 "
"4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB\r\n"
"a=setup:actpass\r\n"
"a=crypto:1 AES_CM_128_HMAC_SHA1_32 "
"a=crypto:0 AES_CM_128_HMAC_SHA1_80 "
"inline:NzB4d1BINUAvLEw6UzF3WSJ+PSdFcGdUJShpX1Zj|2^20|1:32 "
"dummy_session_params\r\n";