mirrors/arti.git/crates/tor-guardmgr, branch arti-v1.0.0

Bump crate versions in preparation for Arti 1.0.0 release.

2022-09-01T12:59:49Z

Because we want to work more on ensuring that our semver stability story is solid, we are _not_ bumping arti-client to 1.0.0 right now. Here are the bumps we _are_ doing. Crates with "minor" bumps have had API breaks; crates with "patch" bumps have had new APIs added. Note that `tor-congestion` is not bumped here: it's a new crate, and hasn't been published before. ``` tor-basic-utils minor fs-mistrust minor tor-config minor tor-rtcompat minor tor-rtmock minor tor-llcrypto patch tor-bytes patch tor-linkspec minor tor-cell minor tor-proto minor tor-netdoc patch tor-netdir minor tor-persist patch tor-chanmgr minor tor-guardmgr minor tor-circmgr minor tor-dirmgr minor arti-client minor arti-hyper minor arti major arti-bench minor arti-testing minor ```

Downgrade "guard set loaded" messages

2022-08-25T15:03:19Z

These aren't interesting to the user.

enable doc_auto_cfg feature on every crate when documenting for docs.rs

2022-08-24T16:22:41Z

Merge branch 'main' into 'linkspec_refactor_v3'

2022-08-10T14:48:57Z

# Conflicts: # crates/tor-netdir/semver.md

Make sure all HasRelayIds constaints allow ?Sized.

2022-08-10T14:39:47Z

tor-netdir: Collapse by_id and by_relay_id into a single fn.

2022-08-10T14:39:46Z

There are some downstream changes required for this to work, but they are all just unit tests that could no longer infer the type of an Ed25519 key.

Final (?) API revisions for tor-linkspec

2022-08-10T14:39:37Z

With this change, each individual identity type becomes optional. The functions that expose them unconditionally are now in a "legacy" trait that only some downstream types are expected to implement. There are new convenience APIs in HasRelayIds: * to return Option<&keytype>, * to see if one identity-set contains another. This commit will break several downstream crates! For the reviewer's convenience, I will put the fixes for those crates into a series of squash! commits on this one. tor-netdir ---------- Revise tor-netdir to accept optional identities. This required some caveats and workarounds about the cases where we have to deal with a key type that the tor-netdir code does not currently recognize at all. If we start to add more identity types in the future, we may well want more internal indices in this code. tor-proto --------- In order to make tor-proto support optional identities, there were fewer changes than I thought. Some "check" functions needed to start looking at "all the ids we want" rather than at "the two known IDs"; they also needed to accommodate that case where we don't have an ID that we demand. This change will also help with bridges, since we want to be able to connect to a bridge without knowing all of its IDs up front. The protocol currently _requires_ the two current ID types in some places. To deal with that, I added a new `MissingId` error. I also removed a couple of unconditional identity accessors for chanmgr; code should use `target().identity(...)` instead. tor-chanmgr ----------- This is an incomplete conversion: it does not at all handle channel targets without Ed25519 identities yet. It still uses those identities to index its internal map from identity to channel; but it gives a new `MissingId` error type if it's given a channel target that doesn't have one. We'll want to revise the map type again down the road when we implement bridges, but I'd rather not step on the channel-padding work in progress right now. tor-guardmgr ------------ This change is mostly a matter of constructing owned identity types more sensibly, rather than unwrapping them directly. There are some places marked with TODOs where we still depend on particular identity types, because of how the directory protocol works. This will need revisiting when we add bridge support here. tor-circmgr ----------- These changes are just relatively simple API changes in the tests.

Introduce a RelayIdSet and use it in place of HashSet.

2022-08-10T14:39:36Z

This makes lookups a little more efficient. I do with that HashSet just supported this use-case, but for now this seems our best option.

Teach guard restrictions about RelayId.

2022-08-10T14:39:36Z

This implementation is (sadly) too copy-heavy or now, because HashSet can't be indexed with RelayIdRef.

Use accessors in two places where tests look at specific keys.

2022-08-10T14:39:36Z

(It's safe to require these specific keys, since we constructed the objects for testing, and we know for certain that they contain given keys.)