[tor-bugs] #14937 [Tor Browser]: Get meek working in Tor Circuit Display

[Tor Bug Tracker & Wiki]

#14937: Get meek working in Tor Circuit Display
--------------------------+------------------------------------------------
     Reporter:            |      Owner:  tbb-team
  arthuredelstein         |     Status:  needs_information
         Type:  defect    |  Milestone:
     Priority:  normal    |    Version:
    Component:  Tor       |   Keywords:  tbb-circuit-display, tbb-usability
  Browser                 |  Parent ID:
   Resolution:            |
Actual Points:            |
       Points:            |
--------------------------+------------------------------------------------

Comment (by arthuredelstein):

 Replying to [comment:8 dcf]:
 > Replying to [comment:5 arthuredelstein]:
 > > Thanks everyone for your help here. Sorry I wasn't very clear about my
 problem in the ticket description.
 > >
 > > For background, the tor circuit display works roughly as follows:
 > >
 > > 1. When a stream is created, get the ID for the circuit it is using.
 > > 2. Read a circut-status and extract the IDs for the nodes in the
 circuit we want to display.
 > > 3. Look up current bridges and if a node matches, then mark it as a
 bridge.
 > > 4. Get the IP address for each node using ns/id/* or the bridge conf
 line, if available.
 > > 5. Request the country code for each IP address.
 > > 6. Display the country and IP address for each node in the circuit, or
 the country and bridge type if it's a bridge.
 > >
 > > (I hope I've fixed the problem David observed in the vanilla bridges
 in my patch for #13882.)
 > >
 > > For meek, my problem is that I have neither an IP address nor a node
 ID. The bridge conf line provides two URLs (meek server and front), but
 the circuit-status shows a node ID for the meek bridge instead (such as
 `$A2C13B7DFCAB1CBF3A884B6EB99A98067AB6EF44~starman`). So is there a
 general way to identify this node ID as meek, and perhaps find a
 corresponding IP address?
 >
 > meek isn't doing anything differently in this respect than, say, obfs3.
 How does the circuit display show obfs3 bridges (not the default ones, but
 some from https://bridges.torproject.org/bridges?transport=obfs3)? I tried
 it just now and I got the same "Unknown country (IP unknown)". I think
 this problem exists for pluggable transports in general.

 As I mentioned, I think #13882 fixed this problem for most pluggable
 transports, including obfs3. To test it, you'll need to build the master
 branch of torbutton.git and install the xpi into Tor Browser. I just
 tested bridges from https://bridges.torproject.org/bridges?transport=obfs3
 and I get, for example "Sweden (Bridge: obfs3)". Most transports,
 including obfs3, have the IP address and fingerprint in the bridge conf
 line, so I'm just using that (in the latest patch). So my question is how
 to identify an entry-node fingerprint as a meek node, given that I don't
 have a fingerprint and IP from the bridge conf. Somehow, the meek code
 must be converting url/front into a fingerprint, correct?

 Thanks for your help, David!

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