mirrors/arti.git/Cargo.lock, branch arti-v1.4.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.22025-03-31T18:00:09ZBump arti crate to 1.4.22025-03-31T18:00:09ZGabriela Moldovangabi@torproject.org2025-03-31T17:35:06Zurn:sha1:494a6911049235e6ed4cf9e595126f7504d06402
Done using:
```
cargo set-version --bump patch -p arti
```
Bump all the unstable tor- and arti- crates to 0.29.0.2025-03-31T17:59:51ZGabriela Moldovangabi@torproject.org2025-03-31T17:34:50Zurn:sha1:1be579f99a7c0784bd7710f9ee6ee9a6b10c85df
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.29.0
done
```
Bump the versions of the non-{arti-,tor-} crates.2025-03-31T17:59:48ZGabriela Moldovangabi@torproject.org2025-03-31T17:33:52Zurn:sha1:a0919b507bb2a5855e36b85a2e10e3eac5fa4e15
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
```
We split them in the following categories:
* crates with no changes (no version bumps):
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
oneshot-fused-workaround: No change.
slotmap-careful: No change.
fslock-guard: No change.
caret: No change.
retry-error: No change.
```
* crates that only have non-functional changes (bump the patch version):
- test-temp-dir
- equix
- fs-mistrust
- safelog
* crates where APIs were broken (bump minor):
- hashx (`RngCore` impl for `SipRand`)
The bumps from this commit were created using this script:
```
PATCH="
test-temp-dir
equix
fs-mistrust
safelog
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
MINOR="
hashx
"
for crate in $MINOR; do
cargo set-version --bump minor -p $crate;
done
```
Run cargo update in preparation for release.2025-03-27T14:32:48ZGabriela Moldovangabi@torproject.org2025-03-27T12:19:28Zurn:sha1:afcdff9f313ff434420b7e1c4567558056540be9Upgrade getrandom dependency to 0.3.22025-03-27T14:32:48ZGabriela Moldovangabi@torproject.org2025-03-27T12:15:38Zurn:sha1:fef7fb1e1bc4b7b4c91a3d64b69a9b9690839e41
The `js` feature was replaced by a configuration flag in [0.3.0], so
I've checked in a `.cargo/config.toml` for `tor-llcrypto` and
`tor-bytes` with `RUSTFLAGS` for selecting the `getrandom` backend to
use on wasm32.
[0.3.0]: https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md#030---2025-01-25
Upgrade rustls-wekpki dependency to 0.103.1.2025-03-27T14:32:25ZGabriela Moldovangabi@torproject.org2025-03-27T11:56:32Zurn:sha1:0cee4a47625c5840003bbd81164adf4f004cb7c8
We aren't affected by any of the breaking changes from [0.103.0].
[0.103.0]: https://github.com/rustls/webpki/releases/tag/v%2F0.103.0
Upgrade strum dependency to 0.27.1.2025-03-27T14:18:29ZGabriela Moldovangabi@torproject.org2025-03-27T11:53:08Zurn:sha1:2253d7695e58565d8ddc6d0b014489726554fb1f
In 0.27.0, strum's MSRV was bumped to 1.66.1, but that's okay because
ours is 1.77.
We aren't affected by any of its [breaking changes].
[breaking changes]: https://github.com/Peternator7/strum/blob/master/CHANGELOG.md#0270
Use CautiousRng for keys going into the KeyMgr.2025-03-24T19:10:21ZNick Mathewsonnickm@torproject.org2025-03-20T14:51:44Zurn:sha1:71ec7a3c6e563c4107ff62ea003794c6a31e45a6llcrypto: new CautiousRng for constructing long-lived keys2025-03-24T19:10:21ZNick Mathewsonnickm@torproject.org2025-03-20T14:26:56Zurn:sha1:ee7c15868e916bc7dbbd26e707077c452dd5d452
This Rng combines inputs from several sources,
including OsRng, to minimize the likelihood
of falling to a vulnerability in any particular one.
Merge branch 'named_protovers' into 'main'2025-03-20T17:10:03ZDavid Gouletdgoulet@torproject.org2025-03-20T17:10:03Zurn:sha1:4727e71c790f96bb84723bbf5afc4bc3aa35136e
protover: Add support for subprotocol version mnemonics.
Closes #1891
See merge request tpo/core/arti!2854