mirrors/arti.git/crates/tor-cert, branch arti-v1.4.2

Bump all the unstable tor- and arti- crates to 0.29.0.

2025-03-31T17:59:51Z

Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.29.0 done ```

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`

Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

(Per discussion at #1774, we think the changes are acceptable.) This commit won't compile on its own; subsequent commits will fix it.

Wrap ed25519-dalek types.

2025-03-18T12:45:28Z

With this change, we'll no longer need to expose the types from dalek-cryptography as part of our API, and we'll have more freedom to switch ed25519 implementations, or to upgrade to a newer `rand` ahead of their schedule. Unlike with x25519-dalek, I had to tweak the API a bit: There's no way to get a &PublicKey out of a Keypair now, and implementing the old ed25519-dalek traits seemed unnecessary.

Bump minor versions in tor-, arti-.

2025-03-03T13:18:27Z

Upgrade to derive_more 2

2025-02-26T18:06:37Z

This took a little refactoring, since derive_more::Foo no longer re-exports std::ops::Foo.

cert: reserve 0x0C for FAMILY_V_IDENTITY (happy families) certs.

2025-02-11T19:01:34Z

Version bumps to 0.27.0

2025-02-06T18:17:34Z

See Release.md. maint/list_crates | grep -P '^tor-|^arti-' | xargs -n1 nailing-cargo -Eu set-version --bump minor -p This completes the version bumps. The report of changed crates, before I started the release work, is: $ maint/changed_crates -v "arti-v$LAST_VERSION" oneshot-fused-workaround: No change. slotmap-careful: No change. test-temp-dir: No change. fslock-guard: No change. hashx: No change. equix: No change. tor-basic-utils: No change. caret: No change. fs-mistrust safelog: No change. retry-error: No change. tor-error tor-general-addr: No change. tor-geoip: No change. tor-rtcompat tor-rtmock tor-async-utils tor-config tor-config-path tor-rpc-connect tor-log-ratelim: No change. tor-rpcbase tor-memquota: No change. tor-units tor-llcrypto: No change. tor-protover: No change. tor-bytes tor-checkable: No change. tor-cert tor-key-forge tor-hscrypto: No change. tor-socksproto: No change. tor-linkspec: No change. tor-cell: No change. tor-proto tor-netdoc: No change. tor-consdiff: No change. tor-netdir tor-relay-selection: No change. tor-persist tor-chanmgr tor-ptmgr: No change. tor-guardmgr: No change. tor-circmgr tor-dirclient: No change. tor-dirmgr: No change. tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy: No change. tor-relay-crypto arti-client arti-relay arti-rpcserver arti arti-rpc-client-core $

tor-cert: Add experimental API for building EncodedEd25519Certs.

2025-01-13T19:28:01Z

This will enable us to deserialize byte slices as `EncodedEd25519Certs`. Needed because this type will be used to representing a parsed + validated cert retrieved from the keystore. Technically, we *could* do without this function by defining a separate newtype wrapper over `Vec` to represent the validated cert data, but IMO adding a second encoded ed25519 cert type in another crate might be confusing later down the line (because the two types will be nearly identical, and are bound to eventually diverge in terms of API and implementation). Part of #1137

tor-cert: Remove no-longer-needed experimental API.

2025-01-13T19:25:57Z

Part of #1768