Test zeroization when going out of scope #1310
Closed
Conversation
This file contains hidden or 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
|
A test like this would make more sense in |
Comment on lines
+395
to
+397
| let bytes: &[u8] = core::slice::from_raw_parts(ptr as *const u8, size_of::<u128>()); | ||
| assert!( | ||
| bytes.iter().all(|&b| b == 0), |
There was a problem hiding this comment.
This is UB since you're making a Rust reference that's UAF.
You could avoid UB by performing only raw pointer operations, i.e. computing new pointers and dereferencing them, which would be fairly trivial to do here.
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.
Test that zeroization actually occurs when a
SecretBoxgoes out of scope.Uses
unsafecode, likely relies on UB and adds a custom allocator, hence the draft: is something like this acceptable?