mirrors/arti.git/crates/tor-keymgr/semver.md, branch arti-v1.1.7

keymgr: Add KeyMgr::generate() for generating new keys.

2023-07-24T12:17:31Z

keymgr: Add function for generating EncodableKeys.

2023-07-24T12:17:23Z

keymgr: Add a Keystore::contains accessor.

2023-07-24T12:17:05Z

Revert "keymgr: Require callers to be explicit about which keystore to get keys from."

2023-07-21T11:21:36Z

This reverts commit 38a6c74c7894dc96b16c9039cacc2a4023977b05. This also updates some tests to make them compile with the reverted version of the code.

keymgr: Require callers to be explicit about where to remove keys from.

2023-07-20T18:25:12Z

As with `KeyMgr::insert`, only `KeystoreSelector::Id` and `KeystoreSelector::Default` are supported.

keymgr: Add EncodableKey::to_bytes for encoding keys.

2023-07-20T18:25:04Z

We'll need this to implement `Keystore::insert`.

keymgr: Add some extra derives to ArtiPath and KeyType.

2023-07-20T18:25:01Z

keymgr: Require callers to be explicit about which keystore to get keys from.

2023-07-20T18:24:57Z

keymgr: Remove unimplemented/unnecessary has_key_bundle function.

2023-07-20T18:24:44Z

The concept of a "key bundle" would introduce a lot of complexity while providing little to no gain. Some context: ``` Originally, "key bundles" were meant to be the answer to the question "which keystore should insert place keys in?": https://gitlab.torproject.org/tpo/core/arti/-/blob/36606a66ddca9abd1595d13c9397bc812bf24cb5/crates/tor-keymgr/src/mgr.rs#L60-69 However, I'm not so sure anymore that "key bundles" are the answer. I don't think there is any way we can "guess" where a key should go. When inserting/generating a new key, we should either: always write to the same, primary key store, OR require the user to be explicit about which key store the new key should go in (by assigning an ID to each key store and expecting the user to provide it when inserting/generating new keys) I prefer the latter option, because it provides more flexibility, which we're going to need when implementing the key management CLI (which I think should allow users to generate keys anywhere they want, e.g. arti keymgr generate --keystore hsm ...) ``` For more details, see the discussion on #903. Closes #903

keymgr: Require callers to specify which keystore to insert keys in.

2023-07-20T18:24:29Z

The caller uses `KeystoreSelector` to specify which keystore to insert the new key into (only `KeystoreSelector::Id` and `KeystoreSelector::Default` are supported for `insert`). The ability to insert keys in a particular keystore will come in handy when we implement the key management CLI (the CLI will have an option for specifying the keystore to access/modify).