mirrors/arti.git/crates/tor-netdoc/src/doc/hsdesc/inner.rs, branch arti-v1.6.0

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

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.

tor-netdoc: Removed dependency on `once_cell`

2025-06-15T02:11:18Z

- Replaced `once_cell::sync::Lazy` with `std::sync::LazyLock`. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

Resolve clippy warnings from 1.83

2025-05-13T18:53:41Z

Now that our MSRV is 1.83, clippy is happy to make more recommendations for us.

netdoc: Make some parsing init functions fallible.

2025-03-17T16:55:57Z

I'm about to make our parsers reject some strings at construction time, so it makes sense to have these functions become fallible. This is a breaking change.

PoW: Consolidate feature flags into a single flag.

2024-11-25T20:49:46Z

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

TimerangeBound: Stop using std::ops::Bound.

2024-11-25T18:20:11Z

Fixes: #1691

Add a little test coverage for pow-params parsing.

2024-10-09T16:06:01Z

Cover some of the novel edge cases we're introducing around object parameters and repetition. This still feels awfully ad-hoc, but it's better than nothing. Co-authored-by: Micah Elizabeth Scott

hs-pow inner desc: broaden pow-params rule, disallow object for v1.

2024-10-09T16:06:01Z

We should not be restricting pow-params to occur only once at the rule level, and we shouldn't be disallowing object parameters at that level either. Instead, the v1 scheme itself needs to check for and disallow objects. Future schemes may allow object parameters. Test cases for this will be added in a subsequent commit. Co-authored-by: Micah Elizabeth Scott

hs-pow: inner doc test using canned data from C tor.

2024-10-09T16:06:01Z

This proliferates the canned hsdesc inner doc testing strategy, adding another file with data encoded with onion-pow-example running on C tor. Tests that it parses successfully, and asserts that the pow params line contents are correct. This is a positive test only. This strategy seems problematic, but it's better than nothing. Co-authored-by: Micah Elizabeth Scott

hs-pow: Change rule to require pow_params type parameter.

2024-10-09T16:05:21Z

This can now notice pow_params lines which are invalid because they have no parameters. Co-authored-by: Micah Elizabeth Scott