WIP: Use proper ref count handling when adding to x509 store #8233
Conversation
This file contains 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
SparkiDev
reviewed
Nov 27, 2024
| result = WOLFSSL_SUCCESS; | ||
| } | ||
| else { | ||
| result = WOLFSSL_FATAL_ERROR; |
There was a problem hiding this comment.
Should we be freeing x509 on failure to push?
There was a problem hiding this comment.
Possibly, there are still additional issues with the implementation in this PR the automated tests exposed. I am currently working on resolving these new memory leaks.
ColtonWilley
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Use proper ref count handling when adding to x509 store
Fixes github issue #8222