summaryrefslogtreecommitdiff
path: root/crates/tor-guardmgr/Cargo.toml
Commit message (Collapse)AuthorAgeFilesLines
* Bump every crate by one patch version.Nick Mathewson2021-11-291-13/+13
|
* Move top-level configuration downwards from `arti` to `arti-config`.Nick Mathewson2021-11-181-0/+1
| | | | | | | | To do this at all neatly, I had to split out `tor-config` from `arti-config` again, and putting the lower level stuff (paths, builder errors) into tor-config. I also changed our use of derive_builder to always use a common error type, to avoid error type proliferation.
* Document that the "testing" feature is not semver-covered.Nick Mathewson2021-11-111-0/+3
|
* tor-circmgr: test ExitPathBuilder with guards.Nick Mathewson2021-11-021-0/+4
|
* Mark primary guards as retriable when we come back online.Nick Mathewson2021-11-021-0/+1
| | | | | | | | | | | | We define "coming back online" as happening when a guard attempt succeeds, if that attempt that was launched when we seemed to be offline. We define "seeming to be offline" as having all of our primary guards marked unreachable, and having received no incoming network traffic in a while. Closes #216.
* Bump all crate versions to 0.0.1Nick Mathewson2021-10-291-11/+11
|
* Tests for top-level GuardMgr.Nick Mathewson2021-10-071-0/+3
| | | | | | | Also, refactor our message handling to be more like the tor_proto reactors. The previous code had a bug where, once the stream of events was exhausted, we wouldn't actually get any more notifications.
* Initial tests for tor_guardmgr::guardNick Mathewson2021-10-071-0/+1
|
* Implement persistent state for guard mgrNick Mathewson2021-10-071-1/+1
|
* Initial backend implementation for guard node manager.Nick Mathewson2021-10-071-0/+32
There are some missing parts here (like persistence and tests) and some incorrect parts (I am 90% sure that the "exploratory circuit" flag is bogus). Also it is not integrated with the circuit manager code.