| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-cell: Rename for_client and for_relay
See merge request tpo/core/arti!793
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit renames the for_client and for_relay functions to
from_client and from_relay respectively, in order to indicate their
origin, as the term "for" is more likely to indicate a destination,
which is not true in that situation.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add semver.md in tor-cell for MR#793
See merge request tpo/core/arti!798
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-cell: Fix typos in msg.rs
See merge request tpo/core/arti!802
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-cell: Add comment explaing Data::MAXLEN
See merge request tpo/core/arti!801
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
This commit adds a comment explaining composition of the magic number
"11" found in the assignment of the Data::MAXLEN constant.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
tor-error: Prepare for more misc errors
See merge request tpo/core/arti!805
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
1. Import it, as we do elsewhere, and use that import.
2. Use thiserror to generate the Display impl, rather than
derive_more, as we do for errors elsewhere.
(tor_error still needs derive_more::Display for ErrorKind.)
|
| |/ / /
| | |
| | |
| | |
| | | |
This has no external API change, but makes space for other
miscellaneous errors to arrive later.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Allow GuardMgr to expose bridges as guards (part 1)
See merge request tpo/core/arti!785
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously we could only use Relay for this case, which won't work
any more: a Bridge is not a `tor_netdir::Relay`. Instead we allow
the GuardMgr to give us something that knows how to convert itself
into an OwnedCircTarget.
This change required a far amount of follow-on revisions and
refactoring, but it should all be internal to the path-building
logic.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Previously this was a private method only visible from Relay, but now
we can use it on any two HasAddrs objects.
|
| | | | |
| | | |
| | | |
| | | | |
The singleton variation here is almost never what we want.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now it contains either an `OwnedChanTarget` or an `OwnedCircTarget`,
which will let `GuardMgr` return bridges that can be used to make
circuits.
As part of this change, it was necessary to revise some
address-modification functions that applied to filters and
`OwnedChanTarget`. Now they do the smart thing, and remove only the
address that are in the `ChanMethod`. This means that the addresses
from HasAddrs are still accurate about which addresses the relay
"has".
|
| | | | |
| | | |
| | | |
| | | | |
This resolves an old TODO, and will simplify our work a little.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The most important part of this commit is to make sure that each
`FirstHopId` includes the `GuardSetSelector` from which the guard
was selected. Doing this lets us be certain that when we report
that a guard has succeeded or failed, we're reporting it in the
right context.
Additionally, this commit uses strum to make an iterator over the
samples, so that we can make sure that our "for each sample" code is
robust against future changes, and we don't miss the bridge sample.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Add two ways to change entries in an n_key_set
See merge request tpo/core/arti!797
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
The keys can change: if they do, then the entry is removed from its
previous position and inserted at the new one, possibly displacing
others.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-cell: Fix typos in msg.rs
See merge request tpo/core/arti!788
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-cell: Remove redundant match clauses
See merge request tpo/core/arti!792
|
| | |/ /
| | |
| | |
| | |
| | | |
This commit removes two redundant match clauses inside the
take_one_netinfo_addr function found inside msg.rs.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-cell: Make historical comments more concrete
See merge request tpo/core/arti!787
|
| | |/ /
| | |
| | |
| | |
| | | |
This commit extends comments that make references to historical protocol
versions of Tor, by adding the concrete protocol version numbers.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-circmgr make get_or_launch_dir_specific depend on specific-relay feature
See merge request tpo/core/arti!795
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
DirSpecificTarget in the usage was renamed apropos an MR comment but
this function name was overlooked.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
If pt-client is disabled, there are in fact no tests, so the module is
empty. But we would always want `use super::*` here.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This doesn't make sense now we've released Arti 1.0. The version
number is enough I think.
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
cleanup target dir on job completion
See merge request tpo/core/arti!786
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-cell: Avoid redundant pointer copy
See merge request tpo/core/arti!791
|
| | | |/
| |/|
| | |
| | |
| | |
| | | |
This commit changes an iteration by copying a u16 (which is 2 bytes)
instead of a pointer address, which is most likely 8 bytes on most
machines.
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Make error from bridge descriptor provider be a trait object
See merge request tpo/core/arti!796
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
We could in the future provide a version of abs_retry_time which took
an &dyn closure if that turns out to be wanted.
I think this isn't a semver break because trait implementors are
allowed to relax bounds.
|
| |\ \
| | |
| | |
| | |
| | | |
Oops: Mark some imports as pt-client only.
See merge request tpo/core/arti!794
|
| | | |
| | |
| | |
| | | |
This causes CI problems, and is entirely my fault.
|