mirrors/arti.git/crates/tor-llcrypto/src/util, branch arti-v1.4.4mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.42025-03-24T19:10:21ZUse CautiousRng for keys going into the KeyMgr.2025-03-24T19:10:21ZNick Mathewsonnickm@torproject.org2025-03-20T14:51:44Zurn:sha1:71ec7a3c6e563c4107ff62ea003794c6a31e45a6squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T14:47:35Zurn:sha1:895bc807f106e359d35522a3ad5f288ba6cf6a9c
- The Rng::gen() functions have been renamed to Rng::random().
llcrypto: add an rng compatibility shim for dalek-crypto2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T13:24:41Zurn:sha1:9e4de6cbfe5cef6076b89f7a94a5232d47b980dd
dalek-cryptography is still on rand 0.8, so we need a compatibility
shim for the Rng.
Fortunately, since we merged interface-abstraction-of-the-daleks
(!2868), we no longer need to propagate this compatibility layer
throughout our codebase.
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:a8b2d247f35c0c5b014b6011caee2832c5f39d31Rename "memquota" feature to "memquota-memcost" when it's just HasMemoryCost2024-10-16T13:48:11ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-16T13:43:47Zurn:sha1:6ee75b3866e374250a760822b4aab49aef70e930
It's not documented anywhere ATM. I will do that in a followup MR.
Some HasMemoryCost impls in tor-llcrypto2024-10-02T18:11:26ZIan Jacksonijackson@chiark.greenend.org.uk2024-09-26T20:19:34Zurn:sha1:b99b6104923dc97d514fab0a7b60e9e98a3ba647Run maint/add_warning.2024-03-13T16:30:53ZNick Mathewsonnickm@torproject.org2024-03-13T16:30:53Zurn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320cllcrypto: Use up-to-date name for a clippy lint.2023-11-30T15:16:10ZNick Mathewsonnickm@torproject.org2023-11-30T14:00:56Zurn:sha1:cbaaddbb2981cd6854fc2595892c96fde4698c43Remove RngCompatExt.2023-11-29T15:55:04ZNick Mathewsonnickm@torproject.org2023-11-29T15:49:26Zurn:sha1:7fb24cb69da537ac04ab2dae80997c6d481622ef
This code was needed with the old version of dalek-cryptography,
which wasn't compatible with up-to-date versions of the `rand`
crate(s). But now that we've upgraded, we can drop this.
(We could have left it around and deprecated it, but we are already
making a breaking change to tor-llcrypto by upgrading
dalek-cryptography.)
Convert to the latest versions of dalek-cryptography2023-11-29T15:34:58ZNick Mathewsonnickm@torproject.org2023-11-21T15:58:29Zurn:sha1:98037a2c788bd901679139178d25f855324637f3
The main changes that we have to adjust for are as follows:
* In x25519-dalek:
* `StaticSecret` is now behind a feature.
* `StaticSecret::new` is deprecated in favor of
`StaticSecret::random_from_rng`.
* StaticSecret no longer does its own clamping.
* In ed25519-dalek:
* `SecretKey` has (in effect) been renamed to `SigningKey`. The name
`SecretKey` is now an alias for `[u8; 32]`.
* `SigningKey` is effectively a keypair, since it contains a
public key as well.
* `PublicKey` has been renamed to `VerifyingKey`.
* The functions to extract a signing key and verifying key have
been renamed as you might expect.
* `ExpandedSecretKey` has been moved to `hasmat` and no longer
implements `sign`.
* `ExpanededSecretKey` now has as its elements a scalar and a hash
prefix.
* Various functions that took `&[u8]` now take `&[u8; N]`.
* We no longer need a wrapper for older versions of rand.
There is a single test in tor-keymgr that does not pass. I've
marked it as ignore for now, in hopes that @gabi-250 can help me
figure it out.
This closes #808. There are several changes I want to make before
we merge, however. They are marked with TODO DALEK.