SSL certificate validation vulnerability fix #13
+221
−3
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
4 participants
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.
Description
This PR addresses a critical security vulnerability in SSL certificate validation by implementing proper certificate chain verification. The fix replaces an insecure "trust-all" TrustManager with a secure implementation that maintains full certificate validation while adding time leeway for certificate expiration.
Fix was done by:
This fix was originally done in the repo provided below but not applied here.
References
Related fix commit .