Fix double free vulnerability #10
Open
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.
Your current ~Cipher will run a delete operation on a stack string or your constant, shared, example key which results in undefined behavior (perhaps this is the cause of) #9
I've moved the private key to a standard char array that will be allocated on the stack (if Cipher is created without "new" obviously, else it will be in the heap but in the same memory region) which doesn't need a destructor. I've also removed the DEBUG constant as the user should enable it manually outside the library so that using it in the ide will be easier and moved your shared key to a macro for simplicity.