tls: Securely clear memory from private key material #460
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
sreimers
reviewed
Jul 27, 2022
Lastique
force-pushed
the
feature/secure_clear_memory
branch
2 times, most recently
from
63bbb54 to
bd2e82d
Compare
sreimers
reviewed
Jul 27, 2022
sreimers
reviewed
Jul 27, 2022
The function can be used to securely clear a block of memory without compiler optimizing away this call.
This ensures that sensitive data is not left on the stack.
Lastique
force-pushed
the
feature/secure_clear_memory
branch
from
bd2e82d to
9d370c4
Compare
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.
This ensures that sensitive data is not left on the stack.