mirrors/arti.git - mirror of https://gitlab.torproject.org/tpo/core/arti

	Commit message (Collapse)	Author	Age	Files	Lines
*	BridgeConfigBuilder: Introduce the struct with the dictionary repr	Ian Jackson	2022-11-21	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	This struct is going to be the principal "dictionary-style" serde representation for a bridge, and the builder, making this all in keeping with our usual approach. In this commit: * Introduce the struct (defining the serialisation) * Provide the setters (defining the Rust API) * Add success test cases (not all of the data in which is used yet)
*	GuardMgr: Remove TODO to move `mod bridge` to another crate	Nick Mathewson	2022-11-10	1	-3/+0
\| \| \| \|	The code seems happy enough here for now.
*	GuardMgr: Pass correct universe to "Bridges" `GuardSet`.	Nick Mathewson	2022-11-08	1	-0/+2
\| \| \| \| \| \|	This can probably be done in a simpler way, but for the moment I would prefer to try to minimize the amount of code I'm changing here.
*	tor-guardmgr: bridges: export BridgeDescError at toplevel	Ian Jackson	2022-10-27	1	-1/+1
\|
*	struct BridgeConfig: Rename from Bridge	Ian Jackson	2022-10-12	1	-1/+1
\| \| \| \|	Fixes #599
*	tor-guardmgr: Export BridgeParseError from toplevel	Ian Jackson	2022-10-12	1	-1/+1
\| \| \| \| \|	Callers could `use` it as `tor_guardmgr::config::BridgeParseError` but it seems unecessary to force them to.
*	Start on a new BridgeRelay type.	Nick Mathewson	2022-10-04	1	-1/+3
\| \| \| \| \| \| \| \|	This is the one we'll actually use to connect to bridges. It has a `Bridge` line, and an optional `BridgeDesc`. Maybe this will turn into a `BridgeRelay<'a>` by analogy to `Relay` some time; I'm not sure.
*	GuardMgr/DirMgr: Add APIs for bridge descriptor lists	Nick Mathewson	2022-09-26	1	-1/+3
\|
*	A basic configuration type for a bridge.	Nick Mathewson	2022-09-26	1	-0/+15
	This type goes in tor-guardmgr, since that's where decisions about circuits' first hops are made. There are a lot of "todo"s here for us to resolve.