mirrors/arti.git/crates/tor-netdir, branch arti-v0.0.4

Bump tor-netdir and tor-guardmgr versions

2022-01-31T16:05:34Z

tor-netdir needs to bump because tor-netdoc bumped, even though there were no other changes in tor-netdir. Whoops. tor-guardmgr needs to bump because it already published, with the older tor-netdir.

Bump the patch version of every crate that changed since 0.0.3

2022-01-31T15:30:52Z

Bump all crate versions to 0.0.3.

2022-01-11T14:40:32Z

Minimize the required version for each dependency.

2022-01-08T00:08:58Z

I found these versions empirically, by using the following process: First, I used `cargo tree --depth 1 --kind all` to get a list of every immediate dependency we had. Then, I used `cargo upgrade --workspace package@version` to change each dependency to the earliest version with which (in theory) the current version is semver-compatible. IOW, if the current version was 3.2.3, I picked "3". If the current version was 0.12.8, I picked "0.12". Then, I used `cargo +nightly upgrade -Z minimal-versions` to downgrade Cargo.lock to the minimal listed version for each dependency. (I had to override a few packages; see .gitlab-ci.yml for details). Finally, I repeatedly increased the version of each of our dependencies until our code compiled and the tests passed. Here's what I found that we need: anyhow >= 1.0.5: Earlier versions break our hyper example. async-broadcast >= 0.3.2: Earlier versions fail our tests. async-compression 0.3.5: Earlier versions handled futures and tokio differently. async-trait >= 0.1.2: Earlier versions are too buggy to compile our code. clap 2.33.0: For Arg::default_value_os(). coarsetime >= 0.1.20: exposed as_ticks() function. curve25519-dalek >= 3.2: For is_identity(). generic-array 0.14.3: Earlier versions don't implement From<&[T; 32]> httparse >= 1.2: Earlier versions didn't implement Error. itertools at 0.10.1: For at_most_once. rusqlite >= 0.26.3: for backward compatibility with older rustc. serde 1.0.103: Older versions break our code. serde_json >= 1.0.50: Since we need its Value type to implement Eq. shellexpand >= 2.1: To avoid a broken dirs crate version. tokio >= 1.4: For Handle::block_on(). tracing >= 0.1.18: Previously, tracing_core and tracing had separate LevelFilter types. typenum >= 1.12: Compatibility with rust-crypto crates x25519-dalek >= 1.2.0: For was_contributory(). Closes #275.

extend lints to include 'clippy::all'

2021-12-28T20:15:40Z

Merge branch 'reconfigure' into 'main'

2021-12-13T14:49:23Z

Make most arti-client fields reconfigurable. See merge request tpo/core/arti!181

tor-netdir: Resolve an XXXX about type ugliness

2021-12-08T17:32:44Z

We had no function to infallibly convert BoundedInt32<{0 or 1},H> into a u32, even though we could have. Because of that, we were treating weight_scale as an i32 when logically it's a u32 or a NonZeroU32. Moreover, it turns out we were using an incorrect minimum for the bwweightscale param, which would in theory have allowed the authorities to make us divide by zero. This patch introduces the necessary From<> implementation and uses it. It corrects the binimum bwweightscale, and prevents a division-by-zero issue in case weight_scale is zero.

Remove a couple of spec-related XXXXs in tor-netdir.

2021-12-08T16:12:33Z

I've opened torspec!54 to fill in the missing parts of the spec about these issues.

Upgrade to digest v0.10.0

2021-12-08T01:33:46Z

We generally try to track the latest rust-crypto traits when we can: fortunately, this upgrade didn't break much, considering.

Make override_net_params take effect sooner.

2021-12-08T00:26:01Z

This is still not as soon as I'd like: a real change here will require refactoring DirMgr::notify().