| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| | |
Some of the behaviors of the existing types here are nonstandard;
I've kept them and documented them, to avoid breaking compatibility.
|
| | |
| |
| |
| |
| |
| | |
This will hopefully fix our nightly 'cargo-check-targets' CI job.
Unclear why cargo also downgrades some versions of windows-sys.
|
| |/
|
|
|
|
| |
This is to fix a build issue on iOS.
Unclear why cargo also randomly changes the versions of windows-sys.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Mr 3616 rebased
Closes #1800
See merge request tpo/core/arti!3681
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This enables us to un-ignore RUSTSEC-2026-0009.
See #2341 for analysis of impact.
|
| |/
|
|
| |
keccak 1.5 was yanked and is causing our `cargo-audit` builds to fail.
|
| |\
| |
| |
| |
| | |
RPC: Replace backend with nonblocking IO
See merge request tpo/core/arti!3644
|
| | |
| |
| |
| |
| |
| |
| |
| | |
There are two levels here. At the lower level, the caller is
responsible for providing their own select/poll wrapper. At the
higher level, we use mio to provide our own.
Before the end of this branch, this new module will replace llconn.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 04ab3cd848d7977baf58dd64ebfcad6aa54ecb17.
Reverted because we no longer need to "peek" into the opaque
`CircChanMsg` of a circuit reactor: now the implementation-dependent
part of the reactor is in charge of handling the channel messages,
and extracting `Relay` objects out of RELAY/RELAY_EARLY cells,
which then get processed in the base reactor.
|
| |\ \
| | |
| | |
| | |
| | | |
deps: Upgrade fast-socks5 to 1.0.0.
See merge request tpo/core/arti!3638
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
One of the APIs we use, `Socks5Server`, is deprecated, and this commit
does not change to the new API. I don't plan to immediately rewrite this
to use the new API, as it seems nontrivial, but it still seems worth
updating.
|
| | |/
|/|
| |
| |
| | |
This commit upgrades the `bytes` crate to `1.11.1` in order to fix the
`RUSTSEC-2026-0007` vulnerability.
|
| |/
|
|
| |
This does not have any breaking changes that affect us.
|
| |
|
|
|
| |
The only breaking change here appears to be a MSRV bump that is lower
than our MSRV, so no changes are required on our end.
|
| |
|
|
| |
These updates won't be in 2.0.0, but will be in our next release.
|
| | |
|
| |
|
|
| |
Since we removes a existing feature, we need to bump the version.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Done via:
```
for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.39.0
done
```
|
| |
|
|
|
|
|
| |
Now that tor-cert-x509 is its own crate, we can use that,
and avoid the circular dependency.
Closes #2330.
|
| | |
|
| |
|
|
| |
This will help resolve some dependencies in our graph.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It would introduce a circular dev-dependency, which is not
well-supported by cargo publish. I hope to resolve this and
re-enable the test in #2330.
|
| | |
|
| |
|
|
| |
Closes #2316.
|
| |
|
|
|
|
|
|
|
| |
This will be used in a future commit, inside the new generic circuit
reactor.
We need it because RELAY cells are handled very similarly, so we need
some way of finding out if a given generic chancell is actually a RELAY
cell that we can handle in an implementation-agnostic way.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Implement authority certificate management
See merge request tpo/core/arti!3561
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
| |
This commit is a simple invocation of `cargo update`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add traits that will be returned outside tor-proto allowing us to not
expose client and relay specific channels.
The goal is for the tor-chanmgr to get those objects implementing those
traits and can build and run the reactor without knowing the specific
underlying type.
This allows us to have less code duplication and less client/relay
distinction in the chanmgr.
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
|
|
|
|
|
| |
This allows us to pass it to the ChanBuilder which will be able to use
this type for the outbound channels.
For now, we do this trick where if we have relay identities, we always
consider that all outbound channels will be RelayInitiator.
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
| |
The dependencies of futures-copy got bumped in arti!3570, leading to a
change in futures-copy, hence why we bump the patch version.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This only includes retry-error which had a few functional additions in
December, thereby rasing the minor version as new features were added to
the public API.
Done using the following:
* Find all non arti, non tor crates.
* `ls -1 crates/ | grep -v "^tor-\|^arti"`
* Exclude the ones without changes.
* `maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change"`
* Look into each with changes.
* In this case only retry-error.
* Bump the minor because it had non-trivial changes.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Done using the following:
```bash
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.38.0
done
```
|