Sergey "Shnatsel" Davidoff
Sergey "Shnatsel" Davidoff
Another lint requested: https://github.com/rust-lang/rust-clippy/issues/4862
https://github.com/rust-lang/rust-clippy/issues/4891
https://github.com/rust-lang/rust-clippy/issues/4896
Discover what reviewers are even available is definitely needed, but I feel this is more of a work item for cargo-crev itself than for safety-dance. Please open an issue at...
Hot take: just put your crev IDs here. This will provide the discoverability if anyone is actively looking, and will not look _too_ much like an endorsement.
I have a proof of concept implementation that embeds `Cargo.lock` into compiled binaries with non-perfect but reasonable ergonomics, and a tool to recover that info afterwards. This can be used...
I have published a proof of concept implementation: https://github.com/Shnatsel/rust-audit Discussion: https://www.reddit.com/r/rust/comments/awlqfi/
RFC for Cargo is open: https://github.com/rust-lang/rfcs/pull/2801 It got a lot of constructive feedback, we need to incorporate it and submit it for another round.
Implementation as a Cargo subcommand: https://github.com/rust-secure-code/cargo-auditable
If initialization is done only once it comes without any overhead because the allocator can request already-zeroed memory from the OS. It's the subsequent initializations that require `memset()`.