saymrwulf/curve25519-dalek-source
1
0
Fork 0
mirror of https://github.com/saymrwulf/curve25519-dalek-source.git synced 2026-09-04 20:24:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
curve25519-dalek-source/curve25519-dalek/Cargo.toml

92 lines
2.9 KiB
TOML
Raw Normal View History

Initial commit.
2016-12-08 05:12:00 +00:00
[package]
name = "curve25519-dalek"
Bump version to 2.1.0
2020-05-29 19:39:39 +00:00
# Before incrementing:
# - update CHANGELOG
# - update README if required by semver
curve,ed,x: Bump prerelease version to fix build (#863)
2026-01-03 15:52:34 +00:00
version = "5.0.0-pre.4"
Bump edition to 2024 and crate versions to prereleases (#775) This represents the first breaking change in a new release series, bumping all crates to the 2024 edition of Rust. As such, the version numbers of all crates have been incremented to represent a new prerelease series: - `curve25519-dalek`: v5.0.0-pre - `ed25519-dalek`: v3.0.0-pre - `x25519-dalek`: v3.0.0-pre Note that this commit isn't intended to cut associated crate releases of these on crates.io, but is merely bumping the version numbers to denote there are pending breaking changes. This commit also includes rustfmt changes which were made as part of the 2024 edition. Also includes clippy fixes.
2025-07-07 15:52:25 +00:00
edition = "2024"
rust-version = "1.85.0"
Cut pre.0 prereleases (#784)
2025-07-09 17:04:17 +00:00
authors = [
"Isis Lovecruft <isis@patternsinthevoid.net>",
"Henry de Valence <hdevalence@hdevalence.ca>",
]
Initial commit.
2016-12-08 05:12:00 +00:00
readme = "README.md"
Fix licence
2017-08-01 02:05:31 +00:00
license = "BSD-3-Clause"
curve: update `repository` in Cargo.toml (#575) Point to the subdirectory which contains the crate
2023-09-06 04:08:06 +00:00
repository = "https://github.com/dalek-cryptography/curve25519-dalek/tree/main/curve25519-dalek"
Minor documentation fixes (#444) * Docs unlink from dalek.rs * Link katex assets to jsdelivr Co-authored-by: Michael Rosenberg <michael@mrosenberg.pub>
2022-12-07 10:36:07 +00:00
homepage = "https://github.com/dalek-cryptography/curve25519-dalek"
Initial commit.
2016-12-08 05:12:00 +00:00
documentation = "https://docs.rs/curve25519-dalek"
Add "cryptography" and "no-std" categories
2017-02-14 16:34:24 +00:00
categories = ["cryptography", "no-std"]
Bump version to 1.2.2
2019-07-31 22:22:31 +00:00
keywords = ["cryptography", "crypto", "ristretto", "curve25519", "ristretto255"]
Remove -pre.0; reword CHANGELOG entries.
2019-02-15 18:11:18 +00:00
description = "A pure-Rust implementation of group operations on ristretto255 and Curve25519"
Cut pre.0 prereleases (#784)
2025-07-09 17:04:17 +00:00
exclude = ["**/.gitignore", ".gitignore"]
Initial commit.
2016-12-08 05:12:00 +00:00
I think this will add KaTeX into docs.rs ???
2017-11-15 18:09:52 +00:00
[package.metadata.docs.rs]
Fixed docsrs flags in Cargo.toml
2022-12-13 13:48:03 +00:00
rustdoc-args = [
Cut pre.0 prereleases (#784)
2025-07-09 17:04:17 +00:00
"--html-in-header",
"docs/assets/rustdoc-include-katex-header.html",
"--cfg",
"docsrs",
]
Fix docs build and prep prerelease (#855) * Fix failing docs build * Remove hiding of docsrs cfg gate in crates where it doesn't appear * Add docsrs build regression check to CI
2025-12-04 23:06:40 +00:00
all-features = true
I think this will add KaTeX into docs.rs ???
2017-11-15 18:09:52 +00:00
Consolidate Cargo.toml and document the weird build hack
2018-01-27 00:29:23 +00:00
[dev-dependencies]
Bump `rand_core` from v0.9 to v0.10.0-rc-2 (#842) Prior to a final stable release of the @RustCrypto dependencies used by the dalek crates, we are going to target `rand_core` v0.10. This updates the `rand` and `rand_core` dependencies as well as the aforementioned @RustCrypto dependencies to be compatible with `rand_core` v0.10, which incurred a few API changes: - `rand_core` no longer includes `OsRng`, so this replaces the `os_rng` features with `getrandom` features (same thing we did for @RustCrypto) which uses the `getrandom` crate directly - For `dev-dependencies` it just migrates straight to `rand`, replacing `rand_chacha` with the `chacha` feature of `rand` (which pulls in `chacha20`), and sourcing `OsRng` from `rand`, its new home (for now) This PR also switches to using the `rustcrypto-ff`/`rustcrypto-group` crates (hopefully temporary) which are forks of `ff` and `group` which have crate releases that have been updated to use `rand_core` v0.10.0 prereleases.
2025-11-22 17:37:51 +00:00
sha2 = { version = "0.11.0-rc.3", default-features = false }
Add Serde support for compressed points; use bincode for tests.
2018-09-26 22:28:47 +00:00
bincode = "1"
curve,ed: chore: update dev deps (#569)
2023-08-28 13:46:38 +00:00
criterion = { version = "0.5", features = ["html_reports"] }
Implements an Elligator2 map for Curve25519 This implementation: - is agnostic on the hash used to pick a field element, even though SHA512 is commonly used, - follows https://tools.ietf.org/id/draft-irtf-cfrg-hash-to-curve-10.html closely - tests the outputs of the function using libsignal's implementation.
2020-10-21 15:02:06 +00:00
hex = "0.4.2"
Scalar::div_by_2 (#805) * [WIP] Scalar::div_by_2 * debug_assert that carry is 0 * revise tests * Test multiply by half scalar, double and compress (#804) * Test `div_by_2` with `proptest` (#806) --------- Co-authored-by: daxpedda <daxpedda@gmail.com>
2025-08-22 18:45:51 +00:00
proptest = "1"
chore(deps): bump `rand_core` to `0.10.0-rc-5` (#870)
2026-01-21 19:52:56 +00:00
rand = "0.10.0-rc.7"
Use `criterion.rs` instead of libtest for benchmarks. Since Criterion can only benchmark public API, these changes just drop all internal benchmarks (e.g., benchmarks for field operations). But those are usually microbenchmarks whose meaning is kind of questionable anyways, so I don't think this is a big loss. The `bench` feature disappears, since Criterion works on stable Rust.
2018-03-26 00:10:30 +00:00
Fixes curve25519_dalek_bits defaults for cross and wasm (#465) build.rs was using cfg(target) but it has to evaluate this from env TARGET as build.rs cfg(target) in build context is the builder host and not the target. This change fixes curve25519_dalek_bits lottery to determine the correct automatic curve25119_dalek_bits with the help of platforms crate. As discussed in #456 this also prepares for well known defaults for wasm and arm serial backend via cfg(curve25519_dalek_bits = "64") If the wasm32 or armv7 are going to be u64 serial by default these will be followed up on later.
2022-12-10 02:09:24 +00:00
[build-dependencies]
Support SIMD on Rust stable (#520) * Remove dependency on `packed_simd` * Support SIMD on stable Rust * Move `packed_simd.rs` to `vector` module * Add comment header to `packed_simd.rs` * Initialize SIMD registers using intrinsics instead of `transmute` * Use a splat inside of `unpack_pair` * Update README: the AVX2 backend now works on stable Rust * Add a CI job to also build the AVX2 SIMD backend on Rust stable * Added SIMD MSRV test
2023-03-30 06:16:18 +00:00
rustc_version = "0.4.0"
Fixes curve25519_dalek_bits defaults for cross and wasm (#465) build.rs was using cfg(target) but it has to evaluate this from env TARGET as build.rs cfg(target) in build context is the builder host and not the target. This change fixes curve25519_dalek_bits lottery to determine the correct automatic curve25119_dalek_bits with the help of platforms crate. As discussed in #456 this also prepares for well known defaults for wasm and arm serial backend via cfg(curve25519_dalek_bits = "64") If the wasm32 or armv7 are going to be u64 serial by default these will be followed up on later.
2022-12-10 02:09:24 +00:00
Use `criterion.rs` instead of libtest for benchmarks. Since Criterion can only benchmark public API, these changes just drop all internal benchmarks (e.g., benchmarks for field operations). But those are usually microbenchmarks whose meaning is kind of questionable anyways, so I don't think this is a big loss. The `bench` feature disappears, since Criterion works on stable Rust.
2018-03-26 00:10:30 +00:00
[[bench]]
name = "dalek_benchmarks"
harness = false
Feature-gated more precomputed tables (#500) Feature-gates `AFFINE_ODD_MULTIPLES_OF_BASEPOINT` Feature-gated tables out of vector vartime aA + bB procedure
2023-01-20 17:55:32 +00:00
required-features = ["alloc", "rand_core"]
first avx2 code
2017-10-23 21:03:23 +00:00
Consolidate Cargo.toml and document the weird build hack
2018-01-27 00:29:23 +00:00
[dependencies]
Implement simplified backend selection (#428) As proposed in #414, this commit changes the backend selection approach, introspecting `target_pointer_width` to select `u32_backend` vs `u64_backend` (or `fiat_u32_backend`/`fiat_u64_backend` if the `fiat_backend` feature is enabled). This helps eliminate the use of non-additive features, and also the rather confusing errors that happen if multiple backends are selected (i.e. thousands of lines of rustc errors). The selection logic checks if `target_pointer_width = "64"` and uses the 64-bit backend, or falls back to the 32-bit backend otherwise. This means the crate will always have a valid backend regardless of the pointer width, although there may be odd edge cases for exotic platforms which would optimally use the 64-bit backend but have a non-"64" target pointer width for whatever reason. We can handle those cases as they come up.
2022-11-13 17:17:42 +00:00
cfg-if = "1"
Bump `rand_core` from v0.9 to v0.10.0-rc-2 (#842) Prior to a final stable release of the @RustCrypto dependencies used by the dalek crates, we are going to target `rand_core` v0.10. This updates the `rand` and `rand_core` dependencies as well as the aforementioned @RustCrypto dependencies to be compatible with `rand_core` v0.10, which incurred a few API changes: - `rand_core` no longer includes `OsRng`, so this replaces the `os_rng` features with `getrandom` features (same thing we did for @RustCrypto) which uses the `getrandom` crate directly - For `dev-dependencies` it just migrates straight to `rand`, replacing `rand_chacha` with the `chacha` feature of `rand` (which pulls in `chacha20`), and sourcing `OsRng` from `rand`, its new home (for now) This PR also switches to using the `rustcrypto-ff`/`rustcrypto-group` crates (hopefully temporary) which are forks of `ff` and `group` which have crate releases that have been updated to use `rand_core` v0.10.0 prereleases.
2025-11-22 17:37:51 +00:00
ff = { version = "=0.14.0-pre.0", package = "rustcrypto-ff", default-features = false, optional = true }
group = { version = "=0.14.0-pre.0", package = "rustcrypto-group", default-features = false, optional = true }
chore(deps): bump `rand_core` to `0.10.0-rc-5` (#870)
2026-01-21 19:52:56 +00:00
rand_core = { version = "0.10.0-rc-5", default-features = false, optional = true }
Bump `rand_core` from v0.9 to v0.10.0-rc-2 (#842) Prior to a final stable release of the @RustCrypto dependencies used by the dalek crates, we are going to target `rand_core` v0.10. This updates the `rand` and `rand_core` dependencies as well as the aforementioned @RustCrypto dependencies to be compatible with `rand_core` v0.10, which incurred a few API changes: - `rand_core` no longer includes `OsRng`, so this replaces the `os_rng` features with `getrandom` features (same thing we did for @RustCrypto) which uses the `getrandom` crate directly - For `dev-dependencies` it just migrates straight to `rand`, replacing `rand_chacha` with the `chacha` feature of `rand` (which pulls in `chacha20`), and sourcing `OsRng` from `rand`, its new home (for now) This PR also switches to using the `rustcrypto-ff`/`rustcrypto-group` crates (hopefully temporary) which are forks of `ff` and `group` which have crate releases that have been updated to use `rand_core` v0.10.0 prereleases.
2025-11-22 17:37:51 +00:00
digest = { version = "0.11.0-rc.4", default-features = false, optional = true, features = [
Cut pre.0 prereleases (#784)
2025-07-09 17:04:17 +00:00
"block-api",
] }
subtle = { version = "2.6.0", default-features = false, features = [
"const-generics",
] }
serde = { version = "1.0", default-features = false, optional = true, features = [
"derive",
] }
Make `zeroize` an optional dependency (#481) * Make `zeroize` an optional dependency The `zeroize` crate provides a defense against memory read oracles which typically arise from memory unsafety. Pure Rust programs may not benefit from `zeroize`, and in certain cases the unsafe code used by `zeroize` may be more concerning. This commit makes `zeroize` into an optional feature so users may elect to disable it if they so desire. * Added zeroize feature flag to README Co-authored-by: Michael Rosenberg <michael@mrosenberg.pub>
2022-12-26 21:19:55 +00:00
zeroize = { version = "1", default-features = false, optional = true }
Runtime backend autodetection
2023-04-11 11:13:18 +00:00
[target.'cfg(target_arch = "x86_64")'.dependencies]
chore(deps): bump `cpufeatures` from `0.2.12` to `0.2.17` (#750) This fixes warnings like: ``` warning: unexpected `cfg` condition value: `` --> curve25519-dalek/src/backend/mod.rs:58:9 | 58 | cpufeatures::new!(cpuid_avx512, "avx512ifma", "avx512vl"); | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ```
2025-05-08 20:06:28 +00:00
cpufeatures = "0.2.17"
Use `--cfg curve25519_dalek_backend` to select backend (#455) Crate features are intended to be additive, whereas only 1-of-N possible backends can be selected. Features can also be activated by transitive dependencies, which leads to a problem of different dependences selecting conflicting backends. Using `--cfg` instead moves all backend selection control to the toplevel executable. This commit switches to the following RUSTFLAGS to enable backends: - `--cfg curve25519_dalek_backend="fiat"`: uses `fiat-crypto` - `--cfg curve25519_dalek_backend="simd"`: uses nightly-only SIMD
2022-12-09 08:42:52 +00:00
[target.'cfg(curve25519_dalek_backend = "fiat")'.dependencies]
curve: Hash to curve and field as defined in the standard (#377) * Implementation of `hash_to_field` as defined in the standard * Implementation of `hash_to_curve` as defined in the standard, by changing the mechanism over which we chose the sign. * For the point above, had to change the `elligator_encode` to return whether `eps` is a square or not (required for `hash_to_curve`). * Included test vectors of the draft. * Included `FieldElement::from_bytes_wide(bytes: &u8; 64])` to reduce integers encoded in 64 bytes.
2025-07-05 20:01:26 +00:00
fiat-crypto = { version = "0.3.0", default-features = false }
Use `--cfg curve25519_dalek_backend` to select backend (#455) Crate features are intended to be additive, whereas only 1-of-N possible backends can be selected. Features can also be activated by transitive dependencies, which leads to a problem of different dependences selecting conflicting backends. Using `--cfg` instead moves all backend selection control to the toplevel executable. This commit switches to the following RUSTFLAGS to enable backends: - `--cfg curve25519_dalek_backend="fiat"`: uses `fiat-crypto` - `--cfg curve25519_dalek_backend="simd"`: uses nightly-only SIMD
2022-12-09 08:42:52 +00:00
Add #![no_std] (fixes #16) Use ::core in lieu of ::std, allowing this crate to be usable in #![no_std] environments. Gates features that presently depend on ::std (presently just rand) behind a "std" cargo feature, which is enabled by default.
2017-01-14 01:43:08 +00:00
[features]
Clean up backend features and vendor curve25519_dalek_derive (#531) * Vendor import unsafe_target_features as curve25519-dalek-derive Co-authored-by: Jan Bujak <jan@parity.io> * Remove feature gates from avx2/ifma * Add buildtime compile diagnostics about backend selection * Add build script tests * Documentation changes * Disable simd related features unless simd was determined via build * Add note and test about the override warning when unsuccesful * Reduce complexity in build gating via compile_error --------- Co-authored-by: Jan Bujak <jan@parity.io> Co-authored-by: Michael Rosenberg <michael@mrosenberg.pub>
2023-06-22 05:46:27 +00:00
default = ["alloc", "precomputed-tables", "zeroize"]
Weakly activate `zeroize?/alloc`; MSRV 1.60 (#485) Previously `alloc` implicitly activated `zeroize` via `zeroize/alloc`. This commit switches to weak feature activation as added in Rust 1.60, only activating `zeroize/alloc` if the `zeroize` dependency is explicitly activated (which it is by default).
2022-12-27 10:12:55 +00:00
alloc = ["zeroize?/alloc"]
Rename `basepoint-tables` to `precomputed-tables` (#499) This is the name we adopted for a similar feature in @RustCrypto. It's a bit less jargony and also leaves the door open in the future to other types of precomputed tables.
2023-01-19 19:04:22 +00:00
precomputed-tables = []
Make scalars always reduced (#519) * Removed Scalar::{from_bits, from_bytes_clamped}; all constructible scalars are now reduced mod l * Made Scalar::reduce() not pub; fixed test warning * Added benches for scalar add/sub/mul * Docs * Added EdwardsPoint::mul_base_clamped and gated Scalar::from_bits behind legacy_compatibility * Added unit test for Mul impl on unreduced Scalars * Added Montgomery::mul_base_clamped * Added BasepointTable::mul_base_clamped * Removed invalid scalar arithmetic test; this functionality is no longer supported * Made clamp_integer() const * Updated readme and changelog * Added BasepointTable::mul_base_clamped to tests * Added proper deprecation notice to Scalar::from_bits; added legacy_compatibility to Makefile and docsrs flags
2023-03-28 22:12:24 +00:00
legacy_compatibility = []
curve: implement `ff` and `group` traits (#562) Originally authored by @str4d as #473
2023-08-27 20:41:06 +00:00
group = ["dep:group", "rand_core"]
Add PrimeFieldBits support to Scalar (#579) Co-authored-by: Michael Rosenberg <micro@fastmail.com> Co-authored-by: pinkforest(she/her) <36498018+pinkforest@users.noreply.github.com>
2023-09-20 03:21:43 +00:00
group-bits = ["group", "ff/bits"]
Bump `digest`, `ed25519`, `signature`, and `sha2` (#676) Bumps the aforementioned dependencies to their latest (pre)releases.
2025-07-07 17:34:26 +00:00
digest = ["dep:digest"]
Implement Lizard encoding/decoding (#826) * Vendor lizard hash to curve from Signal * Add invalid Lizard encoding test * Added lizard details to readme and changelog * Upgrade ristretto.sage to Python3 * Add lizard test vector generation to ristretto.sage * Added map_to_curve and its inverse * Use CtOption instead of bitmasks; other cleanup * Add README to lizard folder * Split map_to_curve into map_to_curve and map_to_curve_restricted; make its inverse return 16 elements * Consolidate Ristretto Elligator functions into its own file
2025-10-24 21:20:50 +00:00
lizard = ["digest"]
Change `Scalar::from_canonical_bytes` to return `CtOption` (#472) This is helpful for implementing `ff::PrimeField::from_repr`. Also changes `Scalar::is_canonical` to return `Choice`.
2022-12-12 22:38:04 +00:00
Clean up backend features and vendor curve25519_dalek_derive (#531) * Vendor import unsafe_target_features as curve25519-dalek-derive Co-authored-by: Jan Bujak <jan@parity.io> * Remove feature gates from avx2/ifma * Add buildtime compile diagnostics about backend selection * Add build script tests * Documentation changes * Disable simd related features unless simd was determined via build * Add note and test about the override warning when unsuccesful * Reduce complexity in build gating via compile_error --------- Co-authored-by: Jan Bujak <jan@parity.io> Co-authored-by: Michael Rosenberg <michael@mrosenberg.pub>
2023-06-22 05:46:27 +00:00
[target.'cfg(all(not(curve25519_dalek_backend = "fiat"), not(curve25519_dalek_backend = "serial"), target_arch = "x86_64"))'.dependencies]
workspace: use a global patch.crates-io to avoid duplicates (#793) When pulling crates via git (to grab non-released yet fixes or otherwise), the `path = "../"` in each crate crates duplicates unless you pull the whole tree in your local `[patch.crates-io]`. This creates issues in downstream packaging (nix, ...) where a crate version can only appear once. Those are somewhat difficult to diagnose. Using a `[patch.crates-io]` in the workspace serves the same purpose but does not create the duplication in consumers' tree.
2025-07-18 14:26:13 +00:00
curve25519-dalek-derive = "0.1"
Enable unexpected cfgs lint (#656) Previously, the only way to configure this lint was using a build.rs file, but now it can be done using Cargo.toml as well.
2024-07-26 02:24:39 +00:00
[lints.rust.unexpected_cfgs]
level = "warn"
check-cfg = [
'cfg(allow_unused_unsafe)',
Make AVX512IFMA opt-in backend (#695) * Make AVX512IFMA opt-in backend * Updated README to have backend info * Added entry to changelog --------- Co-authored-by: Michael Rosenberg <michael@mrosenberg.pub>
2024-09-08 05:13:36 +00:00
'cfg(curve25519_dalek_backend, values("fiat", "serial", "simd", "unstable_avx512"))',
Enable unexpected cfgs lint (#656) Previously, the only way to configure this lint was using a build.rs file, but now it can be done using Cargo.toml as well.
2024-07-26 02:24:39 +00:00
'cfg(curve25519_dalek_diagnostics, values("build"))',
'cfg(curve25519_dalek_bits, values("32", "64"))',
'cfg(nightly)',
]
Reference in a new issue Copy permalink