| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Nothing actually causes an XON to be sent yet. But this adds the code so
that anything holding the `StreamTarget` can request to send an XON.
|
| |/ / / / / |
|
| |\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | | |
maint: Avoid x-prefix in comparisons.
See merge request tpo/core/arti!3100
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This applies the fixes suggested by shellcheck (the x-prefixes were
causing the `shellcheck` job to fail; see [SC2268]).
[SC2268]: https://www.shellcheck.net/wiki/SC2268
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-proto,tor-cell: Code refactoring and add support for sending XOFF messages
See merge request tpo/core/arti!3094
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
XON/XOFF flow control will want to know how many data bytes are queued
on a stream, so the new types track that.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It now performs some validation and can return a `Result`.
We perform validation here since different cell formats may have
different maximum data lengths in the future, and `UnparsedRelayMsg`
doesn't expose the cell format so it's difficult to perform this
validation at a higher layer.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As we continue adding more functionality to streams like flow control,
we'll have more objects to pass around. This tries to group them
together.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The plan is to use `StreamSendFlowControl` (now `StreamFlowControl`) for
both outgoing and incoming directions, so a name change is needed.
This also updates some comments, and renames some related struct fields
that have the word "send" in them.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This allows us to extend the command to implement different flow control
methods. We could add new command variants for new flow control methods
instead, but I think it makes sense to have them be a single command as
they will always have a stream ID / hop location in common. This also
helps us keep the flow control logic in one place.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I don't see any further changes being needed for these types, and it
simplifies a lot of future code in tor-proto that uses these types.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
conflux: Add conflux tests for client-side SWITCH handling
See merge request tpo/core/arti!3091
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The `Ord` impl of `OooRelayMsg` already "reverses" the seqno comparison,
which means previously we were double-reversing it (leading to the ooo
cell heap logic being broken in cases where its size was > 1).
Caught by the new conflux switch handling tests.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The two mock exit legs will use this channel to notify each other of the
receipt of BEGIN cells. This will enable us to extend the tests to
support writing cells to the stream (but only after the stream is
opened).
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This abolishes the overly-long tuple used in these tests.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I am moving these out of the `relays` list, in preparation for a minor
refactoring around that part.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is about to become slightly more complex, as the mock exit will
support writing to the stream too.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
I will another test for exit-to-client transmissions, so I am
preemptively renaming its counterpart.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
config-path, dirmgr, general-addr: Remove unnecessary parentheses.
See merge request tpo/core/arti!3096
|
| | | | | | | |
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
This resolves some nightly clippy warnings.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
arti: raw: Rename `arti keys-raw remove-by-path`
See merge request tpo/core/arti!3095
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
* arti: raw: `remove-by-path` is now `remove-by-id`
* arti: raw: Adjust integration tests
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
CI: bump shadow version
See merge request tpo/core/arti!3092
|
| |/ / / /
| | | |
| | | |
| | | |
| | | | |
Mostly to get reproducibility fixes for
<https://github.com/shadow/shadow/issues/3610>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti: keys: Add arti keys raw-remove-by-path
See merge request tpo/core/arti!3059
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* CLI: Add `keys-raw` and subcommand `remove-by-path`
* arti: Add `arti::subcommand::raw` for the CLI `keys-raw`
* tor-keymgr: Add `ArtiNativeKeystoreError::UnexpectedRawEntry`,
`ArtiEphemeralKeystoreError::NotSupported`
* tor-keymgr: Add `tor-keymgr::raw` module
* tor-keymgr: Add `Keystore::remove_unchecked`
* tor-keymgr: Change `Keystore::list` to return `KeystoreEntry`
* tor-keymgr: Add field `KeystoreEntry::raw_id`
* doc: Update keys.md
* doc: Add raw.md
* tor-keymgr: BREAKING: `UnrecognizedEntryError::new` associated
function is now only accessible within the crate `tor-keymgr`
* tor-keymgr: BREAKING: `UnrecognizedEntryId` is renamed to
`UnrecognizedEntry`
* tor-keymgr: BREAKING: `KeyMgr::list()` and `Keystore::list()`
now return `Result<Vec<KeystoreEntryResult<KeystoreEntry>>>`
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-proto: Handle incoming XON/XOFF messages
See merge request tpo/core/arti!3054
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Moves the `DataWriter` impl to immediately after the definition.
|
| | | | | | | |
|