mirrors/arti.git/crates/tor-circmgr/src/path, branch arti-v0.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.02022-03-30T14:40:14ZDirPathBuilder::pick_path: re-order match cases for clarity.2022-03-30T14:40:14ZNick Mathewsonnickm@torproject.org2022-03-29T12:39:04Zurn:sha1:951b800988ee00048be36a9abf5bcf60eeb19f96circmgr: Use guard-manager's view of the fallbacks when possible.2022-03-30T14:39:09ZNick Mathewsonnickm@torproject.org2022-03-25T20:56:26Zurn:sha1:ed6389acc7c872854984ae1ea38dbda6542f48cb
If we're building a path with the guard manager involved, we now ask
the guard manager to pick our first hop no matter what. We only
pick from the fallback list ourselves if we're using the API with no
guard manager.
This causes some follow-on changes where we have to remember an
OwnedChanTarget object in a TorPath we've built, and where we gain
the ability to say we're building a path "from nothing extra at
all." Those are all internal to the crate, though.
Closes #220, by making sure that we use our guards to get a fresh
netdir (if we can) before falling back to any fallbacks, even if our
consensus is old.
Compilation should be fixed in the next commit.
Turn FallbackList into a real type, and store one in GuardMgr.2022-03-30T14:39:06ZNick Mathewsonnickm@torproject.org2022-03-25T20:44:12Zurn:sha1:9da43189f36b19681d10b78ef982c52c929b4573
The guard manager is responsible for handing out the first hops of
tor circuits, keeping track of their successes and failures, and
remembering their states. Given that, it makes sense to store this
information here. It is not yet used; I'll be fixing that in
upcoming commits.
Arguably, this information no longer belongs in the directory
manager: I've added a todo about moving it.
This commit will break compilation on its own in a couple of places;
subsequent commits will fix it up.
Move fallback.rs into guardmgr.2022-03-30T14:34:48ZNick Mathewsonnickm@torproject.org2022-03-25T17:38:01Zurn:sha1:80b65c3a4d4108c6b4b0cb91722f89c8e5859b7d
This is the logical place for it, I think: the GuardMgr's job is to
pick the first hop for a circuit depending on remembered status for
possible first hops. Making this change will let us streamline the
code that interacts with these objects.
Remove allow(clippy::disallowed_methods) lint.2022-03-30T12:55:58ZNick Mathewsonnickm@torproject.org2022-03-30T12:55:58Zurn:sha1:700e491813f84d76446193aef7121a329b774717Merge branch 'no-system-time' into 'main'2022-03-30T12:44:25Zetator@eta.st2022-03-30T12:44:25Zurn:sha1:fd081742fa13e8464ad46123d83617165587d4f4
Don't use SystemTime::now()
Closes #306
See merge request tpo/core/arti!365circmgr: Change API for using FallbackDirs2022-03-21T13:06:32ZNick Mathewsonnickm@torproject.org2022-03-17T13:33:47Zurn:sha1:d778a922255a75e36baa5296451e9982045ac777
It'll soon more convenient to pass in FallbackDirs as a slice of
references, rather than just a slice of FallbackDirs: I'm going to
be changing how we handle these in tor-dirmgr.
use wallclock where possible in tests2022-02-25T23:33:44Ztrinity-1686atrinity@deuxfleurs.fr2022-02-25T23:33:44Zurn:sha1:f06b25601006ba42c427349837dca6d5634bc718fix tests2022-02-25T19:45:16Ztrinity-1686atrinity@deuxfleurs.fr2022-02-25T19:42:58Zurn:sha1:96daba774768548cb40d88d619feeb9f39865b4aremove most usage of SystemTime::now2022-02-25T19:34:27Ztrinity-1686atrinity@deuxfleurs.fr2022-02-25T19:34:27Zurn:sha1:f9a4f23e8345f1f51e002433e83cda66129118cf