mirrors/arti.git/crates/tor-keymgr/src/keystore.rs, branch arti-v1.3.0

tor-keymgr: Add a keystore for C Tor service keys.

2024-10-08T13:24:44Z

tor-keymgr: Move the checked_op utils out of the arti module.

2024-10-08T13:23:17Z

We are about to use this for the ctor keystore implementation too.

tor-keymgr: put ephemeral keystore behind experimental feature

2024-09-17T19:05:31Z

Feature is named "ephemeral-keystore".

Rename tor-keys crate to tor-key-forge

2024-09-04T18:26:37Z

Signed-off-by: David Goulet

tor-keymgr: Use tor-keys crate and remove dead code

2024-09-04T18:25:55Z

Everything copied in the previous commits to tor-keys is now removed and tor-keys crate is used accross the code. Minor changes to tor-keys to accomodate this change. Part of #1137 Signed-off-by: David Goulet

tor-keys: Automatically implement keymgr trait

2024-09-04T18:25:55Z

The derive ed25519 keypair macro now implements the keymgr trait so the key wrapper can now be used with a keystore without needing to specify it in the tor-keymgr crate. For this to work, a slight change to the KeygenRng trait was needed as in to expect the CryptoRngCore trait which is what ed25519-dalek requires. And also, the removal of the Sealed trait since now it is accepted to implement these traits outside tor-keymgr. Fixes #1137 Signed-off-by: David Goulet

Fix typos

2024-09-03T08:09:02Z

tor-keymgr: Fix nightly warnings.

2024-05-09T16:18:23Z

This is a follow-up from !2131

tor-keymgr: Add function for extracting the KeyType of an ssh key.

2024-05-08T17:32:11Z

tor-keymgr: Fix newly failing tests.

2024-05-08T09:54:39Z

This updates the keymgr tests to be slightly more robust. These tests attach some metadata to each key, such as the "nickname" of the key (which only exists for testing purposes), whether the key was auto-generated, and the keystore ID of the keystore from which the key was retrieved. Previously, the metadata was encoded in the key "material" itself (the test "keys" were actually just `String`s with a hacky `EncodableKey` implementation that abused the "encrypted" variant of `KeypairData`). This was only possible because we had access to the key internals (through `SshKeyData::Public`/`SshKeyData::Private`), but since the internals are inaccessible now, the tests need to be updated.