mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4 2023-03-31T12:28:06Z 2023-03-31T12:28:06Z Nick Mathewson nickm@torproject.org 2023-03-31T12:28:06Z urn:sha1:e208fb15adb800ae41e472db464f984e9f4a4f5c These crates have had breaking changes. They are pre-1.0, so they get a minor bump. ``` tor-basic-utils tor-config ``` 2023-03-31T12:24:39Z Nick Mathewson nickm@torproject.org 2023-03-31T12:24:39Z urn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76 For these crates, the changes are nontrivial, so we _do_ bump the versions on which their dependent crates depend. Fortunately, since they are all pre-1.0, we don't need to distinguish semver-additions from other changes. (Except for arti, which _is_ post-1.0, but gets a patchlevel bump anyway.) These are unstable crates with breaking changes: ``` tor-hscrypto tor-hsclient ``` These have new or extended APIs: ``` safelog tor-bytes tor-cell tor-linkspec tor-llcrypto tor-proto tor-cert arti-client ``` These have new unstable APIs or features: ``` tor-netdoc tor-circmgr (also broke some unstable APIs) arti (is post-1.0) ``` These have bugfixes only: ``` caret tor-dirmgr ``` 2023-03-13T12:47:14Z Nick Mathewson nickm@torproject.org 2023-03-13T12:47:14Z urn:sha1:d6bb8fee0b3f010902d8297f16589467d82e4e4f This version of bitflags now requires us to explicitly list the traits that we want to derive for our bit-flags structs. 2023-03-01T12:38:56Z Nick Mathewson nickm@torproject.org 2023-02-27T20:38:47Z urn:sha1:8c9a1a6fad6fa34dd4ff42795d5c698f0928b331 The old code parsed and encoded a signature and a mac... but there was no way to actually set them properly. Now EstablishIntro is built around an EstablishIntroBody, and has the ability to check signatures and macs. Because there is no way to handle one of these messages if we can't check the signature, we no longer accept unrecognized `auth_key` types in this message. I've added a test to make sure that we can validate a message from the C tor implementation, and a test to make sure we can validate our own cells. I also had to modify the previous tests so that their keys were well-formed. 2023-02-28T12:13:27Z Nick Mathewson nickm@torproject.org 2023-02-28T12:13:27Z urn:sha1:f41449d0bd9a2db5f72dd9941fb897e5cd9b922d These crates have had small code changes, but no API additions: tor-config tor-socksproto tor-cert tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr arti tor-hsservice tor-congestion These crates have had API extensions: fs-mistrust tor-llcrypto tor-bytes tor-checkable tor-linkspec tor-netdoc tor-persist arti-client 2023-02-28T12:10:00Z Nick Mathewson nickm@torproject.org 2023-02-28T12:10:00Z urn:sha1:3e1ae65212575742d50fb2a8ff585b891a985698 (The breaking change was removing `as_days()` from IntegerMinutes.) We are _not_ calling this a downstream-api breaking change, per discussion at https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1012?commit_id=bb2ab7c2a3e0994bb438188511688b5b039cae29#note_2876819 2023-02-28T12:06:15Z Nick Mathewson nickm@torproject.org 2023-02-28T12:06:15Z urn:sha1:4479d52a88272dc4710c2a24b11a27d57d4ae0ca These are API breaks, but the crates themselves are currently 100% experimental, so there's no need to bump the minor versions according to our semver rules. 2023-02-28T12:05:15Z Nick Mathewson nickm@torproject.org 2023-02-28T12:05:15Z urn:sha1:3e257a7cb57801329f013e7c1dc2d8c2dc598e47 This includes tor-cell, tor-proto, and tor-netdir. 2023-02-28T11:10:17Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-02-24T14:26:25Z urn:sha1:f63c7c48afd94fe9d09746f0b76fbaff8d4a1a79 Fixes #756 2023-02-09T15:20:28Z Nick Mathewson nickm@torproject.org 2023-02-08T12:41:17Z urn:sha1:16b9d23a7c0439b574eedd11323884f71a26148d This allows us to remove a shenanigan from `restricted_msg!{}`.