| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since a guard can have a bunch of addresses, and the guard is
permitted if any one of those addresses is permitted, then we might
decide to use a guard with some non-permitted addresses. Thus, we
need to filter those addresses before returning the view of the
guard as a FirstHop.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't need to restrict based on bits in the key id any longer,
since we have a real filter.
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
The guard filter is now a set of restrictions that can be placed on
allowable guards.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Use impl_standard_builder more and remove manual Default/builder impls
See merge request tpo/core/arti!594
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Upgrade to float_eq 1.0.0
See merge request tpo/core/arti!591
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Config handling and logging fixes
Closes #480
See merge request tpo/core/arti!589
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Prompted by review
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/589#note_2813596
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Right now this is an IEFI and therefore a no-op.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
It contains only sections, but we want to detect when that is a problem!
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
We're going to call this new closure another time.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Without this, if the substructure is provided, these fields are
mandatory within it.
|
| |\ \ \ \ \
| | |/ / /
| |/| | |
| | | | | |
# Conflicts:
# crates/arti-client/Cargo.toml
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add "full" and "experimental" features to arti, arti-client, and below.
Closes #499
See merge request tpo/core/arti!584
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Rustls uses ring, which uses code from BoringSSL, which derived from
OpenSSL before OpenSSL changed their license. So ring is currently
under 3BSD/SSLEay licenses, which aren't GPL-compatible, which may
be a problem for some people.
See #493.
|
| | |\ \ \ \ \
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | | |
Fix several clippy issues, most with nightly
See merge request tpo/core/arti!588
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Without this, clippy is error-free, but `cargo test` somehow gives a
warning.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
There is not, apparently, an eprintln equivalent for
allow-dbg-in-tests.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is apparently a new warning from clippy nightly, documented in
https://rust-lang.github.io/rust-clippy/master/index.html#significant_drop_in_scrutinee .
I'm not in love with the temporary variables that this warning wants
me to introduce, but it does seem like a decent way to avoid some
kinds of deadlock.
|
| | | | |/ /
| | |/| | |
|
| | |\ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | | |
tor-netdir: testnet: Make construct_netdir infallible
See merge request tpo/core/arti!585
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Run rustfmt. Separate commit to make review of the substantive commit
easier.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a *lot* of unwraps. The function takes no parameters and
is used only for testing. It ought to be infallible.
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use TaskSchedule to sleep in directory bootstrapping
Closes #497
See merge request tpo/core/arti!571
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will allow somebody else to call bootstrap() if bootstrap() fails
the first time.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change also means that we need to create the handle and scheduler
earlier in the process of creating the DirMgr. If we don't, we won't
have a way to manage the task before bootstrap() returns.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change (not yet exposed as an API) will let the TorClient have
a `TaskHandle` corresponding to the directory task, letting it
make the directory task dormant as needed.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Having this alias makes it easier to implement more complex
schedules, like those used in DirMgr.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Unlike "cancel" and "fire", "suspend" and "resume" don't change any
pending timers or events: they just prevent execution of those
events for a while, and let them resume later on.
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
config: Be consistent about Option
Closes #488
See merge request tpo/core/arti!582
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As per point 3 in
https://gitlab.torproject.org/tpo/core/arti/-/issues/488
|