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

Re: [tor-bugs] #30162 [Applications/Tor Browser]: Tor Browser bootstrap process got stuck after interrupting it

#30162: Tor Browser bootstrap process got stuck after interrupting it
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-mobile, tbb-8.5,                 |  Actual Points:
  TorBrowserTeam201905                           |
Parent ID:                                       |         Points:  0.5
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by eighthave):

 I totally agree with sisbell.  Now that I have the full stack prototype
 working for the new native Android ''TorService'', it is clear to me that
 we all should be moving away from daemons as fast as possible.  Managing
 them is really brittle and time consuming for devs.

 For example, ''TorService'' right now uses a UNIX socket for the
 ''ControlSocket'' then uses Linux ''inotify'' to watch for the
 ''ControlSocket'' and ''control_auth_cookie''.  When those are present,
 then it is clear that tor has started.  No unpacking assets, no timeouts,
 no port conflicts, etc.

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