| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
Found by clippy nightly
|
| |
|
|
|
| |
I don't love this change, but apparently we are trying for
"consistency".
|
| |
|
|
|
|
|
|
| |
- We make the tor-guardmgr "We have found that {} is usable" line
include the word "guard", otherwise it doesn't appear very useful to a
user in safe logging mode, since the guard gets replaced with
[scrubbed].
- The "Actually got an end cell..." message is downgraded to DEBUG.
|
| |
|
|
|
|
| |
Now that we require a version of Rust that allows
`b.then_some(v)`, clippy complains about our use of
`b.then(|| v)`.
|
| | |
|
| | |
|
| |
|
|
|
| |
In both cases I think it's fine to panic; but it's best to do so
explicitly.
|
| |
|
|
|
| |
This panics on error, and we're fine with a panic on misbehavior in
tests.
|
| |
|
|
|
|
|
|
| |
This warning kind of snuck up on us! (See #748) For now, let's
disable it. (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)
Closes #748.
|
| |
|
|
|
|
|
|
|
| |
This is in lieu of upgrading to the latest base64 crate, which has
a different API from the old one. Since we have to migrate either
way, we might as well use base64ct everywhere.
I don't think that most of these cases _require_ constant-time
base64, but it won't hurt.
|
| |\
| |
| |
| |
| | |
Add test lint blocks to all "mod test"
See merge request tpo/core/arti!937
|
| | |
| |
| |
| |
| | |
This is precisely the result of running the rune in
maint/adhoc-add-lint-blocks.
|
| |/
|
|
| |
Closes #589
|
| | |
|
| | |
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/904#note_2858480
|
| |
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/904#note_2858479
|
| |
|
|
|
|
|
|
|
| |
As per
https://gitlab.torproject.org/tpo/core/arti/-/issues/668#note_2858220
This commit is difficult to split up.
The innards of BridgeAddr and PtTargetAddr are still a bit entangled.
|
| |\
| |
| |
| |
| | |
Add tests for a bunch of code in tor-linkspec
See merge request tpo/core/arti!867
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Support building without pluggable transports
Closes #649
See merge request tpo/core/arti!898
|
| | | |
| | |
| | |
| | | |
This is unused in bridgeless configs. Fixes a compiler warning.
|
| | | |
| | |
| | |
| | | |
We've revised this a few times; now it seems plausible.
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| | |
This machinery is a bit inelegant, but it is all confined to
be within the GuardMgr crate, so IMO it should be fine for now.
|
| |/
|
|
|
|
| |
Closes #627, again.
Closes #648.
|
| |\
| |
| |
| |
| | |
Make ChannelMethod non-exhaustive
See merge request tpo/core/arti!891
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Enums with variants conditional on cargo features must be
non-exhaustive, because cargo features are supposed to be additive,
meaning that enabling a feature (which might happen due to some random
distant thing) ought not to break things using that enum.
There were surprisingly few places to fix this.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Require state ownership when using bridges
Closes #612
See merge request tpo/core/arti!889
|
| | |
| |
| |
| | |
Left unsquashed for ease of review
|
| | |
| |
| |
| |
| | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/889#note_2856874
|
| | |
| |
| |
| |
| |
| |
| |
| | |
From Unsupported. Prompted by
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/889#note_2856873
This was added in this MR.
Also add the missing semver note.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
From Unsupported. Following one of the suggestions here
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/889#note_2856873
This was added in 2c3711614908d0c9cf1663b20b67a3fc233301f4 which was
not yet in a release so this isn't a semver break. I have added
the semver note that was omitted in that MR.
|
| | |
| |
| |
| | |
Fixes #612
|
| | |
| |
| |
| |
| |
| | |
The error type needs to be convertible to GuardMgrError and also to
ReconfigureError. Neither of those is right, so we need a new error
type.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`let _ignore =` isn't great because if the function called is
currently infallible, but becomes fallible, it suppresses the
detection of the error check.
A better pattern is to specify the type of the ignored value.
I'm about to do precisely this, here.
I did a git-grep and `let _ignore =` seems very common. Let's not
deal with all those now.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make BridgeConfig be Arc, so no Arc<BridgeConfig>
Closes #635
See merge request tpo/core/arti!885
|
| | | |
| | |
| | |
| | | |
BridgeConfig is itself an Arc now, so these are redundant.
|
| | | |
| | |
| | |
| | |
| | | |
This leaves the external API of this type unchanged, but now it's much
smaller and quite cheap to clone.
|
| | | |
| | |
| | |
| | | |
This was done by !874 and #604 closed accordingly.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-guardmgr: Fix visibility of TestConfig with no features enabled
See merge request tpo/core/arti!875
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Without this, tor-guardmgr tests don't build when run without the
crate's own testing feature enabled.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
guardmgr: Remove a now-unneeded "allow(dead_code)"
See merge request tpo/core/arti!862
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | | |
Closes #650.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Fixes #653
|