aboutsummaryrefslogtreecommitdiff
path: root/crates/tor-proto
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge branch 'deftly-1.5' into 'main'Alexander Hansen Færøy2025-11-101-1/+1
|\ \ \ | | | | | | | | | | | | | | | | Bump derive-deftly to 1.5.0 See merge request tpo/core/arti!3451
| * | | Bump derive-deftly to 1.5.0Ian Jackson2025-11-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This has the meta attributes with optional values feature and also hygiene rework for modules. The breaking changes don't break arti.
* | | | Merge branch 'cell-sender' into 'main'Alexander Hansen Færøy2025-11-103-10/+10
|\ \ \ \ | |/ / / |/| | | | | | | | | | | proto: Move cell_sender out of the client module See merge request tpo/core/arti!3407
| * | | proto: Move cell_sender out of the client moduleGabriela Moldovan2025-10-283-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Soon we'll use CircuitCellSender in the relay reactor too (we need to, because it provides a useful abstraction for handling block/unblock padding actions, and because it has some handy helper functions such as `congestion_signals()`).
| * | | proto: Make everything in CircuitCellSender pub(crate)Gabriela Moldovan2025-10-281-8/+8
| |/ / | | | | | | | | | | | | | | | This is in preparation for moving `CircuitCellSender` out of the client module (it makes the next commit easier to review, because `cell_sender.rs` will be moved without any modifications).
* | | Merge branch 'deftly-1.4' into 'main'opara2025-11-061-1/+1
|\ \ \ | | | | | | | | | | | | | | | | Bump derive-deftly to 1.4.0 See merge request tpo/core/arti!3448
| * | | Bump derive-deftly to 1.4.0Ian Jackson2025-11-061-1/+1
| | |/ | |/| | | | | | | | | | | | | This will let us use the new modules feature. There are no breaking changes to beta features in 1.4.0.
* | | Fix name of clippy lint to unchecked_time_subtraction (2)Ian Jackson2025-11-0630-31/+31
| | | | | | | | | | | | Run maint/add_warning
* | | Drop two use's that seem no longer to be necessaryIan Jackson2025-11-061-1/+1
|/ /
* | all: run cargo fmtSteven Engler2025-11-044-4/+4
| |
* | all: replace all uses of `futures::task::SpawnExt` with `tor_rtcompat::SpawnExt`Steven Engler2025-11-045-5/+5
| |
* | bad_extend_test_impl: Wait for message instead of a 100 ms delay.Nick Mathewson2025-11-041-8/+18
| | | | | | | | Possible fix for #2232.
* | proto: use assert_matches in circuit.rs tests.Nick Mathewson2025-11-042-5/+7
| | | | | | | | | | | | | | | | | | Unlike assert!(matches!(..)), assert_matches prints the value of the expression on a failure. Probably we should use this macro more widely in the future. This might help diagnose recurrences of #2232
* | proto: Move a TODO to CircSyncViewGabriela Moldovan2025-10-302-3/+3
| |
* | proto: Replace ClientCircSyncView in IncomingStreamRequestFilterGabriela Moldovan2025-10-305-7/+10
| |
* | proto: Add a new CircSyncView typeGabriela Moldovan2025-10-302-0/+40
| | | | | | | | | | | | This will replace ClientCircView in the IncomingStreamRequestFilter APIs, which will enable us to use IncomingStreamRequestFilter for incoming streams on the exit side too.
* | maint: remove all semver.md filesSteven Engler2025-10-301-1/+0
| |
* | maint: bump minor versions of all published cratesSteven Engler2025-10-291-24/+24
| | | | | | | | | | | | | | ```bash readarray -t publish < <(cargo metadata --format-version 1 | jq -r '.packages[] | select((.id | startswith("path+file:///")) and (.rust_version != null) and (.publish == null or .publish == true or .publish != [])) | .name') for package in "${publish[@]}"; do echo "$package:"; cargo set-version --bump minor -p "$package"; done ```
* | Merge branch 'remove_socks' into 'main'Nick Mathewson2025-10-281-3/+3
|\ \ | | | | | | | | | | | | | | | | | | arti: Revise strings that implied that we were a SOCKS-only proxy. Closes #2225 See merge request tpo/core/arti!3398
| * | proto: Adjust a comment about a buffer size.Nick Mathewson2025-10-281-3/+3
| |/
* / maint: fixup featuresSteven Engler2025-10-281-0/+1
|/ | | | | | ```bash cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml ```
* proto: Avoid identifying relay circuits using TunnelIdGabriela Moldovan2025-10-271-3/+3
| | | | We replaced TunnelId with UniqId in the relay code a while ago.
* proto: Remove relay ChannelAuthenticationData builderDavid Goulet2025-10-232-82/+46
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Feature flag some relay specific codeDavid Goulet2025-10-232-8/+15
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Add relay todos for the handshakeDavid Goulet2025-10-231-0/+2
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Use Arc for relay identities objectDavid Goulet2025-10-233-5/+7
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Remove LOG_PREFIX in relay handshakeDavid Goulet2025-10-231-5/+1
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Re-arrange some importsDavid Goulet2025-10-231-3/+1
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Add a note about channel canonicityDavid Goulet2025-10-231-0/+5
| | | | Signed-off-by: David Goulet <[email protected]>
* proto: Compute authenticate data after validating certificatesDavid Goulet2025-10-234-15/+58
| | | | | | | | | | | | | | This is only done if we kept the AUTH_CHALLENGE cell and we have relay identities. In other words, this is only when the UnverifiedChannel was created from a RelayInitiatorHandshake. Note: The check_internal() function is too large and should be refactored in smaller pieces. Note: It is also likely that we need to split UnverifiedChannel and VerifiedChannel as it is getting client or relay members. Not great. Signed-off-by: David Goulet <[email protected]>
* proto: Add a relay channel builderDavid Goulet2025-10-233-2/+37
| | | | | | | | | | The client and relay channel builder don't share anything and return different objects hence the seperation. Furthermore, this seperation avoids having the client ChanMgr ability to launch relay channels. Signed-off-by: David Goulet <[email protected]>
* proto: Add RelayIdentities object holding our keysDavid Goulet2025-10-233-1/+63
| | | | | | | | | | | | | | | This is a intermediary object between tor-chanmgr and tor-proto that is when building a relay channel, those keys/certs need to be set in the ChannelBuilder so the tor-proto can use them to authenticate. We avoid that way making tor-proto depending on tor-keymgr for the ultimate goal to avoid tor-proto to have access to all the keys in the KeyMgr. Future commits will introduce a relay channel builder which will use that object to set the keys. Signed-off-by: David Goulet <[email protected]>
* proto: Add the channel authentication dataDavid Goulet2025-10-233-2/+155
| | | | | | | | | | | This commit only adds a struct holding all the authentication data that needs to be built during the verification process after all handshake cells needed for authentication have been sent. It lives in the VerifiedChannel struct so it can be used to build the AUTHENTICATE cell and be sent before the NETINFO. Signed-off-by: David Goulet <[email protected]>
* proto: Add RelayInitiatorHandshakeDavid Goulet2025-10-235-1/+141
| | | | | | | This implements the relay initiator side of the handshake up to the creation of an unverified channel. Signed-off-by: David Goulet <[email protected]>
* proto: Change visibility for some channel objectsDavid Goulet2025-10-233-19/+20
| | | | | | | | | | Upcoming code for relay channels are put in the src/relay module and thus we need visibility into some channel generic things. Turns out also we don't need to re-export publicly UnverifiedChannel and VerifiedChannel. Signed-off-by: David Goulet <[email protected]>
* proto: Replace select! with select_biased!Gabriela Moldovan2025-10-221-2/+2
| | | | We need to give the control channels higher priority here.
* proto: Update an outdated doc linkGabriela Moldovan2025-10-221-1/+1
|
* proto: Add debug log when RelayReactor shuts downGabriela Moldovan2025-10-221-2/+14
|
* proto: Replace futures::select with importGabriela Moldovan2025-10-221-2/+2
|
* proto: Remove no-longer relevant note on control message handlingGabriela Moldovan2025-10-221-10/+0
|
* proto: Remove an already-addressed TODOGabriela Moldovan2025-10-221-2/+0
|
* proto: Handle control messages in RelayReactorGabriela Moldovan2025-10-222-51/+53
| | | | Control messages are handled in RelayReactor instead of BackwardReactor.
* proto: Move the control channels to RelayReactorGabriela Moldovan2025-10-222-53/+53
| | | | | This only moves the control/command fields to RelayReactor. The next step is to actually implement the control message handling and dispatch.
* tor-proto: fix `clippy::needless_pass_by_value` warningSteven Engler2025-10-211-0/+1
|
* Merge branch 'msrv-1-86-0' into 'main'David Goulet2025-10-211-1/+1
|\ | | | | | | | | Bump MSRV from 1.85.1 to 1.86 See merge request tpo/core/arti!3382
| * Bump MSRV from 1.85.1 to 1.86Clara Engler2025-10-211-1/+1
| |
* | proto: Fix broken doc linksGabriela Moldovan2025-10-211-2/+3
| |
* | proto: Prioritize shutdown over everything elseGabriela Moldovan2025-10-211-8/+8
| |
* | proto: Ensure RelayReactor shuts down the other reactorsGabriela Moldovan2025-10-213-21/+48
| | | | | | | | | | | | | | | | | | The `RelayReactor` now holds the sending end of the shutdown broadcast channel, so if `RelayReactor` exits, both the forward and the backward relay reactor will notice and shut down too. Similarly, if the forward or backward reactor exits, the `RelayReactor` will notice (because it select!s between the two), and will shut down
* | proto: Add TODO about moving control message handling to RelayReactorGabriela Moldovan2025-10-211-0/+3
| |
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 09:58:02 +0000