New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 686229 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

ERR_CERT_AUTHORITY_INVALID on a single website after Chrome updated to 56.0.2924.76

Reported by burning....@gmail.com, Jan 27 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36

Steps to reproduce the problem:
1. Open https://natalia-moroz.ru

What is the expected behavior?
Website loaded

What went wrong?
Chrome shows ERR_CERT_AUTHORITY_INVALID error.

Did this work before? Yes 55.x

Chrome version: 56.0.2924.76  Channel: stable
OS Version: Ubuntu 16.04
Flash Version: Shockwave Flash 24.0 r0

I can open https://metrocom-chat.bsrealm.net which is hosted on the same web server and has identical SSL certificate. This is a mystery. Tested under Ubuntu 16.04, 16.10 and Windows 10 on two different laptops.
 
Cc: lgar...@chromium.org
Components: UI>Browser>Interstitials
Labels: M-56 OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on latest Chrome Stable ie., 56.0.2924.76 on Windows(7,10), Mac and Linux.


note : working on the regression once confirmed will update the bisect range.

Comment 2 Deleted

Components: Internals>Network>Certificate
Status: WontFix (was: wong)
natalia-moroz.ru is using a certificate issued by StartCom after October 21, 2016.

StartCom certificates issued after that date are no longer trusted:
https://security.googleblog.com/2016/10/distrusting-wosign-and-startcom.html

(The cert for metrocom-chat.bsrealm.net  was issued on October 9.)
Note that metrocom-chat.bsrealm.net will stop working in M57, as part of the ongoing move to distrust all certificates issued by WoSign and StartCom. The details are on the blog post that was mentioned in Comment #3, and  Issue 685826  tracks the removal for Chrome 57.
Thank you, thank solves the riddle. Though a more detailed error page would save me a lot of troubles..

Sign in to add a comment