summaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
* | | arti-client: Resolve XXX to make CI run.Gabriela Moldovan2025-08-051-23/+26
| | |
* | | proto: abolish path_ref() in favor of all_paths().Gabriela Moldovan2025-08-057-56/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until now, we've been using `ClientCirc::path_ref()` to get the *only* path of a circuit. Now that `ClientCirc` is a handle to a tunnel reactor (which may or may not be multi-path), we need to decide for each call site of `path_ref()`, if we actually want *all* paths in the tunnel, or if we expect the tunnel to be single-path and thus want the *only* path in the tunnel. I've added two new APIs to address this: `all_paths()`, for getting all the paths in the tunnel, and `single_path()` for getting the only path in the tunnel, or an error if the tunnel is single-path.
* | | hsservice, hsclient: Enable tor-circmgr/send-control-msg too.Gabriela Moldovan2025-08-052-2/+2
| | |
* | | proto: Use UserMsgHandler instead of MsgHandler throughout.Gabriela Moldovan2025-08-051-8/+8
| | |
* | | proto: Make UserMsgHandler pub if send-control-msg is enabled.Gabriela Moldovan2025-08-051-0/+1
| | | | | | | | | | | | | | | When the `send-control-msg` feature is enabled, we reexport it from `tor-proto`, so it needs to be made `pub`.
* | | circmgr: Feature-gate ServiceOnionServiceIntroTunnel to fix compile errors.Gabriela Moldovan2025-08-051-0/+1
| | |
* | | circmgr: Feature-gate send_raw_msg.Gabriela Moldovan2025-08-051-0/+1
| | |
* | | circmgr: Gate tor_proto::handshake usage behind hs-common.Gabriela Moldovan2025-08-051-1/+6
| | |
* | | proto, circmgr: Fix feature-gating.Gabriela Moldovan2025-08-053-3/+5
| | |
* | | proto: Feature-gate UserMsgHandler.Gabriela Moldovan2025-08-051-1/+3
| | |
* | | circmgr: Fully-qualify types in macro.Gabriela Moldovan2025-08-051-4/+2
| | |
* | | circmgr: Add back cognitive_complexity allows.Gabriela Moldovan2025-08-052-0/+2
| | | | | | | | | | | | | | | These were removed somewhere along the way (which is now causing the clippy checks to fail).
* | | proto: Return a more specific error message from allow_stream_requests.Gabriela Moldovan2025-08-052-5/+8
| | | | | | | | | | | | | | | | | | | | | Previously the error message would say `Single circuit getter on multi path tunnel`. The new error message makes it clearer that calling `ClientTunnel::allow_stream_requests()` on a multi path tunnel is not supported.
* | | proto: Set is_multi_path = true in the tests.Gabriela Moldovan2025-08-051-6/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the `allow_stream_requests()` tests which ensures we don't allow incoming streams on multipath tunnels (because we don't currently support it). This also changes `newcirc_ext` to return `ClientTunnel` instead of `Arc<ClientTunell>` (we need to mutate `ClientTunnel` to manually set `is_multi_path` on its inner `ClientCirc`).
* | | proto: Avoid using as_single_circ() in the conflux tests (fmt).Gabriela Moldovan2025-08-051-5/+1
| | |
* | | proto: Avoid using as_single_circ() in the conflux tests.Gabriela Moldovan2025-08-051-3/+2
| | | | | | | | | | | | `as_single_circ()` returns an error for multipath tunnels.
* | | circmgr: Fix unit testsDavid Goulet2025-08-052-15/+15
| | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
* | | proto: Fix the tunnel/circuit.rs unit testsDavid Goulet2025-08-052-80/+122
| | | | | | | | | | | | | | | | | | Adapt all tests to use the new ClientTunnel. Signed-off-by: David Goulet <[email protected]>
* | | proto: Remove todo!() from StreamTarget::protocol_error()David Goulet2025-08-051-1/+1
| | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
* | | arti-client: Use the new Tunnel interfaceDavid Goulet2025-08-052-26/+34
| | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
* | | dirmgr: Rename circuit to tunnelDavid Goulet2025-08-051-3/+3
| | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
* | | tunnel: Implement start_conversation() for all tunnel typesDavid Goulet2025-08-059-167/+178
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The BaseTunnel now has a start_conversation() which takes a TargetHop meaning it can be used with a multi path tunnel. The Conversation object has been moved into the tunnel namespace out of the circuit one. Signed-off-by: David Goulet <[email protected]>
* | | hs: Use the new Tunnel interface for onion serviceDavid Goulet2025-08-0514-230/+392
| | |
* | | dirclient: Use the new Tunnel interface (fmt).Gabriela Moldovan2025-08-051-1/+3
| | |
* | | dirclient: Use the new Tunnel interfaceDavid Goulet2025-08-054-20/+29
| | | | | | | | | | | | | | | | | | This entirely removes the requirement on ClientCirc. Signed-off-by: David Goulet <[email protected]>
* | | circmgr: Return more type specific tunnelDavid Goulet2025-08-052-8/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is the first step towards making the circmgr return high level tunnel types (wrappers around ClientTunnel). Future commits will then modify each subsystems to use those specific types. They are split in order to reduce complexity. Signed-off-by: David Goulet <[email protected]>
* | | tunnel: Implement Buildable for ClientTunnelDavid Goulet2025-08-056-88/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to pull this off, the Arc requirement needs to go away because the Arc<ClientCirc> is now within the ClientTunnel. This commit also has a rename of the CircuitBuilder to TunnelBuilder in order to reflect the change that it now builds a ClientTunnel. There is a slight rename in tor-proto as well just for accuracy. Signed-off-by: David Goulet <[email protected]>
* | | proto: Change PendingClientCirc to yield back a ClientTunnelDavid Goulet2025-08-053-27/+28
| | | | | | | | | | | | | | | | | | And rename it in the process to "PendingClientTunnel". Signed-off-by: David Goulet <[email protected]>
* | | circmgr: Major rename for the new Tunnel namespaceDavid Goulet2025-08-058-625/+635
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The CircMgr will no longer yield circuits but tunnels (src/tunnel.rs). This is a first step to rename most circuit related objects to use "tunnel" instead. Some "circuit" names have been kept for more precise definitions. No behavior changes. Signed-off-by: David Goulet <[email protected]>
* | | proto: Add last_hop() to Tunnel interfaceDavid Goulet2025-08-052-0/+43
| | | | | | | | | | | | Signed-off-by: David Goulet <[email protected]>
* | | circmgr: New Tunnel object interfaceDavid Goulet2025-08-054-2/+494
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce the new Tunnel structs that is planned to expose publicly as a replacement to `ClientCirc`. Future commits will make those tunnel objects be used accross the code base up until tor-proto which than handles Circuit directly. Signed-off-by: David Goulet <[email protected]>
* | | proto: Move ClientCirc stream functions to ClientTunnelDavid Goulet2025-08-056-483/+456
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In order to pull this off, some client => tunnel renaming needed to happen including the comments. The send_raw_msg() is an experimental and expert mode method that any tunnel should have access to in order to be able to send whatever message in whatever tunnel type. No behavior changes. Signed-off-by: David Goulet <[email protected]>
* | | proto: Add a new ClientTunnel typeGabriela Moldovan2025-08-053-2/+103
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To use the functionality only allowed on single-circuit tunnels (such as `extend*`), callers will have to call `ClientTunnel::as_single_circ()` to obtain a handle to the underlying `ClientCirc`. This is an opinionated design decision that goes against the plan from [!2790]. It stems from my thinking that it would make more sense to keep `ClientCirc`, than to merge it into `ClientTunnel`. If we merge the two, many functions will need become fallible and less ergonomic, because the user of `ClientTunnel` needs to know whether the `ClientTunnel` consists of a single-circuit or not. Providing (fallible) access to the underlying `ClientCirc` of the `ClientTunnel` seems simpler than the alternative. That being said, I am open to switching back to the original plan if this design turns out to be annoying to work with. [!2790]: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2790
* | | Merge branch 'fix_rustdoc_nightly' into 'main'Nick Mathewson2025-08-0514-8/+30
|\ \ \ | |_|/ |/| | | | | | | | Fix errors from rustdoc nightly. See merge request tpo/core/arti!3124
| * | Fix errors from rustdoc nightly.Nick Mathewson2025-08-0514-8/+30
| | |
* | | Merge branch 'changelog' into 'main'arti-v1.4.6Ian Jackson2025-08-051-1/+1
|\ \ \ | | | | | | | | | | | | | | | | Changelog content for 1.4.6 See merge request tpo/core/arti!3119
| * | | Update the release dateIan Jackson2025-08-051-1/+1
| | |/ | |/|
* | | Bump version of tor-basic-utilsIan Jackson2025-08-0528-35/+35
| | | | | | | | | | | | This was accidentally omitted from my version bump script.
* | | Update hashx-bench lockfileIan Jackson2025-08-051-20/+27
| | | | | | | | | | | | cd crates/hashx/bench && cargo update
* | | Update equix-bench lockfileIan Jackson2025-08-051-20/+27
| | | | | | | | | | | | cd crates/equix/bench && cargo update
* | | Version bumps for 1.4.6Ian Jackson2025-08-0550-445/+445
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Made with the following shell script: export CARGO='nailing-cargo -Eu' # Non-functional changes only maint/bump_nodep hashx # Special $CARGO set-version -p arti 1.4.6 # Additional features, no breaking changes, depended on in tree $CARGO set-version -p safelog 0.4.8 # Unconditional bump to 0.33.0 xargs -I P <<END $CARGO set-version -p P 0.33.0 tor-error tor-general-addr tor-geoip tor-rtcompat tor-rtmock tor-async-utils tor-config tor-config-path tor-rpc-connect tor-log-ratelim tor-rpcbase tor-memquota tor-units tor-llcrypto tor-bytes tor-protover tor-checkable tor-cert tor-key-forge tor-hscrypto tor-socksproto tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir tor-relay-selection tor-persist tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy tor-relay-crypto arti-client arti-relay arti-rpcserver arti-ureq arti-rpc-client-core END
* | Merge branch 'update' into 'main'Ian Jackson2025-08-0425-26/+26
|\ \ | | | | | | | | | | | | Dependency updates (release prep) See merge request tpo/core/arti!3117
| * | Bump rusqlite to 0.37Ian Jackson2025-08-041-1/+1
| | |
| * | Bump derive-deftly to 1.2.0Ian Jackson2025-08-0424-25/+25
| |/ | | | | | | No upstream changes that break our code.
* | Merge branch 'features' into 'main'Nick Mathewson2025-08-043-1/+4
|\ \ | | | | | | | | | | | | Sort out fixup-features See merge request tpo/core/arti!3120
| * | cargo features: Run fixup-features (fmt)Ian Jackson2025-08-041-1/+2
| | | | | | | | | | | | Manual format tidying
| * | cargo features: Run fixup-featuresIan Jackson2025-08-042-2/+2
| | | | | | | | | | | | | | | | | | This just added some obvious full-transitivity. It left a formatting oddity.
| * | cargo features: Restore "memquota" feature into "full"Ian Jackson2025-08-042-0/+2
| |/ | | | | | | | | Our feature doctrine doesn't have a special case for features that are empty and retained for compatibility. "full" is probably best.
* / arti-ureq: Move `builder()` and `new()` to non-generic PreferredRuntime implnield2025-08-041-4/+6
|/ | | | `builder()` and `new()` always return a runtime with `tor_rtcompat::PreferredRuntime` so these methods should only be implemented for that type.
* tor-memquota: moved auto calc into separate functionSteven Engler2025-07-311-49/+112
|
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 20:22:30 +0000