Closed Bug 795440 Opened 12 years ago Closed 12 years ago

We need a separate SSL CDN to deliver the stub installer

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: melissa, Assigned: nmaul)

References

Details

This is an item from the stub installer meeting
To clarify: "firefox-latest" is what the stub installer itself downloads, and the stub installer will cryptographically verify its integrity. Therefore firefox-latest does *not* need to be delivered over SSL. Nice to have, but not really helpful from a security standpoint (and costs more money). However, we *do* need an SSL CDN to deliver the stub installer itself. This is the heart of this bug. See also bug 795439, which is about adding SSL support to bouncer, and bug 795443 which is about changing the links on www.mozilla.org to point to SSL-bouncer. An additional bug should be filed to have www.mozilla.org itself (at least pages with a download button) served over SSL-only.
See Also: → 795439, 795443
Summary: We need a separate SSL CDN to deliver the firefox-latest links → We need a separate SSL CDN to deliver the stub installer
Blocks: 796103
Blocks: 795441
Jake: Can we close this?
Yep.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified; the team (Webprod, IT, Web QA, releng) vetted this functionality on Friday.
Status: RESOLVED → VERIFIED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.