feat(dgw): new TlsVerifyStrict option #1415
Merged
Conversation
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
thenextman
approved these changes
Jul 9, 2025
This adds a `TlsVerifyStrict` option for controlling the new stricter verifications on TLS certificates. When enabled (`true`), the client performs additional checks on the server certificate, including: - Ensuring the presence of the **Subject Alternative Name (SAN)** extension. - Verifying that the **Extended Key Usage (EKU)** extension includes `serverAuth`. Certificates that do not meet these requirements are increasingly rejected by modern clients (e.g., Chrome, macOS). Therefore, we strongly recommend using certificates that comply with these standards. Issue: DGW-293
393bf4d to
511d5d5
Compare
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.
This adds a
TlsVerifyStrictoption for controlling the new stricter verifications on TLS certificates.When enabled (
true), the client performs additional checks on the server certificate, including:serverAuth.Certificates that do not meet these requirements are increasingly rejected by modern clients (e.g., Chrome, macOS). Therefore, we strongly recommend using certificates that comply with these standards.
The default configuration for fresh installs will include the
TlsVerifyStrictkey set totrue.Issue: DGW-293