After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 774465 - bugzilla.gnome.org's https not trusted by Chrome Version 54.0.2840.99 m
bugzilla.gnome.org's https not trusted by Chrome Version 54.0.2840.99 m
Status: RESOLVED FIXED
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: general
unspecified
Other Windows
: Normal normal
: Bugzilla 4.4
Assigned To: Andrea Veri
Bugzilla Maintainers
Depends on: 772897
Blocks:
 
 
Reported: 2016-11-15 11:04 UTC by sander.jonkers
Modified: 2016-11-16 10:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sander.jonkers 2016-11-15 11:04:50 UTC 
Disclaimer: this is about bugzilla.gnome.org, but that FQDN is not in the "Component" list of bugzilla. So bugzilla does not allow bugs about itself ... ;-)

https://bugzilla.gnome.org/ is not trusted by Chrome Version 54.0.2840.99 m: 

"This page is insecure (broken HTTPS).

SHA-1 Certificate
The certificate for this site expires in 2017 or later, and the certificate chain contains a certificate signed using SHA-1."

I'm not sure, but the cause might also be related to StartCom in the chain of trust.
Comment 1 Tom Tryfonidis 2016-11-15 11:37:55 UTC 
Assigning this to bugzilla.gnome.org product.
Comment 2 Andrea Veri 2016-11-15 12:35:08 UTC 
On it, that's one of 3 services that are still using a Startcom certificate. (account.gnome.org, status.gnome.org, bugzilla.gnome.org)
Comment 3 Andrea Veri 2016-11-15 14:50:16 UTC 
This should be fixed.
Comment 4 sander.jonkers 2016-11-16 10:49:35 UTC 
Indeed: Chrome now trusts https://bugzilla.gnome.org/ again.

That was quick. Thank you.