mirrors/arti.git/crates/tor-cert/src/rsa.rs, branch arti-v2.4.0

tor-cert: Stabilise everything gated by feature = "encode"

2026-04-29T16:49:21Z

This is widely used in-tree already. I don't think it makes sense to feature-gate it. There are some (perhaps rather thin) tests for both the Ed25519Builder and EncodedRsaCrosscert. It is possible we might want to change the API further, but this is still a 0.x crate so that's not going to be a problem. We'll remove the actual cargo feature in the next commit.

cert: Deduplicate expiry-in-hours logic

2026-03-17T13:54:16Z

These certificates use a weird expiration format: counting hours since the unix epoch. Previously we had it implemented in two different places. This patch centralizes it, since we are about to become slightly more complicated.

tor-cert: Ability to create Rsa->Ed25519 crosscerts.

2026-02-19T17:15:03Z

cert: Add cert_type() to RsaCrossert

2026-01-22T16:16:44Z

It is always the same type for this specific certificate. Signed-off-by: David Goulet

proto: Remove relay ChannelAuthenticationData builder

2025-10-23T17:47:06Z

Signed-off-by: David Goulet

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.

Change tor_bytes::Error::BadMessage to a Cow.

2023-02-09T15:20:31Z

Actually, to avoid making a breaking change, I'm deprecating BadMessage and creating a new InvalidMessage variant that takes a Cow. This way I don't need to track every crate that re-exposes tor_bytes::Error and call this a breaking change in those. Making this change will allow tor_bytes errors to be much more helpful.

use Ed25519 identity instead of PublicKey in tor-cert::rsa

2022-07-25T18:46:01Z

change usage of PublicKey to Ed25519 in tor-cert

2022-07-23T18:07:25Z

and propagate to other affected crates

Resolve roughly half of the XXXXs.

2021-12-06T20:11:03Z

We want to only use TODO in the codebase for non-blockers, and open tickets for anything that is a bigger blocker than a TODO. These XXXXs seem like definite non-blockers to me. Part of arti#231.