Closed
Bug 1167066
Opened 9 years ago
Closed 9 years ago
No sound WebRTC audio for sites that don't use perfect forward secrecy
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: alice0775, Unassigned)
References
Details
(Keywords: regression)
When I test Bug 1166937, I notice the problem This does not heppen on 39.0. Steps To Reproduce: 1) Connect to a phone conference bridge via WebRTC/JsSIP using the following url demo which is provided by Bug 1166937's author. http://www.felonyflats.com/ffdemo/ 2) After allowing browser access to the microphone, you will connect to the conference, hear an audio message about an invalid conference ID, then be disconnected. Actual Results: No sound Expected Results: An audio message should be playing
Reporter | ||
Comment 1•9 years ago
|
||
Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=87fe5bc1233f&tochange=47d9e690f4a9 Triggered by: 47d9e690f4a9 Martin Thomson — Bug 1052610 - Disabling non-PFS cipher suites, r=ekr Fixed range in beta channel(38beta cycle) https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=d133698337aa&tochange=286ae47a6018 Fixed by(38beta cycle)) d10817faa571 Martin Thomson — Bug 1158343 - Temporarily enable TLS_RSA_WITH_AES_128_CBC_SHA for WebRTC. r=ekr, a=sledru
Reporter | ||
Comment 2•9 years ago
|
||
[Tracking Requested - why for this release]:
tracking-firefox40:
--- → ?
tracking-firefox41:
--- → ?
Comment 4•9 years ago
|
||
This is not a tracking issue. We announced this change https://hacks.mozilla.org/2015/02/webrtc-requires-perfect-forward-secrecy-pfs-starting-in-firefox-38/ but made a temporary allowance for 38 to give sites another cycle to adjust.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(martin.thomson)
Resolution: --- → WONTFIX
Comment 5•9 years ago
|
||
Martin, does this mean people will only see/notice this behavior for the first time in 39? In that case, what do you think about writing a release note explaining that it's a known issue? Or relnoting it as a security fix. Maire, what do you think?
Flags: needinfo?(mreavy)
Flags: needinfo?(martin.thomson)
Comment 6•9 years ago
|
||
This has been on pre-release channels for ages now. And we always encourage WebRTC developers to use Nightly or Aurora because things are still in flux. It shouldn't be a surprise (though for some, inevitably, it will be). Release notes seem appropriate though. WebRTC now requires perfect forward secrecy [https://bugzilla.mozilla.org/show_bug.cgi?id=996237, https://hacks.mozilla.org/2015/02/webrtc-requires-perfect-forward-secrecy-pfs-starting-in-firefox-38/
Flags: needinfo?(martin.thomson)
Comment 7•9 years ago
|
||
Release Note Request (optional, but appreciated) [Why is this notable]: This will be noticeable on release for the first time. [Suggested wording]: WebRTC now requires perfect forward secrecy [Links (documentation, blog post, etc)]: https://hacks.mozilla.org/2015/02/webrtc-requires-perfect-forward-secrecy-pfs-starting-in-firefox-38/ This isn't an ideal bug to inspire this release note, but it's also a little unclear which would be better. Maybe bug 1158343, where there are some notes on issues with Facebook.
relnote-firefox:
--- → ?
Comment 8•9 years ago
|
||
Martin, if bug 1158343 temporarily re-enabled this, where was this undone? What bug number? We should probably follow up to test if Facebook fixed what we thought they might have by now.
Flags: needinfo?(martin.thomson)
Comment 9•9 years ago
|
||
Liz and I talked on IRC; we've communicated this a bunch, and we'll relnote it.
Flags: needinfo?(mreavy)
Comment 10•9 years ago
|
||
Liz, bug 1158343 was a selective uplift only, backing out one change for 38 only. Later branches didn't receive the fix. There's no code change required to keep 39+ on PFS-only.
Flags: needinfo?(martin.thomson)
Comment 11•9 years ago
|
||
Wontfix since FF only supports sites that use PFS for WebRTC.
Updated•9 years ago
|
Summary: No sound WebRTC audio → No sound WebRTC audio for sites that don't use perfect forward secrecy
Release note added to Firefox 41.0a2
You need to log in
before you can comment on or make changes to this bug.
Description
•