mirrors/arti.git/crates/tor-circmgr/src/build.rs, branch arti-v1.0.1

channel usage: Rename CU::UserTraffic from CU::Exit

2022-08-17T09:54:41Z

As suggested in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2827246

Move ChannelUsage from tor_proto to tor_chanmgr

2022-08-17T09:54:41Z

Replace Channel::note_usage with Channel::engage_padding_activities, which unconditionally causes the channel to (start to) do netflow padding things. The condition now lives in chanmgr. Addresses https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2826094

chanmgr: Use NetDirProvider::params and Arc

2022-08-17T09:54:41Z

This gets rid of many Result(). Many parameters are renamed. Test cases of the now-impossible branch are removed. Deleting the match from padding_parameters will come in a moment. I've split off that commit since it has much whitespace noise. for now, change the error type to Void.

Introduce ChannelConfig

2022-08-16T17:39:57Z

This commit is just the necessary plumbing. The config is currently empty. We'll add something to it, for padding control, later.

Provide ChannelUsage and plumb it all the way down

2022-08-16T17:37:06Z

Channel padding depends on what the channel is being used for. We therefore need to let the channel code know this information. The implementation of the per-channel padding control logic will be in the new note_usage function, which for now is simply a stub. A future commit will introduce a `PaddingControlState` which lives in the channel frontend; consult the doc comment for that type to see why the plumbing through the channel manager terminates in the channel frontend.

dormancy: Plumb through to chanmgr reconfigure_general

2022-08-16T17:37:06Z

The chanmgr remembers the last dormancy state it was told. We invent a chanmgr-specific Dormancy which the arti-client code knows how to convert from the richer top-level dormant status. This avoids having to have everyone know all the variants of the top-level state. To call reconfigure_general, we must also obtain and plumb through a netdir. Right now we must return an internal error if there is in fact no netdir, because reconfigure_general does not yet cope with a missing netdir. Nothing actually *uses* the dormancy yet.

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.)

Introduce HasRelayIds::same_relay_ids.

2022-08-02T18:19:00Z

This method tells if two HasRelayIds contain exactly the same set of Relay identities, and is generally useful for debugging.

tor-linkspec: Refactor out traits to represent a relay's ID set.

2022-08-02T16:40:23Z

We want the set of identities supported by a relay to be extensible in the future with minimal fuss; we'd also like to make working with these ID sets more convenient. To handle that, this commit adds a new trait for "Something that has the same IDs as a relay" and a new object for "an owned representation of a relay's IDs." This commit introduces a similar trait for "Something with a list of SocketAddr, like a relay has." There's no owned equivelent for that, since Vec is already a thing. Closes #428.

tor-circmgr: Clarify and improve Protocol error.

2022-07-12T14:01:56Z