mirrors/arti.git/crates/tor-guardmgr/src/daemon.rs, branch arti-v1.1.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.32022-11-16T14:56:51ZGuardMgr: Add Instant to update().2022-11-16T14:56:51ZNick Mathewsonnickm@torproject.org2022-11-16T14:46:21Zurn:sha1:76a89fb178d747255e3b993ff2521e487b4db06f
This lets us avoid calling `Instant::now()`, when `Runtime::now()`
is what we want.
Unfortunately, there are a bunch of functions that called `update()`
that needed to change. Fortunately, none of the changes were very
complicated.
Fixes a `TODO pt-client` comment.
GuardMgr: Launch a background task to keep the list of bridge2022-11-08T13:10:15ZNick Mathewsonnickm@torproject.org2022-11-04T14:27:37Zurn:sha1:d395ae75a54c14e889b577e10869bb1ccd94bbd0
descriptors updated as appropriate.
GuardMgr: Exit keep-netdir-updated task early if GuardMgr disappears.2022-11-08T13:10:15ZNick Mathewsonnickm@torproject.org2022-11-04T14:24:11Zurn:sha1:e93ee142709c25a10d7d3964afd6f28e58fa7dddRefactor external guardmgr APIs: Stop taking NetDir arguments.2022-11-08T13:10:15ZNick Mathewsonnickm@torproject.org2022-11-02T17:54:00Zurn:sha1:95a95076a77f44478736464a6249bee345713ecc
These arguments were used only for legacy (testing) purposes; the
tests now use `TestNetDirProvider`. This lets us simplify our
internal logic for passing a `NetDir` to our samples, and prepare
for having a `BridgeSet` to pass there instead.
This is a breaking change to `guardmgr` and `circmgr`.
GuardMgr: Update to use new NetDirProvider API.2022-07-26T09:41:06ZNick Mathewsonnickm@torproject.org2022-07-25T15:56:10Zurn:sha1:0bca4d825cfa6995ce275b4113a48601e3fdb9dcMove responsibility for GuardMgr NetDir updates to GuardMgr.2022-06-07T15:44:51ZNick Mathewsonnickm@torproject.org2022-06-02T21:35:01Zurn:sha1:dc0a4e3c3d20bb6708a1e20df1c07a78041b6111
Previously it was the job of a task in CircMgr to do this; but we're
going to want to give GuardMgr full access to the latest NetDir for
this, and for other code-simplification reasons.
With this change I'm deprecating a couple of functions in
tor-circmgr. It's no longer necessary for us to have an artificial
external way for you to feed new NetDirs to a circmgr. (I could
just remove them, but I want practice deprecating.)
GuardMgr: record clock skew information.2022-04-07T15:33:34ZNick Mathewsonnickm@torproject.org2022-04-07T15:30:08Zurn:sha1:99146da2c2654c01259b8219bd491c5d4ac47039
(It is not yet actually used.)
Create and use API to report guard/fallback skew.2022-04-07T14:47:45ZNick Mathewsonnickm@torproject.org2022-04-06T13:05:35Zurn:sha1:c3c43b088e9f8dcbe876c277c3af14705244e8b0
(The information is not yet recorded.)
Refactor tor-guardmgr's inter-task communication.2021-11-02T15:19:57ZNick Mathewsonnickm@torproject.org2021-11-02T15:19:57Zurn:sha1:453855693b1d53a26fa8315f6d29a97b04cf8485
This is based on @eta's patches for !118 and !119: Since we already
have an unbounded channel, we don't need to use an elaborate mess of
one-shot senders. We can just use the unbounded_send() method,
which also lets us enqueue a message without having to await.
Closes #219.
Improve some documentation links2021-10-29T12:39:04ZNick Mathewsonnickm@torproject.org2021-10-29T12:39:04Zurn:sha1:1ee24ce6537373448d8fd5fb074768c6887cb90b
Instead of putting a fully qualified name in the text, in most cases
we should just use the short name of the type or function we're
referring to.
In other words, instead of saying [`crate::module::Foo`], we should
typically say [`Foo`](crate::module::Foo).