Use certificate with proper subjectAltName (Chrome 58 compatibility)#137
Open
padde wants to merge 1 commit intodefunkt:masterfrom
Open
Use certificate with proper subjectAltName (Chrome 58 compatibility)#137padde wants to merge 1 commit intodefunkt:masterfrom
padde wants to merge 1 commit intodefunkt:masterfrom
Conversation
|
This still works for me with chrome 71 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem description
Dotjs stopped working with Chrome 58. Chrome will no longer accept a certificate without
subjectAltNameand will display this error instead:For the announcement, see https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/IGT2fLJrAeo/csf_1Rh1AwAJ
How the valid self-signed certificate was generated
For future reference, the openssl command used to generate the certificate was based on this StackOverflow post: