mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 13:13:44 +01:00
2d6914e391
In d1874b4339, we adjusted this check so that we insist on
using routerinfos for bridges. That's almost correct... but if we
have a bridge that is also a regular relay, then we should use
insist on its routerinfo when connecting to it as a bridge
(directly), and be willing to use its microdescriptor when
connecting to it elsewhere in our circuits.
This bug is a likely cause of some (all?) of the (exit_ei == NULL)
failures we've been seeing.
Fixes bug 25691; bugfix on 0.3.3.4-alpha
7 lines
305 B
Plaintext
7 lines
305 B
Plaintext
o Minor bugfixes (client):
|
|
- When using a listed relay as a bridge, and also using
|
|
microdescriptors, and considering that relay as a non-bridge in
|
|
a circuit, consider its microdescriptor as a valid source of information
|
|
about that relay. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
|
|
|