release.mozilla.org uses an invalid security certificate. The certificate is only valid for the following names: *.github.com, github.com, *.github.io 1:45 PM <KWierso> from #security : 1:45 PM <KWierso> 1:41 PM <mancha> https://release.mozilla.org is broken, btw. 1:45 PM <KWierso> 1:42 PM <mancha> CN=*.github.com and SAN: *.github.com, github.com, *.github.io 1:45 PM <KWierso> w0ts0n, fox2mike: I saw you both in the conversation about nightly.m.o the other day, care to look at this too? 1:46 PM <KWierso> or escalate/redirect as needed :) 1:48 PM <@pir> KWierso: I'm told that would be release management, sylvester's team 1:51 PM <KWierso> doubt sylvestre's around at this hour on a friday... maybe ritu's still around? 1:52 PM <@pir> I'd file a bug. It doesn't seem to be an urgent problem 1:52 PM <@pir> it's pointing to githug so uses github's ssl certs 1:52 PM <@pir> github 1:53 PM <ritu> KWierso: is this a prod-details change? 1:53 PM <ritu> which broke it 1:54 PM <@w0ts0n> howdy 1:54 PM <ritu> jgmize: ping, can you help figure out why release.m.o is broken or how to fix it? i can help from relman side
Summary: https://release.mozilla.org/is giving Insecure Connection errors → https://release.mozilla.org/ is giving Insecure Connection errors
GitHub Pages still doesn't allow us to use our own certificate, so we have to work around the issue. 1. Use CloudFlare https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/ 2. Change the platform to WordPress like other Mozilla blogs (and use the same theme) 3. Any other solution?
Actually www.bugzilla.org, which also uses GitHub Pages now, fixed the issue today with 1. See Bug 1398162.
There is no current way to host this on github and have a valid SSL cert without using a proxy server, and Cloudflare won't do that for free unless you delegate the root nameservers for the entire DNS zone (i.e. for mozilla.org itself). Mozilla isn't going to do that with one of their primary DNS zones. Bugzilla got away with it because it's a community project.
This is being worked on in 1357118
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1357118
You need to log in before you can comment on or make changes to this bug.