| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/ /
| |
| |
| | |
Closes #1969.
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
| |
* Change return type `Result<Vec<(KeyPath, KeystoreItemType)>>` if favor
of `Result<Vec<StdResult<(KeyPath, KeystoreItemType), UnrecognizedEntryError>>>`
|
| |\
| |
| |
| |
| |
| |
| | |
Fix clippy warnings from nightly rust
Closes #2009
See merge request tpo/core/arti!3008
|
| | |
| |
| |
| | |
clippy nightly complains when the map() output is unused.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.
I have mixed feelings about these warnings: On the plus side,
they really do help to detect functions that are twistier than they
need to be. On the minus side, they get confused by tracing macros,
and the "allows" do pile up. But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.
|
| | |
| |
| |
| |
| |
| | |
Clippy nightly detects this problem, though earlier clippy verisons
haven't. The common element here is applying unwrap() to the result
from a write!().
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
dirclient: Stop sending suffix .z in URLs.
See merge request tpo/core/arti!3013
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This suffix is redundant with "Accept-Encoding",
which all Tor directory caches have supported
since 0.3.1.1-alpha.
See torspec#342.
|
| | |
| |
| |
| |
| | |
There's already a check right above the TODO that does what the TODO
asks.
|
| | |
| |
| |
| | |
This addresses one of the TODOs from `reactor::conflux`.
|
| | | |
|
| | |
| |
| |
| |
| | |
This is not a MUST for client-side conflux, so I'm filing it as tech
debt.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
We don't have a way to compare virtual hops (see #2016), and we don't
yet support onion service conflux (see #2002), so let's defer this for
now.
|
| | |
| |
| |
| | |
This is tech debt, and is not a MUST for conflux.
|
| | |
| |
| |
| |
| | |
We can tackle this later, after we finish addressing all the remaining
`TODO(conflux)`.
|
| |\ \
| | |
| | |
| | |
| | | |
Service side Proof-of-Work
See merge request tpo/core/arti!2697
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This adds a error type for internal errors, and in error cases where we
previously panicked, returns a Result instead. The publisher then simply
doesn't publish the pow_params line and warns the user.
|
| | | |
| | |
| | |
| | |
| | | |
This shouldn't happen, but there's not a good reason to panic if it
does.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This is convenient for formatting filenames for the PoW nonce replay
log.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This will allow us to more easily switch out the implementation of this
queue as is needed for PoW.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds PowManager, as described in doc/dev/notes/service-side-pow.md,
hooks it into IptManager and Publisher, and adds code to publish and
rotate seeds, and to keep a updated list of Verifier instances for
currently active seeds.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-proto: use the visibility crate for benchmarks
See merge request tpo/core/arti!3010
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The [latest version] of `cargo-sort` is more opinionated than the
previous one, and is now causing the `rust-checks` job to fail on
`main`.
This commit applies the fixes needed to satisfy the new `cargo-sort`
rules. These changes were generated by running `cargo sort --workspace`
several times, until `cargo sort --check --workspace` finally succeeded
(it couldn't fix all the errors in one go, for some reason).
I have omitted the changes `cargo-sort` made to the top-level
`Cargo.toml`, to preserve the topological ordering of the workspace
members.
Closes #2014
[latest version]: https://github.com/DevinR528/cargo-sort/blob/f066ae80e5e6f5c1d8f0e2b8099461dcb97d9656/changelog.md#200
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Don't use MiddleOnly relays for rend points or intro points
Closes #1911
See merge request tpo/core/arti!3007
|
| | |
| |
| |
| | |
(text from Gabi)
|
| | | |
|
| | |
| |
| |
| | |
On !3007, @gabi-250 says that it was a mistake to have it be Naive.
|
| | |
| |
| | |
Co-authored-by: gabi-250 <[email protected]>
|
| | |
| |
| |
| | |
Closes #1911.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is the preferred type for choosing a relay,
since unlike a RelayExclusion, it lets us add multiple restrictions,
and a relay usage.
|
| | |
| |
| |
| |
| |
| | |
We'll need this in order to build paths that are specifically
for client rend circuits. I thought of using a boolean here,
but that had potential to get ugly in the future.
|
| | |
| |
| |
| |
| |
| | |
We're going to be looking at this a little more closely
in order to decide whether the last hop of a stem can be used
as a rendezvous point.
|