[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #12040 [Tor Launcher]: Please make a test connection to tor SOCKS port as part as Tor Launcher

#12040: Please make a test connection to tor SOCKS port as part as Tor Launcher
-------------------------+-------------------------------------------------
     Reporter:  lunar    |      Owner:  brade
         Type:           |     Status:  new
  enhancement            |  Milestone:
     Priority:  normal   |    Version:
    Component:  Tor      |   Keywords:  tbb-helpdesk-frequent tbb-usability
  Launcher               |  Parent ID:
   Resolution:           |
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------
Changes (by mcs):

 * cc: mcs, mikeperry (added)


Comment:

 So the scenario is that the browser can connect to 127.0.0.1:9151 (tor
 control port) but it is blocked from connecting to port 9150 (tor SOCKS)?
 That is surprising; I would expect both ports to be blocked or neither.
 Maybe the AV / firewalls are specifically blocking SOCKS but allowing
 other kinds of traffic.

 I am not exactly sure what we should do.  Tor Launcher does not currently
 concern itself with the SOCKS port.  If I remember correctly, Torbutton no
 longer does a remote check if it is able to do a local check (and the
 local check does not access anything over the SOCKS port).  We would
 rather not slow down the browser startup process by doing a remote check,
 but maybe there is a way to just check if communication to tor over the
 SOCKS port is working.

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