mirrors/arti.git/crates/tor-key-forge/src/macros.rs, branch arti-v1.8.0

Lay foundations for RSA keys in keystore.

2025-09-30T20:00:51Z

This currently can't be used due to upstream limitations in the ssh_key crate, which will be removed likely in the next release. In the meantime, we can put in all the groundwork.

tor-llcrypto: Rename rsa::PrivateKey to rsa::KeyPair.

2025-09-08T21:12:10Z

As discussed with gabi on IRC today.

tor-key-forge: Add RSA key types.

2025-09-08T21:07:35Z

Some things I'm still considering here: * We may want to define a tor_llcrypto::pk::rsa::Signature newtype. * We likely want to rename tor_llcrypto::pk::rsa::PrivateKey to RsaKeypair.

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again.

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()`

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.

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-keymgr: Replace as_ssh_key_data with as_keystore_item.

2024-12-04T16:42:06Z

tor-key-forge: Replace EncodableItem::key_type() with item_type().

2024-12-04T16:42:06Z

This function now returns a `KeystoreItemType`, enabling us to represent certs as `EncodableItem`s.