mirrors/arti.git/crates/tor-guardmgr/Cargo.toml, branch arti-v0.0.2 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.2 2021-11-29T20:21:58Z Bump every crate by one patch version. 2021-11-29T20:21:58Z Nick Mathewson nickm@torproject.org 2021-11-29T20:21:58Z urn:sha1:eef81d9d570572b7a57a76de4003721c546856de Move top-level configuration downwards from `arti` to `arti-config`. 2021-11-18T16:37:48Z Nick Mathewson nickm@torproject.org 2021-11-17T19:16:55Z urn:sha1:5184f5ba84d76b75022fe6249ba18fe42807b1aa 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. 2021-11-11T15:38:23Z Nick Mathewson nickm@torproject.org 2021-11-11T15:38:23Z urn:sha1:a9406796721d49885b3f98d756005b581b745c93 tor-circmgr: test ExitPathBuilder with guards. 2021-11-02T18:17:18Z Nick Mathewson nickm@torproject.org 2021-11-02T18:17:18Z urn:sha1:78fbb141be5ac3c51c1a8e44f7f4b50da9d713cd Mark primary guards as retriable when we come back online. 2021-11-02T16:17:11Z Nick Mathewson nickm@torproject.org 2021-11-01T20:06:41Z urn:sha1:876a569f6cdda44600263cc4f9553987d2022d92 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.1 2021-10-29T15:05:51Z Nick Mathewson nickm@torproject.org 2021-10-29T15:05:51Z urn:sha1:e6e740646ac61c9f06dc332cc156d4b20e793b70 Tests for top-level GuardMgr. 2021-10-07T16:09:29Z Nick Mathewson nickm@torproject.org 2021-10-06T21:19:32Z urn:sha1:00acc5c5b80ed000f14376734f41afb819bd27c4 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::guard 2021-10-07T14:45:42Z Nick Mathewson nickm@torproject.org 2021-09-29T20:35:24Z urn:sha1:0710fb2102d94cf0f58a94dedcc2bb888fc47750 Implement persistent state for guard mgr 2021-10-07T14:45:42Z Nick Mathewson nickm@torproject.org 2021-10-06T19:35:14Z urn:sha1:6cdce3dee6f38e894234fec11a4561803e573b76 Initial backend implementation for guard node manager. 2021-10-07T14:45:42Z Nick Mathewson nickm@torproject.org 2021-09-10T15:18:24Z urn:sha1:0779923d6474bb72427d19b2e504b3fd370b78a2 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.