-
- Downloads
circmgr: Use guard-manager's view of the fallbacks when possible.
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.
Showing
- crates/tor-circmgr/src/lib.rs 4 additions, 1 deletioncrates/tor-circmgr/src/lib.rs
- crates/tor-circmgr/src/path.rs 12 additions, 0 deletionscrates/tor-circmgr/src/path.rs
- crates/tor-circmgr/src/path/dirpath.rs 30 additions, 10 deletionscrates/tor-circmgr/src/path/dirpath.rs
- crates/tor-circmgr/src/path/exitpath.rs 3 additions, 3 deletionscrates/tor-circmgr/src/path/exitpath.rs
Please register or sign in to comment