[tor-bugs] #8641 [TorBrowserButton]: Create Browser UI indication for current circuit status and exit IP

[Tor Bug Tracker & Wiki]

#8641: Create Browser UI indication for current circuit status and exit IP
----------------------------------+-------------------------------
     Reporter:  mikeperry         |      Owner:  mikeperry
         Type:  enhancement       |     Status:  needs_information
     Priority:  major             |  Milestone:
    Component:  TorBrowserButton  |    Version:
   Resolution:                    |   Keywords:  tbb-usability
Actual Points:                    |  Parent ID:  #5752
       Points:                    |
----------------------------------+-------------------------------

Comment (by arthuredelstein):

 Replying to [comment:18 lunar]:
 > I don't think it's related to `IsolateDestPort` in any way. Relay exit
 policy:
 > {{{
 > accept *:443
 > reject *:*
 > }}}
 >
 > Page is at `https://www.example.org/`. It loads a resource from `https
 ://another-host.example.net:4242/`. The circuit that has been used to load
 the page cannot be used to fetch this resource. How does the patch you
 mentioned handle this?

 As it stands, my patch doesn't make any attempt to handle this situation.
 What does the latest version of TorBrowser do now? Presumably after my
 patch, the behavior would be the same.

 > I believe the correct behavior would be to use another circuit. Then it
 should be visible in the UI.

 Is that perhaps a little dangerous as it allows a site to automatically
 force clients to make requests through a particular exit node with a
 unique whitelisted port?

 But if that is the policy, then I agree we would need to show any
 additional circuits in the UI for extra third-party stuff.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8641#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online