0.5.7 — diff review from 0.5.5 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Kershaw.
These reviews are from cargo-vet. To add your review, set up cargo-vet
and submit your URL to its registry.
The current version of Socket2 is 0.5.9.
0.5.7 — diff review from 0.5.5 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Kershaw.
0.5.7 — diff review from 0.5.6 only (older version)
From zcash/rust-ecosystem copy of zcash/librustzcash. By Daira-Emma Hopwood.
0.5.7 (older version)
From kornelski/crev-proofs copy of salsa.debian.org.
Only in debcargo (unstable). Changelog:
0.5.6 — diff review from 0.5.5 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. Audited without comment by Daira-Emma Hopwood.
0.5.5 — diff review from 0.4.4 only (older version)
From google/supply-chain copy of fuchsia. By David Koloski.
Reviewed at https://fxrev.dev/946307
0.5.5 — diff review from 0.5.4 only (older version)
From zcash/rust-ecosystem copy of zcash/zcash. By Jack Grigg.
Adds support for Sony Vita targets. New unsafe
blocks are for Vita-specific
libc
calls to getsockopt
and setsockopt
for non-blocking behaviour.
0.5.5 (older version)
From kornelski/crev-proofs copy of git.savannah.gnu.org.
Packaged for Guix (crates-io)
0.4.9 (older version)
From google/supply-chain copy of chromium. Audited without comment by Vovo Yang.
0.4.9 — diff review from 0.4.7 only (older version)
From bytecodealliance/wasmtime. By Alex Crichton.
Minor OS compat updates but otherwise nothing major here.
0.4.7 — diff review from 0.4.4 only (older version)
From mozilla/supply-chain copy of hg. Audited without comment by Mike Hommey.
cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.
This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…
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.
This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…
Negligible unsoundness or average 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-2
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
May have been packaged automatically without a review
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 socket2
. Alternatively, you can download the tarball of socket2 v0.5.9 or view the source online.
The new uses of unsafe to access getsockopt/setsockopt look reasonable.