mirrors/arti.git/crates/tor-keymgr/src/mgr.rs, branch arti-v1.4.3

tor-keymgr: BREAKING: Refactor API: Keystore::insert

2025-04-02T15:40:15Z

Drop redundant/unused param item_type: &KeystoreItemType from keystore::Keystore::insert. Method now uses param key: &dyn EncodableItem to obtain a KeystoreItemType

tor-keymgr: Fix TODO: Refactor API: Keystore::insert

2025-04-01T23:15:39Z

Makes param item_type redundant. Renames item_type -> _item_type.

tor-keymgr: Introduce ItemMetadata type for testing.

2025-03-26T11:32:13Z

Use an EntropicRng trait to enforce key generation rules.

2025-03-24T19:11:48Z

We want to require that whenever we generate a key that's persistent (stored in KeyMgr), it's going to be made from a stronger-than-usual Rng. This trait helps us enforce that. We also add a FakeEntropicRng struct to use for testing. Note that this turned up a case that we'd missed, which required an internal change in tor-hsservice.

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

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

tor-keymgr: Use ParsedEd25519Cert when decoding certs.

2025-01-13T19:29:19Z

This helps us get rid of our uses of `KeyUnknownCert`. Needed because `KeyUnknownCert` can't readily be converted back to `EncodedEd25519Cert` (while `ParsedEd25519Cert` *can* -- see the `certs` module from `tor-relay-crypto`).

tor-keymgr: Fix cert handling tests.

2025-01-13T19:26:51Z

This updates and reenables the cert management tests. Part of #1768

tor-keymgr: Use Ed25519Cert::decode to parse the certs.

2025-01-13T19:25:57Z

tor-key-forge: Split out ItemType as a separate trait.

2025-01-13T19:22:36Z

This is necessary because `ParsedCert`s will not be `EncodableItem`s. This is because we cannot (and don't want to) write certificates that have not yet been validated to the keystore. They do need to be retrievable from the keystore though, so we also change `ErasedKey` to be `Box` instead.

tor-key-forge: Distinguish between parsed certs and encodable certs.

2025-01-13T19:21:45Z

We need two different types to represent * certs that have been parsed, but not yet validated (`KeyUnknownCert`) * newly generated encodable certs (`EncodedEd25519Cert`) Currently, we don't use `KeyUnknownCert` anywhere, and instead use `EncodedEd25519Cert` to represent "parsed" but not-yet-validated certs. This approach is wrong and relies on a broken (no-op) `EncodedEd25519Cert::from_bytes` implementation. A future commit will address this problem by replacing `EncodedEd25519Cert::from_bytes` with `Ed25519Cert::decode` to actually parse the cert upon retrieving it from the keystore.