summaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
...
| * | tor-netdoc: remove use of arrayref.Nick Mathewson2023-06-012-4/+7
| | |
| * | tor-proto: Remove use of arrayref.Nick Mathewson2023-06-013-5/+10
| | |
| * | tor-bytes: Remove use of arrayrefNick Mathewson2023-05-254-20/+16
| | | | | | | | | | | | | | | Part of #872: Now that const generics are in, we have better ways to express converting slices into array-references.
* | | arti: Interpret socks request to mean "lookup an RPC session"Nick Mathewson2023-06-052-14/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | The actual decoding here is just a placeholder. The important part is that we can get either a (SessionId, StreamId) tuple out of the request, or we treat it as part of an isolation token. This commit has a few TODOs for additional things that we'll need in order to build out our design.
* | | arti: Move SOCKS code for building StreamPrefs and getting a TorClient.Nick Mathewson2023-06-051-12/+25
| | |
* | | arti: Add an alias in the SOCKS code for per-conn isolatino info.Nick Mathewson2023-06-051-4/+10
| | | | | | | | | | | | This enables some small simplifications.
* | | RPC: Note a possible API change in RpcMgr::new.Nick Mathewson2023-06-051-0/+4
| | |
* | | RPC: Make Session objects get a GlobalId.Nick Mathewson2023-06-051-1/+7
| | |
* | | RPC: tell the `arti` SOCKS code about an RpcMgr object.Nick Mathewson2023-06-053-23/+78
| | | | | | | | | | | | | | | It will use this to find which TorClient to use when opening a stream.
* | | RPC: Give out and accept GlobalIds for appropriate objects.Nick Mathewson2023-06-053-11/+86
| | |
* | | RPC: Let objects declare that they need a GlobalId.Nick Mathewson2023-06-051-1/+17
| | |
* | | RPC: Implement a "global identifier" for non-session-bound IDsNick Mathewson2023-06-055-8/+299
| | | | | | | | | | | | | | | | | | | | | These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
* | | rpc: Slightly refactor GenIdx encoding.Nick Mathewson2023-06-053-17/+27
| | |
* | | rpc: Give RpcMgr a registry of connections.Nick Mathewson2023-06-053-5/+68
| | | | | | | | | | | | | | | We're going to use this to implement arti#863, which requires that some RPC objects be globally nameable.
* | | rpc: Move Arc::new() to RpcMgr code.Nick Mathewson2023-06-052-4/+4
| | |
* | | tor-circmgr: send_control_message: Add reference to MR discussionIan Jackson2023-06-051-0/+2
| | |
* | | tor-circmgr: send_control_message: Change a rename proposalIan Jackson2023-06-051-1/+1
| | | | | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1218#note_2908119
* | | tor-circmgr: send_control_message: Fix reference to circuitIan Jackson2023-06-051-1/+1
| | |
* | | tor-circmgr: send_control_message: API change proposalIan Jackson2023-06-051-0/+21
| | | | | | | | | | | | | | | | | | I am hoping we can merge this as a "TODO (Diziet)", even though I think it may be controversial. Ie merging this doesn't represent a decision to do as I suggest.
* | | tor-circmgr: Propose to rename `MetaCellDisposition::UninstallHandler`Ian Jackson2023-06-051-0/+4
| | |
* | | tor-circmgr: send_control_message: Clarify some corner casesIan Jackson2023-06-052-7/+34
| |/ |/| | | | | | | | | | | | | | | | | | | | | Also, no longer talk about handlers being "installed". That's not something that's exposed by this API. And, say that `send_control_message` can be called again only after *`send_control_message`* returns, not when `handle_msg` has returned `UinstallHandler`. IMO this makes more sense. Explain that we can't maintain a continuous watch while holding a conversation with the peer. (This is surely an API bug.)
* | Remove semver.md files from 1.1.5Nick Mathewson2023-06-016-14/+0
| |
* | Merge branch 'bump-versions-v115' into 'main'arti-v1.1.5Ian Jackson2023-06-0143-306/+306
|\ \ | | | | | | | | | | | | Bump crate versions in preparation for v1.1.5 release. See merge request tpo/core/arti!1211
| * | Bump crate versions in preparation for v1.1.5 release.Nick Mathewson2023-06-0143-306/+306
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 ```
* | | fallbackdir: Update list generated on June 01, 2023Tor CI Release2023-06-011-892/+896
|/ / | | | | | | Signed-off-by: Tor CI Release <[email protected]>
* / Run fixup-features script and resolve its complaints.Nick Mathewson2023-05-314-4/+9
|/
* Merge branch 'stream_ctrl' into 'main'Nick Mathewson2023-05-244-3/+238
|\ | | | | | | | | | | | | Experimental new stream-ctrl feature Closes #847 See merge request tpo/core/arti!1198
| * Add "TODO RPC" notes around DataStreamCtrl per review.Nick Mathewson2023-05-242-0/+16
| |
| * proto: Add stream-status functionality to DataStreamCtrl.Nick Mathewson2023-05-241-2/+106
| | | | | | | | There are some weaknesses and problems here; see TODO notes.
| * proto: Create a `DataStreamCtrl` type.Nick Mathewson2023-05-223-1/+114
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea here is that we want to make DataStream visible to the RPC system without requiring that the RPC session hold the DataStream itself (or the Reader, or the Writer). We could solve this problem by making _all_ the state in the DataStream shared, but that would introduce unnecessary extra locking in our critical path. Instead we're creating the notion of a "control handle" that lets you manage and observe a stream without actually owning the stream. Right now the only supported functionality is asking for the stream's circuit. Part of #847
| * proto: Add a new experimental stream-ctrl feature.Nick Mathewson2023-05-221-1/+2
| | | | | | | | | | (It doesn't do anything yet. It may eventually become always-on. But for now let's make this API optional. Part of #847)
| * tor-proto: Move a comment in Cargo.tomlNick Mathewson2023-05-221-1/+2
| |
* | Merge branch 'virtual_conditional' into 'main'Ian Jackson2023-05-242-0/+3
|\ \ | | | | | | | | | | | | proto: Make PathEntry::Virtual feature-conditional. See merge request tpo/core/arti!1201
| * | proto: Make PathEntry::Virtual feature-conditional.Nick Mathewson2023-05-232-0/+3
| | | | | | | | | | | | | | | This fixes a warning when building tor-proto without the `rpc-common` feature.
* | | Merge branch 'rpc-auth-and-meta' into 'main'Nick Mathewson2023-05-247-111/+333
|\ \ \ | | | | | | | | | | | | | | | | rpc: authentication and basic handle manipulation See merge request tpo/core/arti!1200
| * | | rpc: Remove downgrade_owned for nowNick Mathewson2023-05-244-42/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Rationale: Our weak-vs-strong design is a bit confused at the moment due to concerns about deduplication and capability semantics. It's not clear that a general "change strong to weak" method is compatible with what we want to provide.
| * | | rpc: Disable auth:get_rpc_protocol for now.Nick Mathewson2023-05-241-0/+8
| | | |
| * | | rpc: Implement functionality to remove objects from a sessionNick Mathewson2023-05-245-5/+135
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've made doing some design choices here: * Reserving "rpc" as a prefix for post-authentication functionality that is not arti-specific. * Declaring these to be methods on the session rather than methods on the objects themselves. There's a problem with defining an API to drop a weak reference; see comment in code.
| * | | rpc: fix documentation for methods in Context.Nick Mathewson2023-05-241-6/+4
| | | |
| * | | rpc: Make the top-level returned object a "session".Nick Mathewson2023-05-244-38/+67
| | | | | | | | | | | | | | | | | | | | | | | | This will make it easier to change the semantics of what exactly we return, whether it has to be/contain a client, whether you can use it to look up all the live objects, &etc.
| * | | rpc: Implement auth:query.Nick Mathewson2023-05-231-1/+39
| | | |
| * | | rpc: Implement the auth:get_rpc_protocol method.Nick Mathewson2023-05-231-0/+49
| | | |
| * | | rpc: move existing auth code to new module.Nick Mathewson2023-05-232-72/+84
| |/ /
* | | Merge branch 'real_generational_arena' into 'main'Nick Mathewson2023-05-242-79/+2
|\ \ \ | | | | | | | | | | | | | | | | rpc: Use the real generational-arena crate See merge request tpo/core/arti!1203
| * | | rpc: Remove fake_generational_arenaNick Mathewson2023-05-232-79/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Now that generation-arena has merged [@diziet's patch] to clarify their license, we no longer need to disable it. [@diziet's patch]: https://github.com/fitzgen/generational-arena/pull/56
* | | | cell: Make EstablishRendezvous contain a RendCookie.Nick Mathewson2023-05-232-6/+3
|/ / /
* | | Merge branch 'socks-read-fix' into 'main'Nick Mathewson2023-05-232-0/+25
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Fix a local-only CPU DoS bug. Closes #861 See merge request tpo/core/arti!1196
| * | Fix a local-only CPU DoS bug.Nick Mathewson2023-05-232-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, there was a bug in the way that our code used our SOCKS implementations. If the buffer used for a SOCKS handshake became full without completing the handshake, then rather than expanding the buffer or closing the connection, our code would keep trying to read into the zero-byte slice available in the full buffer forever, in a tight loop. We're classifying this as a LOW-severity issue, since it is only exploitable by pluggable transports (which are trusted) and by local applications with access to the SOCKS port. Closes #861. Fixes TROVE-2023-001. Reported-By: Jakob Lell <jakob AT srlabs DOT de>
* | | tor-hsclient: Mockable: Do concrete calls with UFCSIan Jackson2023-05-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Method dispatch rules mean that if the receiver type of the actual function changes, `self.call()` can turn into a purely-recursive call which overflows the stack. Async Rust doesn't have the usual warning for this situation :-(. UFCS is clumsier but doesn't have that problem because it involves much less magical dispatch. Instead of generating a recursive call which overflows the stack, it fails to compile.
* | | tor-hsclient: Fix MockableClientCirc for ClientCirc changesIan Jackson2023-05-231-3/+3
| | | | | | | | | | | | | | | | | | ClientCirc::begin_dir_stream now takes Arc<Self>. Method resolution rules mean that this code would just recurse, leading to a stack overflow.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-28 06:57:59 +0000