New issue
Advanced search Search tips

Issue 705906 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 308330
Owner: ----
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Self signed certificate for localhost gives NET::ERR_CERT_COMMON_NAME_INVALID

Reported by speak.to...@gmail.com, Mar 28 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Create a self-signed certificate with the common name "localhost"
2. Setup a web server with the certificate
3. Visit "https://localhost"

What is the expected behavior?
Chrome should display the content at "https://localhost"

What went wrong?
Chrome displays the "Your connection is not private" screen with the error code NET::ERR_CERT_COMMON_NAME_INVALID

Vis contradictory error description in screenshot: "This server could not prove that it is localhost; its security certificate is from localhost."

Did this work before? Yes 56.0.2924.87

Chrome version: 59.0.3053.3   Channel: canary
OS Version: OS X 10.11.5
Flash Version: 25.0.0.143

Server in question is NGINX:

:~$ nginx -V
nginx version: nginx/1.10.1
built by clang 7.3.0 (clang-703.0.31)
built with OpenSSL 1.0.2h  3 May 2016 (running with OpenSSL 1.0.2j  26 Sep 2016)
TLS SNI support enabled
 
Screen Shot 2017-03-28 at 10.19.37.png
129 KB View Download
Components: Internals>Network>Certificate
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
Mergedinto: 308330
Status: Duplicate (was: Unconfirmed)
Chrome 58 deprecates the use of the SubjectCN field in Self-signed certificates; the certificate hostname must appear in the SubjectAltNames instead.

https://textslashplain.com/2017/03/10/chrome-deprecates-subject-cn-matching/

The bug on the error message is  Issue 703614 

Sign in to add a comment