mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks 2023-07-21T09:48:16Z 2023-07-21T09:48:16Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-21T09:48:16Z urn:sha1:cfbff212d413a6ad06542aa5c489b9037c49a983 2023-07-20T15:42:03Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-20T15:41:24Z urn:sha1:b5e6af9f5c7b31990689e735fb0704c8328b4b0e It's a bit of a wart that tor-ptmgr calls these "protocols" and tor-guardmgr calls these "transport names". 2023-07-03T17:00:25Z Nick Mathewson nickm@torproject.org 2023-07-03T16:51:06Z urn:sha1:19b1d3bba58a95934fce5230a75f0adbbef1cf95 This tries to flesh out some of the details for users who may be new to bridges and PTs. Closes #706. 2022-11-28T18:52:21Z eta tor@eta.st 2022-11-22T16:24:15Z urn:sha1:3b41c78d6fc5eceac3b45ea9ef1540b72f9b4004 This commit implements `PtMgr`, a pluggable transport manager responsible for keeping track of spawned PTs and spawning them to satisfy client requests on demand. It does this in two parts: the `PtMgr` type exported to the rest of the code, and the background `PtReactor` that actually does the spawning; this design ensures that only one attempt to spawn a PT is active at a time, and will prove useful later for implementing e.g. timeouts. A few changes were necessary to the rest of the code in order to make this all work out. Namely: - `TransportRegistry`'s API didn't make any sense for two reasons: - It wasn't feasible for implementors to implement `ChannelFactory`, since that'd require constructing a `ChanBuilder` (which requires a bootstrap reporting event sender). - Treating the PT manager as a registry is over-general; it's only necessary for it to spawn pluggable transports, so saddling it with other concerns didn't make any sense. - (It's possible to get extensibility for arbitrary user customization by just letting the user swap in a new `ChannelFactory`, anyway.) - Therefore, the `PtMgr` implements the new `AbstractPtMgr` trait, which is far more narrowly focused; this only exists to solve a dependency loop, and is documented as such. - This provides a `TransportHelper` instead of a `ChannelFactory`. 2022-11-16T11:39:25Z eta tor@eta.st 2022-11-03T14:36:31Z urn:sha1:1c9f6fb179bc88b77079026f249eb3e1678617ca This brings the draft configuration mechanisms in tor-ptmgr in line with the config in other crates, using builders. It also plumbs the config type through into the main `arti-client` config, and adds some example lines to `arti-example-config.toml`. 2022-09-23T18:08:53Z Nick Mathewson nickm@torproject.org 2022-09-23T18:05:39Z urn:sha1:52ca64fe0da14f7670f61949e94c1dab444c73bb 2022-09-23T18:08:24Z Nick Mathewson nickm@torproject.org 2022-09-23T13:47:30Z urn:sha1:e412d7400ceb3cee1b0a29253fcf13995c21108f When complete, this crate will handle launching and using pluggable transports on demand.