fix feat TrustManager
that accepts all certificates
#4295
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.
java/kubernetes/src/main/java/io/kubernetes/client/openapi/ApiClient.java
Lines 1499 to 1520 in c14bb93
To address this vulnerability, we must remove the custom
TrustManager
andHostnameVerifier
that accept all certificates.KeyStore
, as demonstrated in the good example in the background.TrustManager
should be initialized via aTrustManagerFactory
with aKeyStore
containing only the explicitly trusted certificates.applySslSettings()
method:TrustManager
andHostnameVerifier
.verifyingSsl
isfalse
, throw an exception or require the user to provide a trusted CA cert, as in theelse
branch. This eliminates the insecure option entirely.References
Security with HTTPS and SSL