| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | |
|
| | | | | | | |
|
| | |_|_|_|/
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
All of the pieces are in place for this now.
Some of the pieces are not entirely complete or correct at this point:
that's sorted out by other MRs already open.
Currently there is no encoding, no verification functdion, and no
tests. Encoding depends on another oustanding MR (arti!4058).
Verification depends on the rework in arti!4065.
Tests are still to come.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
netdoc: Add fuzzing support for parse2 with authcert, mds
See merge request tpo/core/arti!4068
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Bump derive-deftly to 1.11.3 to get $impl
See merge request tpo/core/arti!4083
|
| | | |_|/ / /
| |/| | | |
| | | | | |
| | | | | | |
New beta semver policy means we should pin the patchlevel.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The actual item field isn't in the struct yet, because that would
produce conflicts with other outstanding work in this same struct.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will let us encode consensus signatures sections.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This defines ordering of routerstatus items.
|
| | | | | | | |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a nontrivial type with much weirdness to do with publication
times etc., so let's mark this as incomplete until we have a round
trip test.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We must reject unknown objects unless noted otherwise.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
No functional change.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Changes ItemPresent to accept but ignore additional arguments and/or an
object.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Adds the actual keyword for a present object to the test.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit adds a test for ItemPresent in terms of encoding and
decoding.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit adds the ItemPresent type, which is intended for token types
where the mere presence implies a truthful value, such as
`tunnelled-dir-server`.
For now, it lives in `ignored_impls` because it does in fact ignore
(actually rejects) everything around the item except the keyword.
The type implements ItemValueParseable and ItemValueEncodable; both
implementations being very minimal and only parsing/emitting the
keyword.
A test will be added within the next commit.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit documents a shortcoming explained on IRC that exists with
the current derive(Transparent) and generic types that are uncovered.
See E0210.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: minor fixes arising from netstatus work
See merge request tpo/core/arti!4055
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This matches C Tor and the spec.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
We need to use `-`, not `_`. So use concat! stringify!.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Now it round-trips.
|
| | | |_|_|/
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: ParseInput: improve
See merge request tpo/core/arti!4057
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes the code clearer, especially since we're going to add
attributes.
|
| | |/ / / / |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The new `Default`s have no panicking code paths.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This hopefully better shows that there's nothing to use here for general
socket types.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will allow us in the future to set custom sockopts on the socket
before calling connect().
I tested an arti proxy with tokio and async-std manually. Arti doesn't
yet support smol so I was not able to test it, but it's using the same
code as async-std so I would expect it to work.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This adds the trait type `ConnectOptions` to `NetStreamProvider` and adds
this `ConnectOptions` as an argument to `NetStreamProvider::connect()`.
You probably want to look at the changes in tor-rtcompat first, then the
rest of this commit is updating the various places we use
`NetStreamProvider`.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For now this just sets up the structure. We'll add options for TCP
later.
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti: Configuration and RPC support for deferred bootstrapping
Closes #2547
See merge request tpo/core/arti!4056
|
| | | | | | | |
|
| | | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
This option will primarily be used by integrators who want to modify
the configuration, either directly or via RPC, before launching Arti
completely.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
proto: Add a new channel -> circuit queue type
See merge request tpo/core/arti!4025
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is needed for relays as part of #2490.
Note that changing this type affects the client implementation too (i.e.
clients will start prioritizing inbound DESTROY, discarding any queued
data without forwarding it to their local streams). But that's okay,
because it will generally only affect misbehaving clients, and clients
unlucky enough to encounter a hibernating relay.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`CircuitRxSender` is no longer a `Sink`, so we don't need this import
anymore.
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This adds new a `CircuitRxSender`/`CircuitRxReceiver` queue type.
The corresponding (`Sink`-link) sender and `Stream` implementations
prioritize the delivery of `DESTROY` messages, which get delivered
immediately, even if there are other messages queued in the underlying
MPSC message queue.
We are okay with the resulting data loss, because inbound DESTROY can be
indicative of malicious activity on the circuit. We choose to err on the
safe side, and free up the resources associated with such circuits as
soon as possible. DESTROY messages are also sent by relays when they're
about to hibernate, and by clients once they've decided to stop using a
circuit. In the latter case, the lack of an `RELAY_COMMAND_END_ACK`
does mean that this prioritization can cause data loss in cases where
the client closes the circuit immediately after END-ing a stream.
However, this is a deficiency in the protocol, and not something we want
to fix by implementing custom flushing logic in the reactor. See
torspec#196 and the discussion in #2490.
Part of #2490
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This passes now that we can build a `DataStream` without a
`ClientDataStreamCtrl`.
|