| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | | |
The previous "incoming" terminology was rather ambiguous.
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3348#note_3275337
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will be used by relays too (for validating incoming messages on
streams).
This is just code motion, so it's best reviewed with `--color-moved`.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The incoming one will be used for the exit relay implementation too.
Also, with this change, receiving `CONNECTED` on an incoming stream will
result in a clearer error message. Previously, the check against
receiving `CONNECTED` on an incoming stream was bundled with the
double-CONNECTED check for client data streams, so in the incoming
stream case, the error message was misleading ("Received CONNECTED twice
on a stream.").
|
| | | |
| | |
| | |
| | |
| | | |
`Arc` is already in scope, and not fully-qualifying it makes it more
readable.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This makes it easier to see which parts are implementation-agnostic
(i.e. do not import from crate::client).
|
| | | |
| | |
| | |
| | |
| | | |
The CmdChecker will be used by relays too, so I am moving it to the
shared `stream` module.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
arti config: Fix flaky watch_single_file test.
Closes #1607
See merge request tpo/core/arti!2503
|
| | | | |
| | | |
| | | |
| | | | |
Thanks to gabi for the suggestion.
|
| | | | |
| | | |
| | | |
| | | | |
Fixes: #1607
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
Fix a couple of clippy warnings from nightly
See merge request tpo/core/arti!3361
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
maint/reproducible_build: Use cp -R to placate shellcheck
See merge request tpo/core/arti!3362
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
I'm not sure I agree with this complaint - it seems like foolish
standards-wonkery - but GNU cp supports -R too and this change will
fix CI on main.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
proto: Fix typo in OutboundRelayLayer docs.
See merge request tpo/core/arti!3346
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
`OutboundRelayLayer::decrypt_outbound()` is for decrypting cells moving
*away* from the client (in the "forward direction").
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-netdoc: Be able to parse routerstatus entries in votes
See merge request tpo/core/arti!3351
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add links to torspec, and other cross-references.
Change heading fof `IgnoredPublicationTimeSp` to `publication` to
match spec and distinguish it from the `published` item in netstatus
docs.
Align several descriptions with the wording from torspec.
Remove a restatement of a fact from the spec, on the `valid_until`
field in `Lifetime`.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I have eyeballed the output and it seems to look right.
Eventually we'll have encoing code and then we'll be able to check
that things round-trip.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a test of real document structs now, albeit that it still uses
one of the types from `poc`.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This now exercises all the new parsing code.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In md consensuses the referenced document digest is in the `m` field.
This seems to be to make it similar to votes. But really the function
of the md desc hash in md rs entries is much more parallel to the
plain desc hash in plain rs entries. The way the spec has done it
means the `r` item has a needlessly different syntax.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This makes the Rust structure closer to the document structure.
Arguably, this makes the Rust structure worse. But: I'm really very
keen on avoiding handwritten parsing and printing code. And, in the
longer term, having this linkage will hopefully apply pressure to
avoid further protocol complexity/variation/chaos.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We're going to call from_net_params from the parse2 trait impl.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The rest of types::misc does this. We should probably follow suit for
consistency. Also we're going to want to add soemthing here.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This omission seems like an oversight. I thought I wanted it, but it
turns out I don't - but I think it should still be there.
|