15feded162
which is the maximum allowed in RFC 3550: The last octet of the padding contains a count of how many padding octets should be ignored, including itself SRTP encryption does not need to be taken into account since none of the cipher suites used by WebRTC require padding: https://www.rfc-editor.org/rfc/rfc3711#section-3.1 https://www.rfc-editor.org/rfc/rfc7714#section-7.2 BUG=webrtc:15182 Change-Id: Ife3d264af389509733699f2dd4d32ba63793e9de Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/305642 Reviewed-by: Per Kjellander <perkj@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Philipp Hancke <phancke@microsoft.com> Cr-Commit-Position: refs/heads/main@{#40101}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation