mirrors/arti.git/crates/tor-netdoc/src/doc/hsdesc/build, branch arti-v1.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.02025-08-07T15:28:36ZSwitch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
Resolve clippy warnings from 1.832025-05-13T18:53:41ZNick Mathewsonnickm@torproject.org2025-05-13T18:53:41Zurn:sha1:b182a9d05902bc5320ab486d055521f18b6b7832
Now that our MSRV is 1.83, clippy is happy to make more
recommendations for us.
squash! 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-18T13:01:31Zurn:sha1:2f8993c22c2b86010e4fd8b5169ef0ab83f8c754
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
Always use full path to rand::thread_rng().2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T13:00:23Zurn:sha1:30f27c7f8f8028f833ea7e84a034f2416afd447b
This is partly for consistency, and partly to facilitate
a global search-and-replace.
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.
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-netdoc: Error on PowParams::V1 when hs-pow-v1 is disabled.2024-11-25T19:34:37ZWesley Aptekar-Casselsme@wesleyac.com2024-11-25T18:08:08Zurn:sha1:83b52c11e04c60b238600f159ba227f007a81ddetor-netdoc: Don't include pow_params in HsDesc when feature is disabled.2024-11-25T19:34:37ZWesley Aptekar-Casselsme@wesleyac.com2024-11-21T20:40:53Zurn:sha1:a0f5d61d344f289e7c0fdeaff1b6d3e16e261049tor-netdoc: Support writing pow-params line.2024-11-25T18:20:11ZWesley Aptekar-Casselsme@wesleyac.com2024-10-15T18:39:33Zurn:sha1:f740995ca2db08842f3306fda30aa57e0e67bd1c
I'm not particularly happy with the code that does the actual writing
out of the pow-params line, in particular the error handling there seems
very verbose. However, I don't know of a better way to structure it
given that APIs I'm working with.