| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
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`.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I'm about to remove the old testing APIs from GurdMgr that took in a
NetDir in each function: adding this will make that possible.
|
| | | | | | |
|
| | | | | | |
|
| | | |/ /
| |/| |
| | | |
| | | | |
We require these for NetDirProvider, so this shouldn't be a big reach.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Spelling fixes and normalizations on some high-level crates
See merge request tpo/core/arti!835
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
bridge desc: Make BridgeDescProvider DynClone
See merge request tpo/core/arti!834
|
| |/ / /
| | |
| | |
| | |
| | | |
This allows the use of Box<dyn BridgeDescProvider> in callers,
since Box<dyn BridgeDescProvider> is now Clone.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Fix typos
See merge request tpo/core/arti!833
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| | |
bridgedesc: yaks for persistent storage
See merge request tpo/core/arti!827
|
| | |
| |
| |
| |
| |
| | |
This was confusing, because it's the output of the donwload, but
nowhere near the output of the whole process. And it's going to
become even less so.
|
| | |
| |
| |
| | |
It deserves this treatment, I think.
|
| | |
| |
| |
| |
| | |
This gives names to things and makes things clearer, and this will be
even more true in a moemnt.
|
| | |
| |
| |
| | |
We're going to want to reuse this for handling cached stuff.
|
| |/ |
|
| |\
| |
| |
| |
| | |
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.
|
| |\ \
| |/
|/|
| |
| | |
guardmgr: bridges config plumbing
See merge request tpo/core/arti!826
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
This will avoid having to make bridge-related trait features in
GuardMgr conditional, which would be non-additive.
|
| | |
| |
| |
| | |
This is the validation which is called for by the documentation.
|
| | |
| |
| |
| |
| | |
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.
|
| |\
| |
| |
| |
| |
| |
| | |
Suppress new clippy warnings in 1.65
Closes #587
See merge request tpo/core/arti!824
|
| | |
| |
| |
| | |
These are newly present on 1.65. We can address them later.
|
| | | |
|
| | |
| |
| |
| |
| | |
This is a temporary workaround for #587 until we get it fixed for
real.
|
| |/
|
|
|
| |
We were doing `find -name '*.rs'`, but `find . -name '*.rs'` (with the .)
is more standard.
|
| |\
| |
| |
| |
| | |
set all crate edition to 2021
See merge request tpo/core/arti!822
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Provide an implementation of BridgeDescProvider
See merge request tpo/core/arti!820
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The RetryDelays are being triggered for the 2nd time here, so their
timeouts can be longer. We must bump the sleep to make sure we don't
have a flaky test.
|
| | | |
| | |
| | |
| | | |
Worsify formatting as demanded by rustfmt.
|
| | | |
| | |
| | |
| | |
| | | |
This involves breaking the calls to `new_bridges.remove` into a helper
that does the logging.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Prior to the previous commit, set_bridges would malfunction if there
were bridges which where (i) in current (ii) in queued or running
(iii) in the new bridge set.
This test failed then and passes now.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was fundamentally confused and irregular. Now it is more
regular: it does the same things to all the elements of Tracked,
and a simple filtering on current.
This fixes a bug, for which I'm about to add a test case.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We'll use this in a moment.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/820#note_2850269
|