cavp
| Crates.io | cavp |
| lib.rs | cavp |
| version | |
| source | src |
| created_at | 2024-07-22 13:38:01.098029+00 |
| updated_at | 2025-02-24 07:14:52.245438+00 |
| description | Libcrux helper to read NIST CAVP test vectors. |
| homepage | https://github.com/cryspen/libcrux |
| repository | https://github.com/cryspen/libcrux |
| max_upload_size | |
| id | 1311108 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Crates (github:cryspen:crates)
documentation
README
libcrux - the formally verified crypto library
libcrux is a formally verified cryptographic library in Rust.
Minimum Supported Rust Version (MSRV)
The default feature set has a MSRV of 1.78.0. no_std environments
are supported starting from Rust version 1.81.0.
Randomness
libcrux provides a DRBG implementation that can be used standalone (drbg::Drbg)
or through the Rng traits.
no_std support
libcrux and the individual primitive crates it depends on support
no_std environments given a global allocator for the target
platform.
Verification status
As a quick indicator of overall verification status, subcrates in this workspace include the following badges:
to indicate that most (or all) of the code that
is contained in default features of that crate is not (yet)
verified.to indicate that algorithms in a crate have been verified and extracted to Rust as part of the HACL project. Top-level APIs in these crates accessing the code from HACL may not be verified.
to indicate that most (or all) of the code that is
contained in the default feature set is verified.
In every case, please refer to the more detailed notes on verification in each sub-crate to learn more about what has (or has not) been verified in the particular case.