mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.5 2023-06-01T14:03:05Z 2023-06-01T14:03:05Z Nick Mathewson nickm@torproject.org 2023-06-01T14:03:05Z urn:sha1:daf5ecc15340c5910fdb912ea9099719befd916e Generated with the following commands: ``` cargo set-version --bump minor -p tor-cell cargo set-version --bump minor -p tor-linkspec cargo set-version --bump minor -p tor-proto cargo set-version --bump minor -p tor-netdoc cargo set-version --bump minor -p tor-circmgr cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-basic-utils cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-hscrypto cargo set-version --bump patch -p tor-checkable cargo set-version --bump patch -p tor-async-utils cargo set-version --bump patch -p caret cargo set-version --bump patch -p fs-mistrust cargo set-version --bump patch -p safelog cargo set-version --bump patch -p retry-error cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-events cargo set-version --bump patch -p tor-units cargo set-version --bump patch -p tor-rtcompat cargo set-version --bump patch -p tor-rtmock cargo set-version --bump patch -p tor-protover cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-socksproto cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-congestion cargo set-version --bump patch -p tor-persist cargo set-version --bump patch -p tor-chanmgr cargo set-version --bump patch -p tor-ptmgr cargo set-version --bump patch -p tor-guardmgr cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-hsclient cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p arti-rpcserver cargo set-version --bump patch -p arti-config cargo set-version --bump patch -p arti-hyper cargo set-version --bump patch -p arti cargo set-version --bump patch -p arti-bench cargo set-version --bump patch -p arti-testing ``` 2023-05-23T17:33:07Z Nick Mathewson nickm@torproject.org 2023-05-23T17:33:07Z urn:sha1:24d67594d7117cf0b5b5e5283d7d92619494ed0e 2023-05-17T20:22:35Z Nick Mathewson nickm@torproject.org 2023-05-17T15:20:20Z urn:sha1:07e2ed0e5c83bae55f157d8f880fa6823049ccbf We never want to create one of these from its parts except when we are testing it; we only want to forward an Introduce1 message with a new command on it. 2023-05-17T20:22:35Z Nick Mathewson nickm@torproject.org 2023-05-17T15:16:54Z urn:sha1:c3c44cea67ed6b9f1856836c535b935c51747245 We'll need to store this so that it can later on be used to complete the hs_ntor handshake. 2023-05-17T15:06:28Z Nick Mathewson nickm@torproject.org 2023-05-17T15:06:28Z urn:sha1:a6ad49b22bf3f3efe53b3b8e225516f4a5588ebf We'll want this because our hs_ntor handshake requires access to an encoded version of the header independent from the actual encrypted message. part of #866. 2023-05-15T15:00:28Z Nick Mathewson nickm@torproject.org 2023-05-15T15:00:28Z urn:sha1:6fa821238dcaa98f08d3b0a92af7e1f9843296dd 2023-05-15T14:41:32Z Nick Mathewson nickm@torproject.org 2023-05-15T12:37:35Z urn:sha1:4b08ef76a0e9d913ea2c2e7ab0cda48ee2eba805 This litters our Cargo.toml files with "XXX" entries that we should fix. 2023-05-15T13:09:43Z Nick Mathewson nickm@torproject.org 2023-05-15T12:34:47Z urn:sha1:e2e125fef7c027a24f23397eb1644a8565ad5d8b 2023-05-15T13:07:21Z Nick Mathewson nickm@torproject.org 2023-05-15T12:16:43Z urn:sha1:7a5373c11007f29007341dc871c14ae1fa026cef This does the following: - Gives every crate a `full`. - Cause every `full` to depend on `full` from the lower-level crates. - Makes every feature listed _directly_ in `experimental` depend on `__is_experimental`. 2023-05-10T16:30:32Z Nick Mathewson nickm@torproject.org 2023-05-10T16:25:57Z urn:sha1:7ce808b75bb500f27ce7837d4f76cbf7fc1ee705 If we didn't do this, we would need to transfrom `EncodedLinkSpec`s into a `LinkSpec::Unrecognized`, which is not semantically right. What's more, every user of this API wants to consume encoded link specifiers, so encoding them early saves a little effort.