| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
proto: Move the control channels to RelayReactor
See merge request tpo/core/arti!3387
|
| | | | |
| | | |
| | | |
| | | | |
We need to give the control channels higher priority here.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Control messages are handled in RelayReactor instead of BackwardReactor.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This only moves the control/command fields to RelayReactor. The next
step is to actually implement the control message handling and dispatch.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-dirserver: Bump MSRV from 1.83 to 1.86
See merge request tpo/core/arti!3385
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I noticed that when doing `cargo generate-lockfile` in the workspace
root, it was locking dependencies to 1.83 compatible versions. It turns
out tor-dirserver started on MSRV 1.83 after we already bumped to 1.85,
and has been missed in MSRV updates ever since.
I've found no indication it is intentionally getting this special
treatment and am assuming it is a mistake.
Signed-off-by: hashcatHitman <[email protected]>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
impl ItemValueParseable for SharedRandStatus
See merge request tpo/core/arti!3380
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This may not be the best utility type to use for lots of the
fixed-length byte strings, but we *are* using it a lot in the old and
now the new parser.
Implement From and Into.
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti: Mark restricted-discovery as non-experimental
See merge request tpo/core/arti!3384
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change is needed to satisfy `maint/cargo_sort`
|
| | | | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
As per the team decision from the 14 Oct Arti sync.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't want to create new files just when creating a `InertTorRelay`.
We should only generate the keys before bootstrapping.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
relay: Implement a first relay background task
See merge request tpo/core/arti!3363
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We have bootstrap() to prepare everything we need before starting the
relay which yields a TorRelay.
This commit then adds a run() function which starts the relay by
launching background task. At the moment, we only have one task and it
is the channel expiry one.
The relay blocks on the task handle set until one task is on error or
stops which leads to shutting down the relay.
Part of #2217
Signed-off-by: David Goulet <[email protected]>
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a background task in charge of expiring closing channels and
future work is to also prune duplicate channels.
This is not used nor called at this commit, next commit will add the
task handling.
Part of #2217
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: parse2: Minor fixes
See merge request tpo/core/arti!3376
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since 9ce85acb3ab0d1a0b1be6ef0f10707983f4362a3
tor-netdoc: replace impl_item_argument_as_display with NormalItemArgument
this trait impl has implications for encoding as well as parsing.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
In principle some other trait might be in scope.
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
subdoc intro items aren't inherently incoherent, but implementing them
is nontrivial. Let's reject them with a bespoke error instead.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bump MSRV from 1.85.1 to 1.86
See merge request tpo/core/arti!3382
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: blanket impl parse2 traits for Arc
See merge request tpo/core/arti!3381
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
This replaces one ad-hoc impl and will avoid having to have any more.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
proto: Add the initial implementation of the relay reactor(s)
See merge request tpo/core/arti!3369
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The `RelayReactor` now holds the sending end of the shutdown broadcast
channel, so if `RelayReactor` exits, both the forward and the backward
relay reactor will notice and shut down too.
Similarly, if the forward or backward reactor exits, the `RelayReactor`
will notice (because it select!s between the two), and will shut down
|