mirrors/arti.git/crates/arti/src, branch arti-v1.2.4

arti: Note that auto is the same as disabled if vanguards are disabled.

2024-06-03T09:47:32Z

arti: Add vanguards settings to example config.

2024-06-03T09:47:32Z

RPC: Give error from RpcMgr::new if method name is sufficiently bad.

2024-05-14T13:49:44Z

(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:47Z

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: Use a slightly less awful workaround in socks.rs

2024-05-14T12:04:03Z

The problem was that Rust won't let us say ``` type ConnTarget = Arc; ``` because the R parameter wasn't used. Previously we solved this by using a macro instead of a type definition, which is ugly. I had been thinking previously I would need to declare some kind of additional wrapper type, and had shrunk from the verbosity. But @diziet pointed out that I could just use a 2-tuple unconditionally. It's still not beautiful, but it is less hideous than before.

Remove excess indentation from last commit.

2024-05-14T12:04:03Z

(This is a separate commit to make the branch more readable)

RPC: Refactor socks interpretation to remove stream id, add isolation.

2024-05-14T12:04:03Z

RPC: RpcDataStream type to act as a "stream-shaped hole"

2024-05-14T12:04:03Z

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 requests

2024-05-12T17:41:09Z

(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.

Merge branch 'new_ci_cfg_strategy' into 'main'

2024-05-07T12:24:58Z

add_warning/CI: New strategy to avoid "unexpected-cfgs" warning Closes #1395 See merge request tpo/core/arti!2129