Philipp Hancke 2ebbff83ee do not offer gcm as the preferred cipher suite ... Move the GCM srtp cipher suites below the default SRTP_AES128_CM_SHA1_80 one. This will not negotiate them by default since they have an impact on packet overhead for audio-only calls. GCM can still be negotiated if the peer offers it as preferred cipher suite or answers with just that cipher suite. BUG=chromium:713701 Change-Id: I79bd4ab827e5c7f55f5550d14db3f4217a7eff86 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/158404 Reviewed-by: Justin Uberti <juberti@google.com> Reviewed-by: Justin Uberti <juberti@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Justin Uberti <juberti@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29672}		2019-10-31 20:59:42 +00:00
..
BUILD.gn	Use source_sets in component builds and static_library in release builds.	2019-10-17 21:17:18 +00:00
crypto_options.cc	do not offer gcm as the preferred cipher suite	2019-10-31 20:59:42 +00:00
crypto_options.h	do not offer gcm as the preferred cipher suite	2019-10-31 20:59:42 +00:00
frame_decryptor_interface.h	Reland "Refactor FrameDecryptorInterface::Decrypt to use new API."	2019-04-09 20:08:56 +00:00
frame_encryptor_interface.h	(4) Rename files to snake_case: update BUILD.gn, include paths, header guards, and DEPS entries	2019-01-11 17:11:39 +00:00