0.4.0 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
This review is from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
The current version of Fleetspeak is 0.4.2.
0.4.0 (older version)
From google/supply-chain copy of google/rust-crate-audits. By Manish Goregaokar.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
Mild unsoundness or suboptimal soundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-3
Extreme unsoundness.
Full description of the audit criteria can be found at https://github.com/google/rust-crate-audits/blob/main/auditing_standards.md#ub-risk-4
Inspection reveals that the crate in question does not attempt to implement any cryptographic algorithms on its own.
Note that certification of this does not require an expert on all forms of cryptography: it's expected for crates we import to be "good enough" citizens, so they'll at least be forthcoming if they try to implement something cryptographic. When in doubt, please ask an expert.
All crypto algorithms in this crate have been reviewed by a relevant expert.
Note: If a crate does not implement crypto, use does-not-implement-crypto
,
which implies crypto-safe
, but does not require expert review in order to
audit for.
Crates in the crates.io registry are tarball snapshots uploaded by crates' publishers. The registry is not using crates' git repositories. There is absolutely no guarantee that the repository URL declared by the crate belongs to the crate, or that the code in the repository is the code inside the published tarball.
To review the actual code of the crate, it's best to use cargo crev open fleetspeak
. Alternatively, you can download the tarball of fleetspeak v0.4.2 or view the source online.
Reviewed in CL 551181045 Opens files from file descriptors obtained from potentially untrusted sources. This may be okay depending on your use case, and is a common pattern for IPC, but should be included in your project with care since opening the wrong mmaped fd may cause UB.