aboutsummaryrefslogtreecommitdiff
path: root/crates/tor-relay-crypto/src/certs.rs
Commit message (Collapse)AuthorAgeFilesLines
* tor-checkable: Rename `TimeBound::check_valid_*` to `if_valid_*`Ian Jackson2026-07-231-1/+1
| | | | | | | I find these names confusing. To my mind "check" implies a function returning `Result<(), _>`. Some other APIs use `unwrap` here but I think `if` is good.
* Use new TimeBound name throughout the treeIan Jackson2026-07-161-1/+1
|
* tor-cert: Ed25519CertBuilder: do builder fn renameIan Jackson2026-04-291-3/+3
| | | | | | Change all call sites. This completes the rename.
* tor-relay-crypto: port to web-time-compatNick Mathewson2026-03-261-4/+3
|
* relay-crypto: Fix the gen relay signing keypair typoDavid Goulet2026-02-231-3/+3
| | | | Signed-off-by: David Goulet <[email protected]>
* relay-crypto: Add gen_tls_cert() helper functionDavid Goulet2026-02-231-0/+15
| | | | Signed-off-by: David Goulet <[email protected]>
* tor-relay-crypto: Remove TODO about validating cert extensions.Gabriela Moldovan2025-01-131-2/+0
| | | | | | | There is no need for validation here. If any validation is required, it will be handled by the calling code. Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2672?commit_id=10845d5e6a06d4d9548d536846eb470128d8a7d4#note_3147517
* tor-relay-crypto: Use the new cert_type() function to get the cert type.Gabriela Moldovan2025-01-131-2/+8
|
* tor-relay-crypto: Use the high-level cert types instead of EncodedEd25519Cert.Gabriela Moldovan2025-01-131-2/+4
| | | | | | | This will come in handy later on, when we start using these function in conjunction with `KeyMgr::get_or_generate_key_and_cert`, which expects the `make_certificate` callback to return a type that implements `ToEncodableCert`.
* tor-relay-crypto: Implement ToEncodableCert for the relay cert types.Gabriela Moldovan2025-01-131-0/+90
| | | | Closes #1777
* tor-relay-crypto: Add high-level cert types.Gabriela Moldovan2025-01-131-0/+40
| | | | | | These will be the `ToEncodableCert`s we write to the keystore. Part of #1777
* relay-crypto: Initial import of new tor-relay-crypto crateDavid Goulet2024-09-181-0/+37
This adds a new crate called tor-relay-crypto which is responsible for declaring the relay keys and certificate that will be used by a relay and stored in a KeyMgr. This is in its own crate and considered pretty low level so other crates can use it to access the relay keys, like tor-proto, for cryptographic actions like channel authentication or descriptor signing. The lower level cryptographic keys are wrapped in a higher level object in this crate, using tor-key-forge crate, so we can have proper semantic and strong type check on those keys so they are not misused or confused with other keys. At this point, the key declaration might change once the KeyMgr supports attaching a certificate to a key. We are likely going to see more code related to certificate creation in this crate in the future. Part of #1604 Signed-off-by: David Goulet <[email protected]>
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 20:12:36 +0000