mirrors/arti.git/crates/tor-rtcompat, branch arti-v2.5.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.02026-06-30T13:42:13ZVersion bumps for 2.5.02026-06-30T13:42:13ZNick Mathewsonnickm@torproject.org2026-06-30T13:42:13Zurn:sha1:245b03f5a48b4e58f8c84f072920160fc87be500
Closes #2617.
We've lucked out this time, and it turns out that every one of our
published crates gets a minor bump. So this was generated with:
```
for cr in $(./maint/list-crates); do
cargo set-version -p $cr --bump minor
done
```
Bump MSRV to 1.912026-06-15T13:18:11ZClara Englercve@cve.cx2026-06-15T12:59:25Zurn:sha1:e93e0e2f9f42f526a8e1aa64e6ea659ef31dd800
This commit bumps the MSRV to 1.91 which was released on 2025-10-30.
The Cargo.toml files were updated as follows:
```sh
git ls-files | \
grep ".*Cargo\.toml$" | \
xargs sed -i '' 's/^rust-version = "1\.89"$/rust-version = "1\.91"/g'
```
The following files were updated manually:
```
modified: .gitlab-ci.yml
modified: README.md
modified: flake.nix
modified: maint/docker-android/Dockerfile
```
maint: Run maint/add_warning to deny string slices2026-06-09T15:36:01ZClara Englercve@cve.cx2026-06-09T15:36:01Zurn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.
I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.
This commit makes cargo clippy fail. We will add exceptions in the next
commit.
tor-rtcompat: change `Default` impls for connect/listen options2026-06-08T16:56:56ZSteven Engleropara@torproject.org2026-06-08T03:44:55Zurn:sha1:b39bf9524e7a9587256919a6f97b1a357a8a36af
The new `Default`s have no panicking code paths.
tor-rtcompat: replace `_options` with `()`2026-06-08T16:56:56ZSteven Engleropara@torproject.org2026-06-02T03:11:16Zurn:sha1:44d92adfda6605c88a4b9af3cb10581f00a2c9f4
This hopefully better shows that there's nothing to use here for general
socket types.
tor-rtcompat: updated semver.md for `connect()` changes2026-06-08T16:56:52ZSteven Engleropara@torproject.org2026-06-02T02:43:24Zurn:sha1:ad95144996608ca2e099982dab726b37b7ff5d0ator-rtcompat: add connect() options to set the socket buf sizes2026-06-08T16:55:27ZSteven Engleropara@torproject.org2026-05-27T05:16:16Zurn:sha1:600710ad30ef1df88b99721129e1176e6290d326tor-rtcompat: manually create and connect() socket2026-06-08T16:55:27ZSteven Engleropara@torproject.org2026-05-27T05:09:59Zurn:sha1:d47fecdb1f2f660e9a2bda1d13319e93b6981a5e
This will allow us in the future to set custom sockopts on the socket
before calling connect().
I tested an arti proxy with tokio and async-std manually. Arti doesn't
yet support smol so I was not able to test it, but it's using the same
code as async-std so I would expect it to work.
tor-rtcompat+misc: add `NetStreamProvider::ConnectOptions`2026-06-08T16:55:27ZSteven Engleropara@torproject.org2026-05-26T20:57:08Zurn:sha1:926c7a5449e29e2d652431a2406e7acae59bed50
This adds the trait type `ConnectOptions` to `NetStreamProvider` and adds
this `ConnectOptions` as an argument to `NetStreamProvider::connect()`.
You probably want to look at the changes in tor-rtcompat first, then the
rest of this commit is updating the various places we use
`NetStreamProvider`.
tor-rtcompat: add structs to hold connect() options2026-06-08T16:55:27ZSteven Engleropara@torproject.org2026-05-26T20:54:02Zurn:sha1:9f5f7107841c520d6c2a6d2e8f50b95a93136a0a
For now this just sets up the structure. We'll add options for TCP
later.