| commit | 73df82bd36a812496067c8bef948df5130cb991b | |
| author | Richard Pospesel <richard@torproject.org> | |
| Thu, 17 Oct 2019 21:40:40 +0000 (17 14:40 -0700) | ||
| committer | Georg Koppen <gk@torproject.org> | |
| Sat, 19 Oct 2019 20:59:00 +0000 (19 20:59 +0000) | ||
| tree | 9402ebe05841bd1beb8589f4601b21d5b3176ecb | treesnapshot (tar.gz zip) |
| parent | 324e8fd7f73c7f97f8174713c6a112ec75669e56 | commitdiff |
Bug 32125: Fix circuit display for bridge without a fingerprint
Torbutton expects all bridges to have a fingerprint when creating
the browser's circuit display. This patch works around the case
when the user provides a bridge without a fingerprint by assuming
it is a bridge, but we cannot determine the other displayed info:
type (obfs4, meek, etc) nor the ip.
In this scenario, the entry node in the circuit display will simply
say "Bridge".
Torbutton expects all bridges to have a fingerprint when creating
the browser's circuit display. This patch works around the case
when the user provides a bridge without a fingerprint by assuming
it is a bridge, but we cannot determine the other displayed info:
type (obfs4, meek, etc) nor the ip.
In this scenario, the entry node in the circuit display will simply
say "Bridge".
| chrome/content/tor-circuit-display.js | diffblobblamehistory | |
| modules/tor-control-port.js | diffblobblamehistory |