| commit | 87f9b42179bd23418c3e698938bdeead56da1c43 | |
| author | Nick Mathewson <nickm@torproject.org> | |
| Wed, 30 Nov 2016 13:49:39 +0000 (30 08:49 -0500) | ||
| committer | Nick Mathewson <nickm@torproject.org> | |
| Fri, 16 Dec 2016 16:06:20 +0000 (16 11:06 -0500) | ||
| tree | 0d72e49c2c201b79dfc61003fb916b92264d1f3c | treesnapshot (tar.gz zip) |
| parent | 17c3faa2e393c59e9ee4aeca6986b0905d17f3b5 | commitdiff |
Implement support for per-circuit guard restrictions.
This is an important thing I hadn't considered when writing prop271:
sometimes you have to restrict what guard you use for a particular
circuit. Most frequently, that would be because you plan to use a
certain node as your exit, and so you can't choose that for your
guard.
This change means that the upgrade-waiting-circuits algorithm needs
a slight tweak too: circuit A cannot block circuit B from upgrading
if circuit B needs to follow a restriction that circuit A does not
follow.
This is an important thing I hadn't considered when writing prop271:
sometimes you have to restrict what guard you use for a particular
circuit. Most frequently, that would be because you plan to use a
certain node as your exit, and so you can't choose that for your
guard.
This change means that the upgrade-waiting-circuits algorithm needs
a slight tweak too: circuit A cannot block circuit B from upgrading
if circuit B needs to follow a restriction that circuit A does not
follow.