mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 13:13:44 +01:00
665baf5ed5
When the new path selection logic went into place, I accidentally dropped the code that considered the _family_ of the exit node when deciding if the guard was usable, and we didn't catch that during code review. This patch makes the guard_restriction_t code consider the exit family as well, and adds some (hopefully redundant) checks for the case where we lack a node_t for a guard but we have a bridge_info_t for it. Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2016-006 and CVE-2017-0377.
8 lines
359 B
Plaintext
8 lines
359 B
Plaintext
o Major bugfixes (path selection, security):
|
|
- When choosing which guard to use for a circuit, avoid the
|
|
exit's family along with the exit itself. Previously, the new
|
|
guard selection logic avoided the exit, but did not consider
|
|
its family. Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked
|
|
as TROVE-2016-006 and CVE-2017-0377.
|
|
|