-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove basicConstraints extension from certificate #2330
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2330 +/- ##
=======================================
Coverage 93.95% 93.95%
=======================================
Files 34 34
Lines 1291 1291
Branches 368 368
=======================================
Hits 1213 1213
Misses 77 77
Partials 1 1
Continue to review full report at Codecov.
|
I am afraid it is can break https in other browsers, we should test this on chrome/firefox/safari, anyway thanks for PR |
@akx thanks for PR, i will look on this in near future and do more tests 👍 |
@evilebottnawi do you know the reason? I have only Mac... |
@hiroppy can you try to remove |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be honestly i afraid removing basicConstraints
because it can break certificates for old browsers
I think it might be better to change the targeted branch from master to next. |
@hiroppy right now https is broken for chrome on linux, it should be not next, it is bug and we need fix it |
This fixes TLS on Chromium Linux (see webpack#2313) Based on webpack#2313 (comment)
I'm not sure this change's inpact. Anyway someone can check this change on Windows? |
@hiroppy i think we should open issue in chrome bug tracker, because some options works on macos chrome but doesn't on linux chrome and versa vice, for me it is very strange behavior and we need more information from developers why it is happens |
This fixes TLS on Chromium Linux (see #2313).
Based on #2313 (comment) – thanks to @gigafied for the fix!
fixes #2313
For Bugs and Features; did you add new tests?
No tests – I did give it a spin on Linux Chromium (via Docker and Xquartz, which is why it's shown with macOS window decoration here). As discussed in #2313, we now only get ERR_CERT_AUTHORITY_INVALID, which is skippable.
Motivation / Use-Case
Restores TLS functionality on Linux Chromium.
Breaking Changes
This should not break anything, though I don't have macOS Catalina (see #2274) to test with.