Implement the sequence for downloading the OpenH264 plugin (upon update or install), including signature verification, etc
The behavior that's needed here is as follows: - When Firefox is initially installed, it needs to download OpenH264 immediately. - Firefox needs to periodically check with Cisco's servers for updates for OpenH264. - Whenever a version of OpenH264 is downloaded, we need to check a digital signature on the binary and not install it if it doesn't verify. - There needs to be a button that lets you disable the module. - If no version of OpenH264 is installed or someone has disabled it, we need to just detect that case and not offer H.264.
As noted in prior emails, I believe strongly that we ought to be using Mozilla domain names at least to check for updates, if not Mozilla servers. But I still haven't seen the complete spec about how all this is going to be deployed and QAed, which makes me think this is not yet ready for implementation.
Bug 999721 - Implement OpenH264 Signing opened as separate bug from this one. Likely another person/3rd party will do the signing implementation. Bug 985255 (this bug) covers download, verify, install, and update.
Component: WebRTC → Firefox Operations
Product: Core → Tracking
Summary: Implement OpenH264 download → Breakdown: Implement OpenH264 download
Version: unspecified → ---
What's the next step here, and who's working on it?
Assignee: nobody → benjamin
Whiteboard: [p=0, est:0d, s=fx32, c=webrtc] → p=5
Status: NEW → ASSIGNED
Whiteboard: p=8 → p=8 s=it-32c-31a-30b.2 [qa?]
Whiteboard: p=8 s=it-32c-31a-30b.2 [qa?] → p=8 s=it-32c-31a-30b.2 [qa-]
Whiteboard: p=8 s=it-32c-31a-30b.2 [qa-] → p=8 s=it-32c-31a-30b.3 [qa-]
Bug 1013354 resolved to the point where we have a plan. Woot.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.