| commit | a5b0dcd0865b6c997327b83e12a291e3aaa7e8e5 | [log] [tgz] |
|---|---|---|
| author | Jonas Oreland <jonaso@webrtc.org> | Wed Apr 09 10:08:56 2025 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 09 11:29:08 2025 |
| tree | 7edfe1a3d343cf6c437c6963028e6eab8b3f28f9 | |
| parent | 3904780df0af17e96389f9e3b3ce32c2fca8bdf9 [diff] |
dtls-in-stun: Prepare for multi packet handshakes 1) Change format of ACK attribute to be hash of packet (crc32). this is good since we anyway can't retransmit parts of DTLS packet and it also works for the encrypted handshake packages. This change is "somewhat upgrade" compatible, version prior to this does not actually check/use the content of the ack attribute, only the presence. This version will automatically clear pending packets when a new flight begins => It works, but retransmit of 1 packet in a multi placket flight does not unless both ens has this version....But multi packet handshake flight are not yet "in play" 2) Keep track of individually acked packets. Clear array of pending when getting an ACK. This is "already today" and improvment of existing code. 3) Limit size of ACK to 4 packets, this limit *should* never be reached...but there is a test for it :) 4) Readd restrictions removed in https://webrtc-review.googlesource.com/c/src/+/381102. It only worked "by accident", and the use case is of zero value. Even hard to explain! Maybe I'll take a stab after PQC is done. --- With this, PQC handshake _almost_ work with dtls-in-stun. BUG=webrtc:367395350 Change-Id: I582397babb099896ba56ef26e174f47f7e98d1d9 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/385401 Commit-Queue: Jonas Oreland <jonaso@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/main@{#44340}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.