Open Bug 1491583 Opened 2 years ago Updated 1 year ago
Can we remove the SRTP
_AES128 _CM _HMAC _SHA1 _32 cipher
We want to figure out when we can remove the SRTP_AES128_CM_HMAC_SHA1_32 from Firefox SRTP inside WebRTC.
Preliminary data after 13 days https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2018-10-02&include_spill=0&keys=__none__!__none__!__none__&max_channel_version=nightly%252F64&measure=WEBRTC_SRTP_CIPHER&min_channel_version=nightly%252F57&processType=*&product=Firefox&sanitize=0&sort_keys=submissions&start_date=2018-09-20&table=0&trim=1&use_submission_date=0 Surprising 3% use of SRTP_AES128_CM_HMAC_SHA1_32 in the Nightly channel. Lets wait how this evolves in the Beta channel, but so far it doesn't look like we can remove this without causing interop issues.
Well, maybe. The problem is the other side might support 80 bit MACs but prefer 32. Not sure how to measure that, though
We could record new telemetry that splits by role: as a server, we won't pick 32.
We could, but that just tells us who prefers 32, not who would fail if we did not offer it.
You need to log in before you can comment on or make changes to this bug.