aboutsummaryrefslogtreecommitdiff
path: root/crates/tor-guardmgr/src/bridge/config.rs
Commit message (Collapse)AuthorAgeFilesLines
...
* tor-guardmgr: Fix build without pt-client featureIan Jackson2022-10-111-1/+3
|
* Implement HasRelayIds for Bridge.Nick Mathewson2022-10-041-1/+11
|
* pt: bridge line parsing: overhaul errorsIan Jackson2022-10-031-36/+107
| | | | | | | | | | | | | Include the offending word in all the applicable errors. Always print it with {word:?}. As a consequence, there are no From impls any more and error generation/conversion is by hand in all cases. Clarify InvalidPtOrAddr vs InvalidIAddrorPt, and don't make the attempted parse be a source error for those. Where we still have source errors, don't print them in Display.
* pt: Check PT key=value syntaxIan Jackson2022-10-031-3/+0
| | | | | This is not perfect but it at least ensures that our own parsing and printing code works correctly with all the values we accept.
* pt: Make PtTarget::push_setting fallible, and take IntoIan Jackson2022-10-031-3/+8
| | | | | | It has its own error type PtTargetInvalidSetting. In check_doc_features, adjust suppression to new code.
* pt: bridge line parsing: Add commentaryIan Jackson2022-10-031-0/+26
|
* pt: Document Bridge line syntaxIan Jackson2022-10-031-0/+31
|
* pt: bridge parsing: Add an IPv6 test caseIan Jackson2022-09-301-0/+12
|
* pt: impl Display for Bridge and test itIan Jackson2022-09-301-0/+43
|
* implement FromStr for Bridge, and test itIan Jackson2022-09-301-0/+327
|
* pt: Make some more types EqIan Jackson2022-09-301-1/+1
| | | | I wanted this for testing. I think it's reasonable to promise this.
* A basic configuration type for a bridge.Nick Mathewson2022-09-261-0/+41
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.