mirrors/arti.git/crates/tor-llcrypto/src/pk/rsa.rs, branch mainmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=main2026-05-12T20:55:43ZUpgrade rand crates to 0.10.2026-05-12T20:55:43ZWesley Aptekar-Casselsme@wesleyac.com2026-05-07T20:06:21Zurn:sha1:a18167928901d8c88cd1cdd87346de8ad1ee42a2
When the circ-padding feature is enabled, we use maybenot, which does
not yet support rand 0.10. In the meantime, enabling this feature pulls
in rand 0.9. This is not ideal, but should be okay as a temporary
situation.
This also replaces the use of ReseedingRng (which was removed in 0.10)
with the reseeding_rng crate. This is somewhat less performant, but it
should be okay.
tor-llcrypto: Add RsaIdentity::to_bytes()2026-04-23T14:53:37ZClara Englercve@cve.cx2026-04-23T14:51:17Zurn:sha1:5f0cc69966dcd6f30719a516739d2670e86e645f
This commit adds .to_bytes() to RsaIdentity which is similar to
.as_bytes() except that it returns the RsaIdentity as a byte array.
We are going to need this at a few places in tor-dirserver. The naming
was inspired from x25519-dalek which has similar .as_bytes() and
.to_bytes() methods. Besides, copying 20 bytes shall be okay and it
avoids having to write ugly try_into() constructs.
llcrypto: Depend on tor-memquota-cost, not tor-memquota.2026-02-02T15:02:22ZNick Mathewsonnickm@torproject.org2026-01-29T16:43:49Zurn:sha1:eb62db42196714c9526624e2700794f1639b1036tor-llcrypto: Add `RsaIdentity::as_hex_upper`2026-01-15T10:48:22ZClara Englercve@cve.cx2025-12-15T13:39:20Zurn:sha1:0c641bfa2f05c264a78b9465279d948843c4dccd
This commit adds the method `as_hex_upper(&self) -> String` to
`RsaIdentity`, which returns the `RsaIdentity` as a hexadecimal string
in uppercase.
Although this type already implements `ToString`, this result is
unsuitable for working with consensuses because they neither contain a
`$` prefix, nor are encoded in lowercase.
Lay foundations for RSA keys in keystore.2025-09-30T20:00:51ZWesley Aptekar-Casselsme@wesleyac.com2025-09-30T18:44:05Zurn:sha1:073a6a96873d953cd4e8cc5018b593e3aa04d83a
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: Add more comments about implementation of RSA sign function.2025-09-10T16:36:46ZWesley Aptekar-Casselsme@wesleyac.com2025-09-10T16:36:46Zurn:sha1:c2606632992588ce03cb98bc538b98e9b6aacdaator-llcrypto: Add note about key size to RSA KeyPair::generate.2025-09-10T15:52:44ZWesley Aptekar-Casselsme@wesleyac.com2025-09-10T15:52:44Zurn:sha1:00f643ebecbc9d1fd3266caaf1ff8f4ffa17065ator-llcrypto: Rename rsa::PrivateKey to rsa::KeyPair.2025-09-08T21:12:10ZWesley Aptekar-Casselsme@wesleyac.com2025-09-08T21:10:33Zurn:sha1:e3081529a0aa68bf74554b3a176717b4ba4c8c41
As discussed with gabi on IRC today.
tor-key-forge: Add RSA key types.2025-09-08T21:07:35ZWesley Aptekar-Casselsme@wesleyac.com2025-09-08T20:08:52Zurn:sha1:058455138a88141670b66a253fb5b0c124c30f40
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.
Rename "memquota" feature to "memquota-memcost" when it's just HasMemoryCost (fmt)2024-10-16T13:48:29ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-16T13:48:29Zurn:sha1:a8b2d247f35c0c5b014b6011caee2832c5f39d31