mirrors/arti.git/crates/tor-hscrypto/src, branch arti-v1.4.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.32025-03-18T16:09:44Zsquash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T14:47:35Zurn:sha1:895bc807f106e359d35522a3ad5f288ba6cf6a9c
- The Rng::gen() functions have been renamed to Rng::random().
squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T14:08:19Zurn:sha1:9c1958c25a0ad7ba77d8d7127db0e1ce4818ee25
- The Standard distribution has been renamed to StandardUniform.
squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T13:02:40Zurn:sha1:e57c16e03ddf07dffaa4dda4fa1b4101ac02a233
- The rand::distributions module has been renamed to rand::distr
Wrap ed25519-dalek types.2025-03-18T12:45:28ZNick Mathewsonnickm@torproject.org2025-03-17T18:31:42Zurn:sha1:d50e945a5286d89d75892878ff3aa9ed7ebed1f7
With this change, we'll no longer need to expose the types from
dalek-cryptography as part of our API, and we'll have more freedom
to switch ed25519 implementations, or to upgrade to a newer
`rand` ahead of their schedule.
Unlike with x25519-dalek, I had to tweak the API a bit: There's no
way to get a &PublicKey out of a Keypair now, and implementing the
old ed25519-dalek traits seemed unnecessary.
tor-hscrypto: Implement Display for TimePeriod2025-03-13T18:22:40Zhjrgrn3874-hjrgrn@gitlab.torproject.org2025-03-13T18:22:40Zurn:sha1:fd21de5b82646524543dd2d5eae34b68fceeb91eclippy: deny `mod_module_files`2025-01-06T23:09:41ZSteven Engleropara@torproject.org2025-01-06T23:02:49Zurn:sha1:252a3a803b2db65792db5bd51dee8950d8557e0d
Denies 'mod.rs' files for consistency.
https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files
tor-hscrypto: Move encodable key trait impls from tor-key-forge.2024-12-11T16:13:10ZGabriela Moldovangabi@torproject.org2024-12-11T16:11:54Zurn:sha1:cf6998c7e8fa42d29847759d96af3c5fe02ab5f0
This enables us to get rid of the tor-key-forge -> tor-hscrypto
dependency, partially addressing the TODO from `tor_key_forge::traits`.
This commit is mostly code motion. Best reviewed with `--color-moved`.
See also #1778
add_warnings, *: Allow clippy::needless_lifetimes2024-12-03T14:27:26ZNick Mathewsonnickm@torproject.org2024-12-03T14:15:50Zurn:sha1:64cc3f2ed3eea0b7c5cc89ae07cbdadfdc1646fb
In 1.83, this warning triggers on many of our crates.
We're thinking of fixing them all, but for now,
we're going to disable the warning.
This is part of #1765.
PoW: Consolidate feature flags into a single flag.2024-11-25T20:49:46ZWesley Aptekar-Casselsme@wesleyac.com2024-11-25T20:45:58Zurn:sha1:7846ed242bf39d9b366f47393de28056d70abec0
This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full
features with a single hs-pow-full feature.
It's possible that in the future we will want to split different schemes
into different features, but we can do that when it comes up.
For now, having this as a single flag makes it clearer what's going on,
since the previous thing was not actually expressive enough to capture
some things we care about (like "at least one pow scheme is enabled"
that works in a future-compatible way).
This change is not semver breaking since it's a experimental feature.
Related: #1751
tor-hscrypto: Add Verifier::seed() helper function.2024-11-25T18:20:11ZWesley Aptekar-Casselsme@wesleyac.com2024-10-29T14:45:05Zurn:sha1:90eecb223172c5d8fc0cbae7fee7f76819e6663c