Skip to content
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.

Empty consensus weights in consensus footer #21

Open
robgjansen opened this issue Dec 3, 2015 · 0 comments
Open

Empty consensus weights in consensus footer #21

robgjansen opened this issue Dec 3, 2015 · 0 comments
Labels

Comments

@robgjansen
Copy link
Member

When one of the positions has 0 bandwidth, which can happen in small Tor networks, Tor fails to produce weights in the consensus footer which causes it to default to an older path selection algorithm.

I proposed a fix in Tor here:
https://trac.torproject.org/projects/tor/ticket/14881

More info about this bug, see these mailing list threads:
http://mailman.cs.umn.edu/archives/shadow-support/2015-November/000462.html
http://mailman.cs.umn.edu/archives/shadow-support/2015-December/000465.html

As stated in the threads, if you use the strict flag assignment feature that I proposed in https://trac.torproject.org/projects/tor/ticket/14882 and was merged into Tor 0.2.7 stable, then we can set the flags properly to avoid running into this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant