| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Move an import to resolve a warning.
See merge request tpo/core/arti!1407
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Stop unconditionally marking bridges as having dir info.
Closes #638
See merge request tpo/core/arti!1408
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When we implemented bridges, we added code in 08473872abccf389 to
conditionally mark their directory info as present or not present.
But the we didn't remove the old code to mark them present
unconditionally!
Fixes #638.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
Currently we list an address for a bridge twice if it is listed both
in the bridge line and the bridge descriptor. That can't be right.
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- When the `geoip` feature flag of `tor-netdir` is enabled, perform
GeoIP lookups for all relays added to the directory and add the
resulting country code to the `Relay` struct.
- The GeoIP database is provided in a new
`PartialNetDir::new_with_geoip` constructor.
- A new trait was also added to `tor-linkspec`, `HasCountryCode`, to
enable getting this data out from other crates.
Part of onionmasq#47.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Basically, it's all ChanBuilder at some point, and ChanBuilder
has a timeout.
|
| |/ /
| |
| |
| |
| | |
This method will let the user construct a channel that isn't
stored or monitored by the ChanMgr.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
CI: Add client auth integration test.
Closes #954
See merge request tpo/core/arti!1399
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
"Fix" CI complaints about "Conversation"
See merge request tpo/core/arti!1402
|
| | | |
| | |
| | |
| | |
| | | |
I don't know if these are needed because the rules are not documented
afaict. But it seems like probably they ought to be there?
|
| | | |
| | |
| | |
| | | |
These fns are in a feature-gated impls on feature-gated structs.
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Expose channel builder in order to create channels more efficiently in external code
See merge request tpo/core/arti!1374
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
These errors aren't ignored anymore.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Explain the code for the #952 fix.
See merge request tpo/core/arti!1391
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Let's explain what Trinity did in its fix for #952, so that we know
why this code is here the next time we find it.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
clippy: Allow some of our existing code patterns
See merge request tpo/core/arti!1396
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This launders the closure so that clippy's
clippy::redundant_closure_call can't see it.
We can't have a local #[allow] because it would be on an expression,
which isn't allowed on stable.
This avoids having to use more clumsy idioms at call sites.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This fixes a needless_vec lint on nightly.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Fixes #920
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There are a number of places where we generate random Durations
in a range which starts at zero.
These call sites currently (i) have to write out Duration::ZERO
or equivalent, and (ii) would have to use gen_range_checked and expect
the result, even though it can be statically proven to be OK.
To make this slightly smoother, provide `GenRangeInfallible` and
`gen_range_infallible`.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Ideally we would be allowed to use vanilla gen_range() here, but there
doesn't seem to be a way to allow a specific clippy-forbidden method
using #[allow] and we probably don't want to make a blanket allow.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
In each of these, it is locally obvious that the range is nonempty.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
delay_bounds's implementation ensures the postcondition, so the
potential p[anic in next_delay_msec cannot happen.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We will use this in many places instead of gen_range.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
keymgr: Use Box<dyn EncodableKey> instead of Box<dyn Any>.
Closes #937
See merge request tpo/core/arti!1398
|
| | | | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1337#note_2917701
This will make it harder to accidentally return the wrong value from
`Keystore::get` (the returned value is now at least guaranteed to
implement `EncodableKey`).
Closes #937
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Overhaul send_control_message
See merge request tpo/core/arti!1367
|
| | | | | | | |
|