Potential fix for code scanning alert no. 8: Disabled TLS certificate check #1
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.
Potential fix for https://github.com/AKA-NETWORK/cli/security/code-scanning/8
To fix the issue, the
InsecureSkipVerify: truesetting should be removed, and proper certificate validation should be implemented. If the application requires custom handling of certificates (e.g., due to CDN-related issues), a trusted certificate authority (CA) or a custom certificate pool should be configured using theRootCAsfield intls.Config. This ensures that the application validates certificates securely while accommodating specific requirements.The changes will involve:
InsecureSkipVerify: true.x509.NewCertPool()and loading trusted certificates.TLSClientConfigto use the custom certificate pool.Suggested fixes powered by Copilot Autofix. Review carefully before merging.