mirrors/arti.git/crates/arti, branch arti-v1.9.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.9.02026-01-13T10:07:35Zcargo: Bump futures-copy2026-01-13T10:07:35ZClara Englercve@cve.cx2026-01-13T10:05:53Zurn:sha1:10eeb583eb1824003a76adf697005ed03e32d788
The dependencies of futures-copy got bumped in arti!3570, leading to a
change in futures-copy, hence why we bump the patch version.
Merge branch 'version-bump' into 'main'2026-01-13T09:07:31ZClara Englercve@cve.cx2026-01-13T09:07:31Zurn:sha1:e3bc58dcd2a2ef5e9b32e75c6dbd43e8dd319885
Bump dependencies for 1.9.0
See merge request tpo/core/arti!3570arti: fix path comment in example config2026-01-13T02:00:25ZSteven Engleropara@torproject.org2026-01-13T02:00:25Zurn:sha1:2c26ba553aebf7ea486640006c5b93cf23349148Make sure that rpc_state_sender lives as long as the proxies.2026-01-12T20:04:55ZNick Mathewsonnickm@torproject.org2026-01-12T19:28:46Zurn:sha1:572418264b53dd514a0a1aa9a686079b325290fc
Fixes bug introduced in 0cc367b9fef37c0f7d7f04d54c4687b27ef251d0.
Without this fix, RPC's get_proxy_info command wouldn't work.
cargo: Bump `arti` to `1.9.0`2026-01-12T12:35:01ZClara Englercve@cve.cx2026-01-12T12:35:01Zurn:sha1:314401ad9b4cebc332a1dc1536d313bff427d4eacargo: Update `arti-*` and `tor-*` to `0.38.0`2026-01-12T12:32:35ZClara Englercve@cve.cx2026-01-12T12:32:35Zurn:sha1:230b0201ea730a633e55c2781611a52c5ec73c28
Done using the following:
```bash
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.38.0
done
```
cargo: Run fixup-features for release2026-01-12T10:41:36ZClara Englercve@cve.cx2026-01-12T10:41:36Zurn:sha1:4c226f3486151300bfd53920c4b5ca34db1172a9
Executed command:
```
cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml
```
keymgr: Make CTorPath more like the client/service specifiers2026-01-06T15:25:20ZGabriela Moldovangabi@torproject.org2026-01-06T10:43:41Zurn:sha1:71178a54dc8c3c3ed75b14ecbca3197feb22accc
This will make it easier to see the correspondence between CTorPaths
and the HS client/service key specifiers.
Initially, I was hoping this would make it easier to write a d-d macro
that automatically derives a `CTorPath` variant (e.g.
`HsClientDescEncKeypair`) from the KeySpecifier type name
(`HsClientDescEncKeypairSpecifier`), but alas, I don't think d-d can
"chop off" name suffixes ("Specifier", in this case).
`from_ctor_path()`/`ctor_path()` implementations for converting
`CTorPath`s to and from key specifiers.
keymgr: Move Unrecognized errors out of KeyPathError2026-01-06T15:25:19ZGabriela Moldovangabi@torproject.org2026-01-05T11:07:23Zurn:sha1:0f2b9e7914580e2b0c58936c22f80996781df014
Out of all the variants in `KeyPathError`, `Unrecognized` is the odd one
out, because unlike the others, which are mainly just lower level
parsing errors, `Unrecognized` is a higher level error constructed in
`KeyMgr::describe()`.
`KeyMgr::describe()` now returns an `Option`, because
* the failure to describe a user provided `KeyPath` may or may not be
an error
* previously, `describe()` would only ever return `Ok` or
`Err(KeyPathError::Unrecognized)`, which essentially a binary
result. Also, `describe()` would never return any of the other
`KeyPathError` kinds, which further suggests `Unrecognized`
doesn't belong there
The `Unrecognized` variant still exists, but is now part of
`KeystoreCorruptionError`, (returned from
`KeyMgr::validate_entry_integrity()`).
keymgr: Update expected output in integration tests2026-01-06T15:25:19ZGabriela Moldovangabi@torproject.org2025-12-23T20:49:13Zurn:sha1:6b5ae77db280e2c74cb44571e789ccef5f0d2b76
C Tor keystore entries now use the same output format as the non-C Tor
entries.