New issue
Advanced search Search tips

Issue 700415 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 700595
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

SSL certificate case sensitivity

Project Member Reported by wfh@chromium.org, Mar 10 2017

Issue description

A report from reddit:

https://pay.reddit.com/r/chrome/comments/5ylr3s/chrome_dev_58030296_takes_ssl_certificates_common/

"
I am using HTTPS on my home network. I tried to connect to the website from my laptop, but Chrome kept saying ERR_CERT_COMMON_NAME_INVALID. I checked the certificate, and the certificate itself was all right. The only thing I suspect is that the name is starting with a capital letter like "Doge". So, when I tried to access the page by an address "https://doge/such.page", I think Chrome treated "doge" != "Doge" and thus, a wrong certificate.

I do not think domain names are case-sensitive. So, if this is the case, I think it is a bug.

I do not know why the dev version of Chrome had been installed on my laptop in the first place. Probably, it was a mistake. I uninstalled it and installed the stable version, and the problem is gone.
"
 
Components: -Internals>Network>SSL Internals>Network>Certificate
Guessing this is the common name deprecation.
Status: WontFix (was: Untriaged)
It's not case sensitive, it appears the reporter was just assuming it is, based on the description.

This is https://www.chromestatus.com/features/4981025180483584 , for which the Enterprise Policy "EnableCommonNameFallbackForLocalAnchors" exists for internal purposes.

Beyond that, Chrome should not be matching against common names anymore, because they are ambiguous as to whether they contain a domain and are exempt from more stringent security checks.

Comment 3 by eroman@chromium.org, Mar 11 2017

Mergedinto: 700595
Status: Duplicate (was: WontFix)

Sign in to add a comment