| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-netdir: Add separate functions for computing hsdirs for upload/download.
See merge request tpo/core/arti!1518
|
| | | | |
| | | |
| | | |
| | | | |
`HsBlindId` is `Copy`.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
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).
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
hsserrvice: resolve many TODOs in ipt_establish.rs
See merge request tpo/core/arti!1522
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Resolve (mostly) RUSTSEC-2023-0052
See merge request tpo/core/arti!1534
|
| | | |
| | |
| | |
| | |
| | | |
We've solved this for rustls-webpki, but tls-api (which arti-hyper
uses) still requires the unmaintained webpki crate. See #1016.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
upgrade serde to >=1.0.184 to not use prebuilt blob
Closes #1011
See merge request tpo/core/arti!1526
|
| | | |/
| |/|
| | |
| | | |
to remove the use of a pre-built blob
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
hashx/bench: Add cachegrind microbenchmarks
See merge request tpo/core/arti!1513
|
| |/ /
| |
| |
| |
| |
| |
| | |
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?
|