| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
When `hs_dirs` is removed this won't n't need to be public anymore.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The hsdir selection algorithm for uploads and downloads is different
enough to justify splitting `hs_dirs` into 2 different functions.
More specifically, when selecting the relays to upload a service's
descriptors to, the service's `hsids` need to be matched up with the
correct `ring` (using the time period) before applying `select_nodes` to
pick the replicas. This is not the case when downloading, because
for downloads select relays from the current ring.
|
| | | |/
| |/|
| | |
| | |
| | |
| | | |
These will become useful when we split `hs_dirs()` into 2 separate
functions (one for uploading/services, and another for
downloading/clients).
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We don't actually want to distinguish drop from not-drop.
|
| | | |
| | |
| | |
| | | |
Needed for ClientCirc::wait_for_close
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need a type that holds a rend_handshake::IntroRequest object
internally, but where we don't materialize that object from the
Introduce2 message inside the MsgHandler, since that's more crypto
than we want to put in that task.
|
| | | |
| | |
| | |
| | | |
This ensures that the status becomes Faulty when the reactor exits.
|
| | | |
| | |
| | |
| | | |
This does not yet do exactly what's documented, but it's closer.
|
| | | |
| | |
| | |
| | |
| | | |
(This requires us to change the type of the data sent in the
stream. I hope to put it back soon.)
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This solves some problems but introduces a few new ones; I've tried
to open comments for the latter.
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
proto: new ClientCirc::send_raw_msg function.
Closes #1010
See merge request tpo/core/arti!1525
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Closes #1010.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Upgrade num_enum dependency to 0.7
See merge request tpo/core/arti!1530
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Resolve warnings about ambiguous/redundant doc links
See merge request tpo/core/arti!1531
|
| | |/ /
| | |
| | |
| | |
| | | |
Nightly rustdoc now warns if you have a link that isn't necessary,
and if you have a link that might refer to two different things.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
hsservice: Compute rendezvous points correctly.
See merge request tpo/core/arti!1521
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This duplicates some code from hsclient as noted in the comments;
it might be good to reduce this, but the remaining nontrivial
duplication is small, and the logic flow is slightly different
because of the two-step process.
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| | |
This uses the 'iai' crate and valgrind to measure fine grained cache
behavior during program generation and hash computation.
Signed-off-by: Micah Elizabeth Scott <[email protected]>
|
| |\ \
| | |
| | |
| | |
| | | |
tor-hsservice errors: Introduce more error types
See merge request tpo/core/arti!1515
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
At the very least, I need FatalError to be distinct:
IptEstablisher::new ought not to fail unless everything is terrible.
Add a the Spawn variant to FatalError (that we'll need soon) and the
Bug variant (which it seems likely we might need).
This also gets rid of the crate-level Result alias.
|
| | | |
| | |
| | |
| | | |
This is what we do elsewhere.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If the service encouters operational errors, surfacing them here is
not helpful. So these methods ought to work, if they weren't called
erroneously.
|
| | | |
| | |
| | |
| | |
| | | |
The semantics of an Err return from this are unclear. Was it stopped?
And what kind of error might we even return?
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We want to change the error return types of many methods, so we need a
way to name `std::result::Result`.
We could use `StdResult`, but, actually, properly distinguishing the
kinds of errors that can occur in various contexts means we don't
actually want a single Error type for the whole crate, so
`crate::Result` is going to go away.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
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.
|
| | |_|/
|/| |
| | |
| | | |
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
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|