Closed
Bug 823684
Opened 12 years ago
Closed 11 years ago
SRTP_AES128_CM_HMAC_SHA1_32 deviating from RFC
Categories
(Core :: WebRTC: Networking, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 829624
People
(Reporter: martin, Unassigned)
Details
(Whiteboard: [WebRTC], [blocking-webrtc-])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20121220 Firefox/20.0
Build ID: 20121220030912
Steps to reproduce:
Do a WebRTC PeerConnection to a peer that only advertises/accepts SRTP_AES128_CM_HMAC_SHA1_32 in the DTLS handshake.
Actual results:
Mozilla sends data where both RTP and RTCP packets have 32 bit HMAC checksums.
Expected results:
According to http://tools.ietf.org/html/rfc5764#section-4.1.2, SRTP_AES128_CM_HMAC_SHA1_32 should have 80 bit checksums for RTCP (while it has 32 bit checksums for RTP).
|
||
Updated•12 years ago
|
Whiteboard: [WebRTC], [blocking-webrtc-]
|
Reporter | |
Comment 1•12 years ago
|
||
FWIW, Chrome (which implements DTLS-SRTP in the latest canary) implements SRTP_AES128_CM_HMAC_SHA1_32 correctly according to the spcec, with 80 bit HMAC for RTCP.
|
||
Comment 2•11 years ago
|
||
Resolved shortly after the last comment here in bug 829624
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•