#25672: Debugger in delevoper tools is fetching website over catch-all circuit
--------------------------------------+--------------------------
 Reporter:  gk                        |          Owner:  tbb-team
     Type:  defect                    |         Status:  new
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-linkability           |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------

Comment (by sysrqb):

 I should also mention
 https://trac.torproject.org/projects/tor/ticket/15599#comment:9 is another
 instance of this. I noticed this in my logs, too. An OCSP fetch should
 happen over the domain isolated circuit.

 {{{
 [04-11 00:04:30] Torbutton INFO: tor SOCKS: https://twitter.com/search-
 advanced via
                        --unknown--:71e69d27f4adff41fb754a6dc960dfeb
 [04-11 00:04:30] Torbutton INFO: controlPort >> 650 STREAM 51 NEW 0
 twitter.com:443 SOURCE_ADDR=127.0.0.1:46898 PURPOSE=USER
 [04-11 00:04:30] Torbutton INFO: controlPort >> 650 STREAM 51 SENTCONNECT
 36 twitter.com:443
 [04-11 00:04:30] Torbutton INFO: controlPort >> 650 STREAM 51 REMAP 36
 104.244.42.65:443 SOURCE=EXIT
 [04-11 00:04:30] Torbutton INFO: controlPort >> 650 STREAM 51 SUCCEEDED 36
 104.244.42.65:443
 [04-11 00:04:31] Torbutton INFO: tor SOCKS: http://ocsp.digicert.com/ via
                        --unknown--:71e69d27f4adff41fb754a6dc960dfeb
 [04-11 00:04:31] Torbutton INFO: controlPort >> 650 STREAM 52 NEW 0
 ocsp.digicert.com:80 SOURCE_ADDR=127.0.0.1:46900 PURPOSE=USER
 [04-11 00:04:31] Torbutton INFO: controlPort >> 650 STREAM 52 SENTCONNECT
 36 ocsp.digicert.com:80
 [04-11 00:04:31] Torbutton INFO: controlPort >> 650 STREAM 52 REMAP 36
 93.184.220.29:80 SOURCE=EXIT
 [04-11 00:04:31] Torbutton INFO: controlPort >> 650 STREAM 52 SUCCEEDED 36
 93.184.220.29:80
 [04-11 00:06:26] Torbutton INFO: controlPort >> 650 STREAM 52 CLOSED 36
 93.184.220.29:80 REASON=DONE
 [04-11 00:06:27] Torbutton INFO: controlPort >> 650 STREAM 51 CLOSED 36
 104.244.42.65:443 REASON=DONE
 }}}

 Considering how often it seems this occurs, I'm guessing plumbing the
 first party URI through the layers is more complicated than expected.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25672#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Reply via email to