This repository was archived by the owner on Aug 4, 2025. It is now read-only.
core: fix the ssl verification issue #171
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
Signed-off-by: Le Yao <[email protected]>
|
@dongx1x Hi, will this change broke the logic or cause some new issues? |
We need to validate this change, it should work for the normal https server, and maybe a certificate should be provided for the self-signed https server. |
|
@Hulongyin Can you help test with the changes to verify if it works or not? |
Sure, I will verify it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It is used to fix the SSL verification which should be the default
Turevalue during scan.