New issue
Advanced search Search tips

Issue 713199 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 308330
Owner: ----
Closed: Apr 2017
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Security



Sign in to add a comment

localhost https problemn with a CN=127.0.0.1

Reported by david.ra...@gmail.com, Apr 19 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.68 Safari/537.36

Steps to reproduce the problem:
1. local serveur with a certificat CN=127.0.0.1 without SAN
2. https://127.0.0.1/(fonction)
3. Chrome 58 refuse the certificat, chrome 57 don't

What is the expected behavior?
Chrome must accept this certificat.
If you replace "CN=127.0.0.1" with "CN=localhost" it works but why ?

What went wrong?
https://127.0.0.1/(fonction) + CN= 127.0.0.1 => KO
https://127.0.0.1/(fonction) + CN= localhost => OK (?)
https://localhost/(fonction) + CN= 127.0.0.1 => KO
https://localhost/(fonction) + CN= localhost => KO

Did this work before? Yes 57

Chrome version: 58.0.3029.68  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 

Comment 1 by mea...@chromium.org, Apr 19 2017

Labels: -Restrict-View-SecurityTeam allpublic
Mergedinto: 308330
Status: Duplicate (was: Unconfirmed)
Support for common name matching has been removed in M58. Please see  bug 308330 .

Sign in to add a comment