| commit | 5f2e5f3b50c1695c55691b492fcca1bb58b42487 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Thu Feb 02 02:30:49 2023 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Thu Feb 02 02:30:49 2023 +0000 |
| tree | b58635ffb70fc166f5b6989189c0317e4800e522 | |
| parent | 4b4aa50875c0b96f84536775b9b47963a392fe85 [diff] | |
| parent | d33b2d96b93e24a7ebefac0f3a176a142590bf2f [diff] |
Snap for 9552483 from d33b2d96b93e24a7ebefac0f3a176a142590bf2f to udc-release Change-Id: I40b46c99824ff65a043646bdb575bcd2c6765df0
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.51 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.