Closed
Bug 1498068
Opened 7 years ago
Closed 7 years ago
SRTP_AEAD_AES_128_GCM failed to connect
Categories
(Core :: WebRTC: Networking, enhancement, P2)
Core
WebRTC: Networking
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: drno, Assigned: drno)
Details
Attachments
(2 files)
No description provided.
| Assignee | ||
Updated•7 years ago
|
Assignee: nobody → drno
Priority: -- → P2
| Assignee | ||
Comment 1•7 years ago
|
||
Pushed by nohlmeier@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/62f5e5f579e7
fixed SRTP key length assertion for GCM 128 bit. r=mt
Comment 3•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•7 years ago
|
Flags: qe-verify-
Comment 4•7 years ago
|
||
pcap showing SRTP_AEAD_AES_128_GCM being used with an SFU that only offers this ciphersuite. The srtp profile can be seen in the DTLS server hello in either packet #77 or #84
Thank you Nils!
You need to log in
before you can comment on or make changes to this bug.
Description
•