| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | | |
Now we can use a group of bridges as the basis for a sample of
guards.
|
| | | |
| | |
| | |
| | | |
This will be necessary for bridges.
|
| | | |
| | |
| | |
| | | |
This is a trickier case, since we have to deal with weights.
|
| | | |
| | |
| | |
| | | |
Two more simple cases that can use Universe instead of Netdir.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In this and the upcoming commits I'll be changing how guards related
to `NetDir` and to `Relay`. Previously, a guard could only come
from (or be updated from) a `Relay` in a `NetDir`. Soon it will be
able to be built from a bridge as well.
To do this, I'm defining a `Universe` trait (name negotiable) that
represents a set of things that may be guards. I'm going to
continue extending its functionality until there are no more
methods in guard.rs or sample.rs that take `NetDir`.
This commit removes most of the usage of `NetDir` and `Relay` in
`guard.rs`.
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| | |
Use a vector, since we may (someday) want to allow a Guard to have
multiple PtTargets.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
refactor config reload triggering
Closes #562
See merge request tpo/core/arti!819
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| |\ \
| |/
|/|
| |
| | |
remove unused dependancies
See merge request tpo/core/arti!817
|
| |/ |
|
| |\
| |
| |
| |
| | |
Upgrade and update dependencies
See merge request tpo/core/arti!816
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Use ByRelayIds to hold guards in GuardSet
See merge request tpo/core/arti!808
|
| | |
| |
| |
| | |
These will need a bigger overhaul: see #612 and #611.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This has subtleties; the comments try to explain them.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This is necessary for the (somewhat undesirable) lookup_ids function
to return an ID that the dirmgr can actually use to report successes
and failures.
As noted, lookup_ids will create problems down the road when we
implement relays. We should refactor it out before then.
|
| | |
| |
| |
| |
| |
| | |
To see if we can add a relay as a guard, we need a conservative
test: any IDs in common with the given relay prevent us from adding
it.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This required a number of changes, which I've tried to document.
I've taken a conservative approach to modification, and I'm not
using any of the by_*_mut() functions (yet). For cases which
potentially modify the whole set, I'm using into_values() and
collect() to ensure that it's re-indexed correctly, even though the
identities don't change.
I introduce some "TODO pt-client" comments here which I will resolve
in the next commit(s).
|
| | | |
|
| | |
| |
| |
| |
| | |
These are the ones that turned out to be necessary while converting
guard samples to use ByRelayIds.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Misc minor changes to BridgeDescProvider APIs
See merge request tpo/core/arti!812
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will enable us to impl FlagEvent for it.
|
| | | |
| | |
| | |
| | |
| | | |
The bridge descriptor manager wants to index data structures by the
BridgeConfig.
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
ptmgr: Add a fuzzer for ptmessage.
See merge request tpo/core/arti!814
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
ptmgr::ipc: Try an alternate approach to initial quotes.
See merge request tpo/core/arti!813
|
| | |/ /
| | |
| | |
| | | |
This lets us use `chars()` rather than `char_indices()`.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Two misc minor changes, for descriptor downloading
See merge request tpo/core/arti!811
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is currently nightly-only and is blocked on an unresolved API
question:
https://github.com/rust-lang/rust/issues/71503
|
| |/ / /
| | |
| | |
| | |
| | | |
I want one of these for the bridge descriptor downloader, and they
seem reasonable to me.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-cell: Assert data length in Data cells
See merge request tpo/core/arti!800
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This commit adds a `debug_assert!` macro into the `new_unchecked()`
function of the Data cell. Beside this, it also fixes a misleading
comment regarding that limit.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Misc minor changes to tor-dirclient, for descriptor downloading
See merge request tpo/core/arti!810
|
| | | | | |
|
| | | | | |
|