Code reviews of the constant_time

These reviews are from cargo-vet. To add your review, set up cargo-vet and submit your URL to its registry.

0.3.0 — diff review from 0.2.6 only (current) safe-to-deploy

From zcash/rust-ecosystem copy of zcash/zcash. By str4d.

Replaces some unsafe code by bumping MSRV to 1.66 (to access core::hint::black_box).

0.3.0 (current) unknown

From kornelski/crev-proofs copy of git.savannah.gnu.org.

Packaged for Guix (crates-io)

The current version of constant_time_eq is 0.3.0.

0.2.4 (older version) safe-to-deploy

From bytecodealliance/wasmtime. By Nick Fitzgerald.

A few tiny blocks of unsafe but each of them is very obviously correct.

cargo-vet does not verify reviewers' identity. You have to fully trust the source the audits are from.

safe-to-deploy (implies safe-to-run)

This crate will not introduce a serious security vulnerability to production software exposed to untrusted input. More…

safe-to-run

Implied by other criteria

This crate can be compiled, run, and tested on a local workstation or in controlled automation without surprising consequences. More…

crypto-reviewed

The cryptographic code in this crate has been reviewed for correctness by a member of a designated set of cryptography experts within the project.

unknown

May have been packaged automatically without a review

These reviews are from Crev, a distributed system for code reviews. To add your review, set up cargo-crev.

The current version of constant_time_eq is 0.3.0.

0.1.5 (older version) Rating: Strong Positive Thoroughness: Medium Understanding: High

by Minoru on 2020-05-13

I compared this to crypto/memneq.c from Linux 5.7-rc5; the algorithm is indeed the same, and I understand how it works. There are comments for all the unobvious bits, too. I am not formally trained in cryptography, but I posses basic knowledge and I believe this code to be secure for any application.

0.1.4 (older version) Rating: Positive Thoroughness: Medium Understanding: Medium

by git.sr.ht/~icefox on 2019-09-19

Tiny, safe, well-documented.

0.1.3 (older version) Rating: Positive Thoroughness: Medium Understanding: High

Approved without comment by dpc on 2019-01-27

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 constant_time_eq. Alternatively, you can download the tarball of constant_time_eq v0.3.0 or view the source online.