mirrors/arti.git/crates/arti/src/rpc.rs, branch arti-v1.2.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.72024-08-28T13:00:31Zrpc: Try using postage::watch to initialize ProxyInfo.2024-08-28T13:00:31ZNick Mathewsonnickm@torproject.org2024-08-27T17:16:15Zurn:sha1:ebbece794a2b11ff8d90af61be56a460d74255cd
(This is a bit trickier than I would like, but it ensures that we
never return a "not initialized yet" code.)
RPC: Add experimental method to list SOCKS proxies.2024-08-28T13:00:31ZNick Mathewsonnickm@torproject.org2024-08-22T14:38:33Zurn:sha1:5a79d84df763867ac5f22a81ddbc594ca0b7b939
We'll need this for our rpc-library code to meaningfully open SOCKS
connections.
Closes #1523.
arti: Define a new ArtiRpcSession type.2024-08-28T13:00:31ZNick Mathewsonnickm@torproject.org2024-08-22T12:46:32Zurn:sha1:657aa2e4d5dff83fadedec7a0be0e5413a27d8f3
This type exists in the `arti` crate. It wraps and delegates to
`arti_rpcserver::RpcSession`. Subsequent commits will use it to
expose information from the `arti` crate to the RPC system; right
now it does nothing.
RPC: Use RPC methods instead of the "ClientConnectionTarget" trait.2024-06-11T21:02:04ZNick Mathewsonnickm@torproject.org2024-06-04T17:22:30Zurn:sha1:c07455965fd201ec66631e649a10660e5955e47c
On its own, this might not seem like a huge improvement, but it will
later let us implement these RPC methods for types that can't
reasonably implement ClientConnectionTarget.
It also serves as a proof of concept that special-method invocation
can actually work, so that we can build things like this in cases
where introducing a trait isn't practical.
Closes #1427
RPC: Give error from RpcMgr::new if method name is sufficiently bad.2024-05-14T13:49:44ZNick Mathewsonnickm@torproject.org2024-05-14T13:46:02Zurn:sha1:9f50a947a9859535c02aa117fe1cd4fea4fff09b
(We don't give an error about unrecognized namespaces (for now),
since we have no way to opt in to them.)
RPC: Enforce method name format.2024-05-14T13:39:47ZNick Mathewsonnickm@torproject.org2024-05-14T13:35:19Zurn:sha1:8da4b96991c01ff16bd1194bca77d9bedf0bb9fa
We need to do this carefully, since we want our system to be
extensible with new namespaces.
First, when we are constructing an RpcMgr, we _warn_ about any
method names that are misformed.
Second, we add a test in the `arti` crate to fail if any method
names are invalid. This will only catch method names in crates that
`arti` depends on.
RPC: RpcDataStream type to act as a "stream-shaped hole"2024-05-14T12:04:03ZNick Mathewsonnickm@torproject.org2024-05-10T01:32:03Zurn:sha1:d014d60e9e5fe439846e4c05fdd8e73bfc67a1fd
The application creates these, using a new-stream-handle RPC command,
on an object that can actually create streams.
Then later, the application provides the (global) identity of one of
these objects when it's making a SOCKS connection. This causes the
object to take hold of a `DataStreamCtrl`.
TorClient: Slightly cleaner (?) interface for registering RPC methods.2024-05-06T13:12:08ZNick Mathewsonnickm@torproject.org2024-05-01T13:37:53Zurn:sha1:1bc4064c835edaf972716563bc35b27b37d10703RPC: Implement methods to get and watch client bootstrap status.2024-05-06T13:12:08ZNick Mathewsonnickm@torproject.org2024-04-25T14:10:04Zurn:sha1:7f9770aa50036d6c5ab01880a7f9e2dc0087364arpc: Give the session-creation function an argument.2023-06-15T15:50:12ZNick Mathewsonnickm@torproject.org2023-06-15T15:50:12Zurn:sha1:9e8ad5415edfa6d422b6b91375b6723ce9da5704
This will later let us tell the session-creation function
how the authentication occurred, which will let it decide
what privileges to provide.