| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| |/
|
|
|
| |
It cleans up and changes a few things. Changelog at
https://github.com/maybenot-io/maybenot/blob/main/crates/maybenot/CHANGELOG.md
|
| |\
| |
| |
| |
| | |
proto: Move implementation-agnostic conflux parts to a new module
See merge request tpo/core/arti!3229
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This enables us to make the conflux handler logic
implementation-agnostic (we want to avoid using `CircuitCmd` here,
because it is specific to client circuits).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves the shared types under `tor_proto::conflux`.
Note: the shared types currently import `CircuitCmd` from `client`. A
future commit will change the signature of `handle_msg` to return
something other than `CircuitCmd` (this will also improve readability,
because in reality, that function can never return most `CircuitCmd`
variants).
|
| | |
| |
| |
| |
| |
| |
| | |
`tor_proto::conflux` is where the shared conflux logic will live.
Soon the generic parts of the conflux handlers will be moved there
(whereas the client-specific `AbstractConfluxMsgHandler` impl will
continue living under `tor_proto::client`).
|
| | |
| |
| |
| |
| |
| | |
This will enable us to pull `ConfluxMsgHandler` outside of the `client`
module (this is needed because relays are meant to use this type as
well, but with a different `AbstractMsgHandler`)
|
| |\ \
| |/
|/|
| |
| | |
proto: Define a new composable SinkBlocker type.
See merge request tpo/core/arti!3228
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This type wraps a futures::Sink, and allows it to be temporarily blocked
and unblocked.
I'm going to use this to implement padding-based circuit blocking,
according to the designs in !3225.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes it clearer that the tunnel shutdown is triggered correctly
(i.e. that it is enough for *one* of the legs to receive the bad SWITCH
cell).
This also updates a comment that wrongly suggests that the tunnel is
only shut down if both legs get removed from the conflux set.
|
| | |
| |
| |
| |
| |
| |
| | |
The test code now creates the params (which enables it to build test
cases that use various params).
Resolves a TODO.
|
| | | |
|
| | |
| |
| |
| | |
Also removes all the TODOs related to #2031 (which is now addressed).
|
| | |
| |
| |
| | |
Closes #2031
|
| | |
| |
| |
| | |
This partially addresses #2031
|
| | |
| |
| |
| |
| |
| | |
This will be needed for the SWITCH seqno validation logic.
Part of #2031
|
| | |
| |
| |
| |
| |
| | |
These will be used for validating SWITCH cells.
Part of #2031
|
| | |
| |
| |
| |
| |
| |
| | |
We no longer need to clone `CongestionWindowParams` now that it
implements `Copy`.
Resolves a clippy warning.
|
| | |
| |
| |
| |
| | |
These will likely always just be a collection of integers (lightweight
to copy).
|
| |\ \
| | |
| | |
| | |
| | | |
Circuit padding: note when cells are sent and received
See merge request tpo/core/arti!3222
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
(This was so much easier than reporting on the send side.)
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(This is what required us to stick a padding controller handle in each
CircEnt, and what required us to accompany each queued cell with a
QueuedPaddingCellInfo. Ouch!)
|
| | | |
| | |
| | |
| | |
| | | |
This requires some annoying plumbing to make sure that the right
types wind up in the right places.
|
| | | |
| | |
| | |
| | | |
(I'm about to add more fields.)
|
| | | |
| | |
| | |
| | | |
Also, use it to report that we have queued normal data.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We'll need this so that we can tell the right padding machine(s)
which of them just had a queue flush.
This is not yet 100% done; the unfinished parts are marked with
XXXXs.
|
| | |/
|/| |
|
| |\|
| |
| |
| |
| | |
Define and implement a backend padding API, based on maybenot.
See merge request tpo/core/arti!3185
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
There are incomplete pieces, marked with "TODO circpad".
There is no integration into the circuit reactor code yet.
Part of #63
|
| |\ \
| |/
|/|
| |
| | |
proto: Refactor channel handshake code for upcoming relay handshake
See merge request tpo/core/arti!3182
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Initiator always know if they will authenticate or not. Responder is
different as a relay doesn't know until the end of the handshake if it
is responding to a relay or a client.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These are following the review of MR 3182. They are put in a single
commit because the git absorb has a large amount of conflicts on rebase
and this commit allows the reviewers to see what happened.
The base branch was rebased on main due to the need for 3184.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| | |
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| |
| |
| | |
In the spirit of avoidin code duplication.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
All initiator handshake will implement this in order to get access to
the helper function to receive the relay responder cells.
Relay will implement this in future commits.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Client and relay handhsake share a lot of code because they both
send/recv the same cells, just handles them differently for
verification.
This is the base trait for all handshake implementing basic getters and
VERSIONS cell handling.
This will allow the RelayInitiatorHandshake and RelayResponderHandshake
to use this common code.
See, traits are fun. Win-win-win.
Signed-off-by: David Goulet <[email protected]>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The ClientInitiatorHandshake holds a "tls" sink but the very first thing
we do is transform it to a ChannelFrame<T>. Instead, just store the
frame to the object directly so we can then use a channel frame
uniformily accross its lifetime.
This will be useful for the future refactoring paving the way for relay
channel authentication.
Signed-off-by: David Goulet <[email protected]>
|
| |\ \
| |/
|/|
| |
| | |
various crates: Switch to "assert in const" pattern
See merge request tpo/core/arti!3217
|