summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | | arti: Remove a completed TODO.Gabriela Moldovan2024-09-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | The tests were added in !2275
| * | | | | tor-hsservice: Add API for generating the hsid for a service.Gabriela Moldovan2024-09-171-2/+30
| | | | | | | | | | | | | | | | | | | | | | | | This also reexports `HsId` from the `tor-hsservice` crate.
| * | | | | tor-hsservice: Make maybe_generate_hsid take a selector (fmt).Gabriela Moldovan2024-09-171-3/+14
| | | | | |
| * | | | | tor-hsservice: Make maybe_generate_hsid take a selector.Gabriela Moldovan2024-09-171-6/+8
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We will soon add a new `OnionService` function for generating an HsId for the service without launching it (#1621). This new API will be implemented using `maybe_generate_hsid`, which will need to take the user-provided keystore selector as an argument. (the selector exists for future-proofing reasons; we're not yet exposing it in the CLI, but it will be part of the new `OnionService` API)
* | | | | Merge branch 's101-2024-q2' into 'main'Alexander Hansen Færøy2024-09-171-0/+26
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | Update s101 numbers for Q2 2024 See merge request tpo/core/arti!2245
| * | | | Update s101 numbers for Q2 2024Alexander Færøy2024-07-081-0/+26
| | | | |
* | | | | Merge branch 'bug_1612v2' into 'main'gabi-2502024-09-171-1/+45
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bug 1612: Allow programmatic launching of onion-service with user-provided HsIdKeypair Closes #1612 See merge request tpo/core/arti!2402
| * | | | | arti-client: add experimental launch_onion_service_with_hsid() method which ↵Morgan2024-09-151-1/+45
| | | | | | | | | | | | | | | | | | | | | | | | HsIdKeypair
* | | | | | Merge branch 'defer-hsid-generation' into 'main'gabi-2502024-09-174-48/+29
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | | | | | | | | | | | | | tor-hsservice: Do not generate the HsId until the service is launched. See merge request tpo/core/arti!2417
| * | | | | arti: Test hss onion-name behavior when the hsid is missing.Gabriela Moldovan2024-09-172-0/+17
| | | | | |
| * | | | | tor-hsservice: Do not generate the HsId until the service is launched.Gabriela Moldovan2024-09-171-8/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This defers generating an HsId until `OnionService::launch`, enabling us to use APIs like `OnionService::onion_name` to e.g. check for the existence of an HsId (previously, you couldn't do that because creating an `OnionService` would auto-generate the `HsId`).
| * | | | | tor-hsservice: Remove outdated TODO.Gabriela Moldovan2024-09-171-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As per #1247, we decided to stick with the current name. As for the docs, they were added in !1946
| * | | | | tor-hsservice: Remove deprecated constructor.Gabriela Moldovan2024-09-172-36/+2
|/ / / / / | | | | | | | | | | | | | | | This has been deprecated since 1.2.6, so let's remove it.
* | | | | Merge branch 'take_all_but' into 'main'Nick Mathewson2024-09-162-8/+75
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Implement and user Reader::take_all_but() Closes #1620 See merge request tpo/core/arti!2415
| * | | | | tor-proto: Use Reader::take_all_but().Nick Mathewson2024-09-162-21/+15
| | | | | |
| * | | | | tor-bytes: Add a new take_all_but method.Nick Mathewson2024-09-161-0/+73
| | | | | |
* | | | | | Merge branch 'ticket_1591' into 'main'Nick Mathewson2024-09-163-97/+108
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rpc: Simplify handling of fatal Json read errors. Closes #1591 See merge request tpo/core/arti!2400
| * | | | | | rpcserver: Split a few long lines.Nick Mathewson2024-09-161-5/+10
| | | | | | |
| * | | | | | rpcserver: move is_connection_close detection into run_loop.Nick Mathewson2024-09-161-6/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've used an `async{ expr }.await` pattern, to make sure that _every_ error returned by the `loop{select!{}}` construct is actually transformed.
| * | | | | | rpcserver: Add an extra level of braces.Nick Mathewson2024-09-161-50/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (This will make the next commit easier to read.)
| * | | | | | rpcserver: Apply documentation suggestion.Nick Mathewson2024-09-161-0/+2
| | | | | | |
| * | | | | | rpcserver: Use a struct to enforce explicit ContinueNick Mathewson2024-09-161-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Per suggestion from @diziet.
| * | | | | | rpc: Simplify simplified close logic even furtherNick Mathewson2024-09-162-35/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of classifying errors and complicating our behavior _early_ in our loop, instead we just decide whether an error indicates an EOF immediately before we return it.
| * | | | | | rpc: Simplify close logic even further.Nick Mathewson2024-09-161-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make it more clear than the previous match statement that once we get an Err() from request_stream.next(), we aren't going to continue the loop.
| * | | | | | rpc: Simplify handling of fatal Json read errors.Nick Mathewson2024-09-163-44/+33
|/ / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, after determining that an error on an RPC connection was fatal, we would: 1. Determine whether it was a "clean" close or one that needed to be logged. 2. In exactly one case (specifically, when the inbound Json stream contained a Value that was not an Object) , we would send back a message to the client. 3. Exit the connection with Ok() or Err(e). We no longer do step "2" above. Additionally, we document: - Why it's important to exit immediately on syntax errors. - A better way to tolerate non-Object Json Values, if we decide someday to do so. Closes #1591.
* | | | | | Merge branch 'circmgr-remove-abstractspec' into 'main'Nick Mathewson2024-09-164-260/+328
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | tor-circmgr: Remove AbstractSpec and FakeSpec. See merge request tpo/core/arti!2412
| * | | | | Add test for CircList::find_open.Wesley Aptekar-Cassels2024-09-161-1/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This tests that when requesting preemptive circuits, they are not given out when a insufficient number of circuits are in the CircList, but that they are given out once the required number of circuits has been reached.
| * | | | | tor-circmgr: Remove AbstractSpec and FakeSpec.Wesley Aptekar-Cassels2024-09-164-260/+274
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AbstractSpec and FakeSpec actually make testing more difficult, since they prevent using FakeBuilder in code that relies on the concrete TargetCircUsage and SupportedCircUsage types. Removing them means FakeBuilder can be used in more places, and also means that the test code is closer to the real code, since TargetCircUsage and SupportedCircUsage are now exercised directly in more tests. This did require making one change to a test, which I think was previously testing behaviour that was true for FakeSpec but not for the real code: The mgr::test::isolated test previously asserted that, in the case where three circuits were requested, two with isolation and one without, the non-isolated circuit would be shared with one of the isolated circuits. This was allowed by the FakeSpec::supports function. However, in the actual code, the path is as follows: * AbstractCircMgr::get_or_launch * AbstractCircMgr::prepare_action * CircList::find_open * AbstractSpec::find_supported * abstract_spec_find_supported * OpenEntry::supports * SupportedCircUsage::supports * StreamIsolation::compatible_same_type StreamIsolation::compatible_same_type checks owner_type, which is always zero for non-isolated streams and always non-zero for isolated streams, meaning that a isolated stream will never be compatible with a non-isolated stream. The seems like desirable behaviour, so I simply modified the test to make four connections, two isolated and two not, and checked that the isolated streams never share any circuits, and that the two non-isolated streams use the same circuit. As far as I can tell, this is the intended behaviour in the existing code.
* | | | | Merge branch 'proxy-subcmd' into 'main'Nick Mathewson2024-09-163-188/+224
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | arti: Move proxy subcommand to a separate module. See merge request tpo/core/arti!2416
| * | | | arti: Move proxy subcommand to a separate module.Gabriela Moldovan2024-09-122-41/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | No functional changes, this is just code motion. This helps organize the code in `arti/src/lib.rs` a bit. It now only contains the argument parsing and various other setup, and all the subcommands are contained in separate modules.
| * | | | arti: Move arti::run to subcommands::proxy.Gabriela Moldovan2024-09-122-156/+172
| | | | | | | | | | | | | | | | | | | | No functional changes, this is just code motion.
| * | | | arti: Add a new module for the proxy subcommand.Gabriela Moldovan2024-09-122-0/+19
|/ / / / | | | | | | | | | | | | | | | | The implementation for `arti proxy` will soon be relocated to this new module.
* | | | Merge branch 'orport' into 'main'David Goulet2024-09-127-30/+170
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | tor-chanmgr: add experimental `ChanMgr::handle_incoming` See merge request tpo/core/arti!2389
| * | | | tor-chanmgr: add experimental `ChanMgr::handle_incoming`Steven Engler2024-09-117-4/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The channel manager in the future will need to be able to receive incoming streams. The type of the stream depends on an associated type within `ChannelFactory`, so this commit exposes this associated type through several other types, eventually to the `ChanMgr`. The new methods are behind the experimental "relay" feature flag.
| * | | | tor-chanmgr: make `CompoundFactory` generic over `ChannelFactory`Steven Engler2024-09-112-30/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This has two advantages: 1. Code is a little easier to follow with generics rather than dynamic dispatch, especially since the type is fixed at compile time anyways. 2. It allows us to access associated types of the `ChannelFactory`, which will be useful later for getting the stream type from the `ChanBuilder`.
* | | | | Merge branch 'rpc_proxy_info_fix' into 'main'Ian Jackson2024-09-121-1/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | rpc: Fix argument type for rpc_session_get_rpc_proxy_info See merge request tpo/core/arti!2409
| * | | | | rpc: Fix argument type for rpc_session_get_rpc_proxy_infoNick Mathewson2024-09-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Without this, we get a panic on startup when running with RPC! (This stresses the need for an integration test for RPC; I will start writing that after the Python wrapper lands.)
* | | | | | Merge branch 'rpc-rename-conn-to-stream' into 'main'Ian Jackson2024-09-124-27/+23
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | rpclib: Rename connect.rs to stream.rs, and "connect" identifiers to "open_stream" See merge request tpo/core/arti!2406
| * | | | | | rpclib: Remove TODO about connect=>stream renaming.Nick Mathewson2024-09-101-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AFIACT, all of this renaming is done. I've grepped for `[Cc]onn` and didn't find any more identifiers that needed to be renamed.
| * | | | | | rpclib: Rename "connect" to "open_stream" as appropriate.Nick Mathewson2024-09-103-21/+21
| | | | | | |
| * | | | | | rpclib: Rename connect.rs to stream.rsNick Mathewson2024-09-102-2/+2
| |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (This is about DataStreams, so we should make it less confusing. This commit is _just_ about the file renaming, with no associated function renaming.)
* | | | | | Merge branch 'inert-client-docs' into 'main'David Goulet2024-09-121-43/+5
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | arti-client: Remove duplicated documentation. See merge request tpo/core/arti!2414
| * | | | | | arti-client: Convert a note to a comment.Gabriela Moldovan2024-09-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This was supposed to be a comment, not part of the docs.
| * | | | | | arti-client: Remove duplicated documentation.Gabriela Moldovan2024-09-121-42/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `TorClient` and `InertTorClient` have a number of identical state-management functions. This makes the `InertTorClient` link to the `TorClient` docs instead of duplicating them.
* | | | | | | Merge branch 'reader-3' into 'main'Ian Jackson2024-09-1217-255/+414
|\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rework tor_bytes::Truncated Closes #1614 See merge request tpo/core/arti!2407
| * | | | | | | tor-bytes: Fix Truncated refs in various docs.Ian Jackson2024-09-121-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use "throws" terminology to avoid having to clutter the description with Err(). Many of these doc comments contain otiose text such as "returns Ok(()) on success" but let's not deal with that now.
| * | | | | | | tor-bytes: Rename OnIncomplete to Completeness (fmt)Ian Jackson2024-09-121-1/+1
| | | | | | | |
| * | | | | | | tor-bytes: Rename OnIncomplete to CompletenessIan Jackson2024-09-121-11/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | And rename its variants and update the docs to contemplate wider use, as suggested in #1620. As discussed here https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2407#note_3075658
| * | | | | | | tor_bytes: Clarify a method docIan Jackson2024-09-121-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Apropos https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2407#note_3075638
| * | | | | | | tor_bytes: Rename new_truncated_for_test to new_incomplete_for_test (fmt)Ian Jackson2024-09-121-2/+8
| | | | | | | |
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 17:20:58 +0000