Use default TLS validation for sync downloads#101
Open
mobasi-team wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
--syncdownload path.HttpClientuse the platform's default TLS certificate validation when downloading the GitHub map archive.Rationale
--syncdownloads the SQLECmd map archive from GitHub and installs updated maps into the localMapsdirectory. The previous custom validation callback accepted all server certificates, bypassing normal hostname and certificate-chain validation.Using the default
HttpClientbehavior preserves the existing sync flow while allowing invalid TLS certificates to be rejected.