summaryrefslogtreecommitdiff
path: root/crates/tor-key-forge/semver.md
Commit message (Collapse)AuthorAgeFilesLines
* Use an EntropicRng trait to enforce key generation rules.Nick Mathewson2025-03-241-0/+1
| | | | | | | | | | | 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.
* Remove semver.md files post releaseIan Jackson2025-02-071-5/+0
|
* tor-key-forge: Add missing semver.md entries.Gabriela Moldovan2025-01-131-0/+3
|
* tor-key-forge: Split out ItemType as a separate trait.Gabriela Moldovan2025-01-131-0/+2
| | | | | | | | 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<dyn ItemType>` instead.
* Remove semver.md files after 1.3.2 releaseNick Mathewson2025-01-071-1/+0
|
* tor-key-forge: Abolish the HasKind impl of Error.Gabriela Moldovan2024-12-101-0/+1
We can't possibly know the `ErrorKind` of such an error, unless we know where the unsupported key came from. Since we can't know this, we should let a higher level crate (like `tor-keymgr`) decide the `ErrorKind` instead.