| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is the only way I could find in which parameter interpretation
differs between bridge guards and relay guards; with it documented,
I can remove a TODO about identifying such ways.
|
| | |
| |
| |
| |
| | |
Have the check only apply to non-bridge universes, and explain why
in a bunch more comments.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously we would call extend_sample_as_needed in only two places,
one of which called the other unconditionally. That's obviously not
necessary.
I've selected just one of them (`update_guardset_internal`) since it
fits better with the theme if that function. I've added comments
explaining what is going on.
This commit also introduces a yes/no enum for "were any guards added
while extending this set". Formerly we had a boolean, but it got
passed around so many times that I think its intent became obscure.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
What this function actually does is return the number of primary
guards whose presence (by identity) is ambiguous in a current
universe. The new name and documentation should help avoid
confusion.
The method's old name had led me astray when identifying whether it
should apply to bridges in one case. This commit also removes the
corresponding `TODO pt-client`.
|
| | | |
|
| | |
| |
| |
| | |
The code seems happy enough here for now.
|
| | |
| |
| |
| |
| |
| |
| | |
Also, add a bunch of reminders around these implementations that
`HasAddrs` returns all the address associated with you for GeoIp or
family purposes, even if they are _not_ ones that we should actually
contact you at.
|
| | | |
|
| |/
|
|
|
| |
The BridgeSet type does not necessarily need further changes... and
if it gets them, it won't be because of this comment.
|
| |\
| |
| |
| |
| |
| |
| | |
Persistently cache bridge descriptors
Closes #619
See merge request tpo/core/arti!831
|
| | |
| |
| |
| |
| |
| | |
This is more consistent with our naming elsewhere.
Suggested-by: Nick Mathewson <[email protected]>
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This explanation is slightly complicated by the fact that I think
that one of the calls to update_guardset_internal() is possibly
unnecessary, and that one of the calls that it makes is potentially
ill-advised.
I'm not going to make those changes right now, however, because they
are potentially a little destabilizing.
|
| | |
| |
| |
| |
| |
| |
| | |
Now it is an Option, and is set to None if bridges aren't enabled.
This simplifies `replace_bridge_config` a bit, and forces us to
check for `None` in a few more places.
|
| | |
| |
| |
| | |
Enforce this with assert!() and a documented panics section.
|
| | | |
|
| | |
| |
| |
| |
| | |
Also remove a bunch of now-unnecessary `allow(dead_code)`
annotations.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
We do this by checking the FirstHops we're about to return, and when
they correspond to bridges, looking up an appropriate BridgeRelay
in the current BridgeSet (if we can).
|
| | |
| |
| |
| |
| |
| | |
We already _have_ these Arc<>s whenever we construct a UniverseRef,
so there's no real point in using &refs and making these so
hard to construct.
|
| | |
| |
| |
| | |
Found while grepping for NetDir.
|
| | |
| |
| |
| |
| |
| |
| | |
The `GuardMgr` code has functionality to tell the DirMgr "Hey,
don't switch to the new NetDir yet: we still need more guard
information!" But we never want to do that if we're selecting
bridges, since they don't come from the NetDir.
|
| | |
| |
| |
| |
| |
| | |
Instead of duplicating the logic about which guard sample uses which
universe, we explicitly ask it, and then use that universe. This
will avoid trouble if/when we introduce more samples.
|
| | |
| |
| |
| | |
descriptors updated as appropriate.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This can probably be done in a simpler way, but for the moment I
would prefer to try to minimize the amount of code I'm changing
here.
|
| | |
| |
| |
| |
| |
| |
| | |
This will match our needs better and help avoid some `Arc<>`s.
It will be especially helpful for avoiding `Arc`s we don't
actually have.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I'm using an Arc<[]> here though I think that there's a chance
that a simple Vec<> would suffice. Since it's an internal type,
nothing will break if we change it later.
Also, we now switch into and out of the Bridges guard sample
as needed. However, that selection is not (yet) built from the
list of bridges. That will come soon.
|
| | | |
|
| | |
| |
| |
| | |
Also fix its behavior when using bridges.
|
| | |
| |
| |
| |
| |
| | |
The first part changes which guard set is active based on based on
the parameters, which always come from a NetDir; the second changes
the contents of the active guard set, based on a Universe.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
These arguments were used only for legacy (testing) purposes; the
tests now use `TestNetDirProvider`. This lets us simplify our
internal logic for passing a `NetDir` to our samples, and prepare
for having a `BridgeSet` to pass there instead.
This is a breaking change to `guardmgr` and `circmgr`.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
We require these for NetDirProvider, so this shouldn't be a big reach.
|
| | |
| |
| |
| |
| | |
This allows the use of Box<dyn BridgeDescProvider> in callers,
since Box<dyn BridgeDescProvider> is now Clone.
|
| |/ |
|
| |\
| |
| |
| |
| | |
tor-guardmgr: use imported WeightThreshold in one place
See merge request tpo/core/arti!825
|
| | |
| |
| |
| |
| | |
Without this, an unused import warning is generated when building
without features.
|
| | | |
|
| | |
| |
| |
| |
| | |
This will avoid having to make bridge-related trait features in
GuardMgr conditional, which would be non-additive.
|
| | |
| |
| |
| |
| | |
It doesn't seem to me like it makes sense to provide the backward
compatibility here.
|
| |/
|
|
|
| |
This does involve additional cloning. However, soon it will mean that
we can pass the whole `TorClientConfig` by reference.
|
| | |
|