Add security warning to TrustStrategy implementations documentation #490
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.
Tries to improve the documentation of
TrustAllStrategy
andTrustSelfSignedStrategy
by mentioning their security implications and suggesting more secure alternatives.For
TrustSelfSignedStrategy
it also documents what exactly the strategy does. Otherwise without looking at the implementation details users might erroneously think it is always necessary to useTrustSelfSignedStrategy
when using self-signed certificates (even if they are also in the truststore), which is not the case.Any feedback is appreciated!