mirrors/arti.git/crates/arti-client/src/client.rs, branch arti-v1.2.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.52024-06-11T21:02:04ZRPC: 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
arti-client: Unconditionally retire all HS circuits if circmgr says so.2024-06-03T14:28:23ZGabi Moldovangabi@gotpcrel.net2024-06-03T13:01:46Zurn:sha1:0c96190b5035713ee301e6ef43fe4cf1040f608d
If the circmgr retires all of its circuits, so should the HS circ pool.
The circuits can be retired for various reasons (for example, if the
configured vanguard mode changes).
arti-client: Add TODO about always clearing the HS circ pool.2024-06-03T14:28:23ZGabriela Moldovangabi@torproject.org2024-05-23T16:49:40Zurn:sha1:936e23fd3fd3986c7c1d2bdeb5c9e45a0baa58f9tor-circmgr: Remove VanguardMode from Pool (fmt).2024-06-03T14:28:22ZGabriela Moldovangabi@torproject.org2024-05-23T16:40:51Zurn:sha1:2deb0b5df8c7d7e14ab151781b3f3b30180aa210tor-circmgr: Remove VanguardMode from Pool.2024-06-03T14:19:24ZGabriela Moldovangabi@torproject.org2024-05-23T16:38:33Zurn:sha1:d75f136e506e474274529e4d0fee742d5b5d9011
Storing the VanguardMode in multiple places (in the VanguardMgr *and*
the HS circ Pool) is dangerous and can lead to split brain situations
where different parts of the code think they are running in different
VanguardModes.
See #1424
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`.
RPC: Add a trait that can be the target of SOCKS requests2024-05-12T17:41:09ZNick Mathewsonnickm@torproject.org2024-05-09T22:54:39Zurn:sha1:a20973afe602d5977fd686f6e005c13a1e9d5100
(These will later become objects that can receive any application
request, once we have HTTP connect.)
For now, Session and TorClient implement this trait;
but soon there will be a new type to hold on to the created
DataStreamCtrl.
There are some XXXXs here, marking code that is too ugly to live.
I should fix it before I merge this branch.
rpc: Mark TorClient as exposed outside of session2024-05-09T20:34:17ZNick Mathewsonnickm@torproject.org2024-05-06T18:16:39Zurn:sha1:d1c42ba7c22c6a06111f6744d522f03d0ac1e1baarti-client: add hs_circ_pool() method on TorClient2024-04-15T18:23:38ZRichard Pospeselrichard@torproject.org2024-04-07T21:21:10Zurn:sha1:b8b1cb6ea08f4cba7f06e2df1e2b62f42a026983Port many of the macros in tor-rpcbase to use derive-deftly.2024-04-04T20:42:57ZNick Mathewsonnickm@torproject.org2024-04-04T20:04:39Zurn:sha1:66cfabc442bfc1779a4748b89d0be2d51f908fc9
This simplifies our implementation logic in a few places,
and simplifies our invocation syntax greatly. There are a few
infelicities, noted in `TODO RPC` comments.