| commit | a02a486f40d84c5140cca14531359119a667c823 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Wed Sep 11 23:31:13 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Wed Sep 11 23:31:13 2024 +0000 |
| tree | 985323d8131747fd1e7578983d2f204e00b81e74 | |
| parent | 657af774feb6405c8684c7c0451064a90d602b75 [diff] | |
| parent | 8eb9e0bb187139194e4366e25f1644a3d170930f [diff] |
Snap for 12355814 from 8eb9e0bb187139194e4366e25f1644a3d170930f to build-tools-release Change-Id: If5f57aeb43c666d47a97efef3473306a0fc984f2
Securely zero memory (a.k.a. zeroize) while avoiding compiler optimizations.
This crate implements a portable approach to securely zeroing memory using techniques which guarantee they won't be “optimized away” by the compiler.
The Zeroize trait is the crate's primary API.
Zeroing memory securely is hard - compilers optimize for performance, and in doing so they love to “optimize away” unnecessary zeroing calls. There are many documented “tricks” to attempt to avoid these optimizations and ensure that a zeroing routine is performed reliably.
This crate isn‘t about tricks: it uses core::ptr::write_volatile and core::sync::atomic memory fences to provide easy-to-use, portable zeroing behavior which works on all of Rust’s core number types and slices thereof, implemented in pure Rust with no usage of FFI or assembly.
#![no_std] i.e. embedded-friendly!Rust 1.56 or newer.
In the future, we reserve the right to change MSRV (i.e. MSRV is out-of-scope for this crate's SemVer guarantees), however when we do it will be accompanied by a minor version bump.
Licensed under either of:
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.