mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0 2025-08-07T15:28:36Z 2025-08-07T15:28:36Z Nick Mathewson nickm@torproject.org 2025-08-06T01:19:58Z urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc 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. 2023-11-29T15:34:58Z Nick Mathewson nickm@torproject.org 2023-11-21T15:58:29Z urn: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. 2023-08-10T14:27:50Z Emil Engler me@emilengler.com 2023-08-10T14:07:53Z urn:sha1:2f9011962256e058674a5d2819cba358a3894034 This commit implements a test for an expired Ed25519 certificate within the `tor_cert` crate. 2023-05-16T21:53:15Z Nick Mathewson nickm@torproject.org 2023-05-15T20:59:02Z urn:sha1:56c6e4345b2e9e46684783de25bd56b9ad7c6a8f 2023-02-09T15:20:31Z Nick Mathewson nickm@torproject.org 2023-02-08T13:51:27Z urn:sha1:48ab7b0463aaada172a426ad4b20a63d7f44cb84 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. 2022-12-12T17:41:22Z coral coral@anderstorpsfestivalen.se 2022-12-12T17:41:22Z urn:sha1:25f113b8b388cc7b70723ec99b295b989ca372e0 2022-07-23T18:07:25Z trinity-1686a trinity@deuxfleurs.fr 2022-07-23T18:07:25Z urn:sha1:8c28622ecbde60c710e24a722e0253b799b607a1 and propagate to other affected crates 2022-07-23T16:38:31Z trinity-1686a trinity@deuxfleurs.fr 2022-07-23T16:38:31Z urn:sha1:8def41614435e1ccbfdf3b96a291eaf457994ddd 2022-06-23T19:42:45Z Nick Mathewson nickm@torproject.org 2022-06-23T19:42:45Z urn:sha1:38004a4f4dd3aa99b81b6585039e81dc77c17f32 Some of these were for decoding particular objects (we now say what kind of objects), and some were unrelated tor_cert errors that for some reason we had shoved into a tor_bytes::Error. There is now a separate tor_cert::CertError type, independent from tor_cert's use of `tor_bytes::Error` for parsing errors. 2021-08-27T13:53:09Z Nick Mathewson nickm@torproject.org 2021-08-27T13:53:09Z urn:sha1:557a0ff40b3731d4690767de27010bbeff08777d This will cause some pain for now, but now is really the best time to do this kind of thing.