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

Re: [tor-bugs] #20111 [Applications/Tor Browser]: use Unix domain sockets for SOCKS port by default



#20111: use Unix domain sockets for SOCKS port by default
-------------------------------------------------+-------------------------
 Reporter:  mcs                                  |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:
                                                 |  needs_revision
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-torbutton, tbb-security, tbb-    |  Actual Points:
  sandboxing, TorBrowserTeam201610               |
Parent ID:  #14270                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by gk):

 Replying to [comment:26 mcs]:
 > Replying to [comment:25 gk]:
 > > That said I tested the patches again with the proposed fix for bug
 1311044 and there is not shutdown hang anymore. However, seeing all the
 output after `tor` is supposedly shut down still makes me nervous. I think
 we should have the behavior we currently have in this regard (at least it
 seems to me we have it that way at the moment): first no traffic anymore,
 then `tor` gets shut down and then the browser goes away.
 >
 > This is not new behavior. We were able to reproduce it using TB 6.5a3
 when running with TCP control and SOCKS ports. I will attach a log.
 >
 > It surprises me that Firefox does not cancel all network activity as a
 browser tab is closed, but maybe that hurts performance. I don't think any
 harm is done in this case because, even though the catch all circuit would
 be used, there is no tor to talk to any more. But I wonder if this same
 situation can happen when closing a window or tab without exiting the
 browser. Probably we should open a new ticket for this issue.

 Woah, that was news to me. I actually am seeing this behavior for the
 first time. I opened #20411.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20111#comment:29>
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