| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Define drop behaviour of IPT establisher, wrt status watch
See merge request tpo/core/arti!1516
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was introduced in c82cda85d69d
tor-basic-utils: DropNotifyWatchSender: use DropNotifyEofSignallable
and already, then, the is_eof() method is redundant.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | | |
hsservice: Use correct circparameters_from_netparameters fn
See merge request tpo/core/arti!1520
|
| |/ / /
| | |
| | |
| | | |
I had incorrectly thought that this function was private.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tor-proto: Make ClientCirc::allow_stream_requests take a HopNum.
Closes #1009
See merge request tpo/core/arti!1519
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds a test that checks if the reactor is shut down if it receives
an incoming stream request from an unexpected hop.
Part of #1009
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For consistency with the other `ClientCirc` APIs,
`ClientCirc::allow_stream_requests` now takes a `HopNum` argument. Upon
receiving an incoming stream request, the reactor now checks if the
request came from the hop specified in `allow_stream_requests` (and if
it came from a different hop, the circuit is closed).
Part of #1009
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-hsservice: Change IptEstablisher::new to take RelayIds
See merge request tpo/core/arti!1517
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The IptEstablisher needs to continuously maintain the IPT even as the
netdir is updated. Whereas, the IPT manager just wants to select the
relay from the netdir once and then only think about the relay
identity.
So it makes sense for the establisher to do necessary lookups of the
relay's ids in the netdir.
|
| |\ \
| | |
| | |
| | |
| | | |
hsservice: new rend_handshake module
See merge request tpo/core/arti!1512
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This code has most of what we need to go from an INTRODUCE2 message
we've just received to the point where we've connected to the
rendezvous point and we're waiting for a stream of BEGIN messages.
Unfinished pieces are marked with TODO HSS.
Most of #980.
|
| | | | |
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
tor-bytes: deprecate always_bug with From trait
See merge request tpo/core/arti!1500
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This commit deprecates the `EncodeError::always_bug` function with a
`From<EncodeError> for Bug` trait, which is a more semantically correct
way to perform this action.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
test: add a test for missing NETINFO cells
See merge request tpo/core/arti!1501
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This commit adds a unit test to the `tor_proto::handshake` module,
which tests the behavior when no NETINFO cell is present within a
channel.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Resolve all warnings that appear from `maint/every-crate`
See merge request tpo/core/arti!1507
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-netdir: Only select nodes that haven't been used for lower-numbered replicas.
See merge request tpo/core/arti!1494
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This just simplifies the expression a little bit. It still has the same
behaviour.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This will become useful later when we build a `HashSet` of `HsDirIndex`.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
replicas.
This implements the part of the spec that says a node that has already
been selected for a lowered-numbered replica, shouldn't be considered
when choosing `spread` nodes for any other higher-numbered replicas.
Note: previously, the test added in this commit wouldn't have passed
(because `NetDir::hs_dirs` used to return duplicate relays under some
circumstances).
Part of #960
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This makes `ring_items_at()` take an extra parameter which specifies
whether an item is acceptable or not. The newly added filtering
capabilities will be used to implement the part of the spec that says
that if a node was selected for a replica, then it shouldn't be
considered when choosing `spread` nodes for any other higher-numbered
replicas.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This updates the docs to reference the `spread` parameter (rather than
`spread_fetch`).
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
The spread should be either `hsdir_spread_store` or
`hsdir_spread_fetch`, depending on whether we're uploading or
downloading descriptors.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
tor-hsservice: Have IptEstablisher::new() return the status watch
See merge request tpo/core/arti!1511
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The IPT manager is going to want to separate the IptEstablisher
struct (which contains the Drop signal) from the watch receiver.
We could add an accessor to clone the watch, but the copy in the
IptEstablisher would be redundant.
This makes new()'s signature a bit funky but it's an internal method
so I think that's fine.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-dirclient: Add support for uploading descriptors.
See merge request tpo/core/arti!1505
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
It's simpler to always use a `String` to represent directory request bodies.
We no longer need the `StringBody` trait.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The hsdir publisher will send the `HsDescUploadRequest`s to the
appropriate directory using `send_request()`.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, the `Requestable` trait assumed the body of the request
would always be empty (`http::Request<()>`). This change replaces the
hardcoded `()` body type with the `Requestable::Body` associated type
(which will allow implementors to create requests with non-empty
bodies). This will enable us to reuse the `Requestable` trait for
building `POST` requests for uploading descriptors.
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
`download()` is actually a general-purpose function for sending HTTP
requests on a stream. We will soon repurpose it for `POST`-ing
descriptors, so let's rename it to `send_request`.
|