mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0 2025-08-28T10:54:48Z 2025-08-28T10:54:48Z Gabriela Moldovan gabi@torproject.org 2025-08-27T13:02:57Z urn:sha1:567c8bd287c5c5a45b602be80c119fd741f9eb3a The `TunnelId*` types will be reused in the relay reactor (exit relays need to have the concept of a "tunnel ID" because of conflux). Now the `relay::reactor` module only has a single import from `client` (for the `unwrap_or_shutdown` helper, which we should be able to remove soon). From now, we will avoid importing anything from `client` in the `relay` module, and instead prefer refactoring the code as needed (to pull the implementation-agnostic parts outside of `client`). This commit has no functional changes, just code motion. 2025-08-28T10:54:48Z Gabriela Moldovan gabi@torproject.org 2025-08-26T17:48:56Z urn:sha1:4ee5a4abcee895e79588888f6bc8eaa6963a6ba7 This is just code motion (I suggest reviewing with `--color-moved`). This also moves the implementation-agnostic parts from `tor_proto::client::circuit` to a new `tor_proto::circuit` module. 2025-08-18T16:09:04Z Gabriela Moldovan gabi@torproject.org 2025-08-18T15:52:38Z urn:sha1:702e7276898d3f31e22033c5b64fea91703f3701 The `stream` module is client-specific, for the most part, so I am moving it under `client`. Later on, we will factor out the parts that can be shared with the relay implementation. Note: this is a breaking change as the deleted `stream` module was `pub`. We could've kept the module and reexported from it the public types from `tor_proto::client::stream`, but I think it's better to have this `client` namespacing, because it makes the separation between the client and relay parts clearer. 2025-08-18T16:09:04Z Gabriela Moldovan gabi@torproject.org 2025-08-18T15:16:39Z urn:sha1:f91f291c75b61bf29521755f77097cfa1bc8fe58 2025-08-18T16:09:04Z Gabriela Moldovan gabi@torproject.org 2025-08-18T15:14:43Z urn:sha1:1ee26f2168ee2dede8ab993ef57435334e9efabe The implementation from `tunnel` is client-specific, so we are renaming the module accordingly. The more generic parts will be pulled into a separate module in a future commit. 2025-08-18T16:09:04Z Gabriela Moldovan gabi@torproject.org 2025-08-18T14:57:26Z urn:sha1:4a6c8da93c392726c96420dc8983a0beebb347d8 This reorganizes the `relay_tunnel` module as per @dgoulet's [suggestion]. [suggestion]: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/3162/diffs#note_3240092 2025-08-18T11:14:35Z Gabriela Moldovan gabi@torproject.org 2025-08-13T12:40:08Z urn:sha1:0e8e00dedf90f2366b284b346bf17da73e384448 The new relay tunnel reactor will live in this module for now. This is temporary, as I expect we will soon need to reorganize this crate a little bit, to more clearly separate the client-specific parts from the relay ones. 2025-08-07T16:47:52Z Nick Mathewson nickm@torproject.org 2025-08-07T16:47:52Z urn:sha1:f40f8f89e71b102ac6827269fd4a3b0dec2d205b Enable counter-galois onion negotiation and make it work. See merge request tpo/core/arti!3133 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. 2025-08-06T15:59:21Z Nick Mathewson nickm@torproject.org 2025-08-06T12:48:30Z urn:sha1:eb83e81608877a36beff7b716e7b8420287e570d