wolfssl: avoid taking cached x509 store ref if sslctx already using it #14442
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.
When using x509 store from cache we first call
wolfSSL_X509_STORE_up_ref
followed bywolfSSL_CTX_set_cert_store
here, however wolfSSL_CTX_set_cert_store will be a noop if we're trying to set a store which the sslctx is already using causing us to leak ref -> leak memory.