Re: [tor-bugs] #22283 [Applications/Tor Launcher]: Linux 7.0a4 broken after update: "Directory /run/user/$uid/Tor does not exist."

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#22283: Linux 7.0a4 broken after update: "Directory /run/user/$uid/Tor does not
exist."
---------------------------------------+-----------------------------------
 Reporter:  mcs                        |          Owner:  mcs
     Type:  defect                     |         Status:  needs_information
 Priority:  Medium                     |      Milestone:
Component:  Applications/Tor Launcher  |        Version:
 Severity:  Normal                     |     Resolution:
 Keywords:                             |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:
---------------------------------------+-----------------------------------

Comment (by gk):

 Replying to [comment:2 mcs]:
 > Replying to [comment:1 mcs]:
 > > To try to avoid removing torrc lines that the user may have added
 themselves, the code should check that the path in the ControlPort and
 SocksPort lines matches what Tor Launcher would use if it were configured
 to use Unix domain sockets by default.
 >
 > Because of the way the code is organized inside Tor Launcher, checking
 the path will be messier than Kathy and I would like. We can do it if
 necessary, but would it be acceptable to remove '''all''' of the Unix
 domain socket ControlPort and SocksPort lines if Tor Launcher is now using
 TCP for those things? The risk is that we would remove extra Unix domain
 socket ControlPort and SocksPort lines that were added by a user. But I
 suspect very few people have done that, and we could ensure that the extra
 cleanup we do would only affect alpha users.

 That's fine with me.

 > Another question: will 7.0a5 use Unix domain sockets by default or TCP?
 If the answer is Unix domain sockets, then we have another transition back
 from TCP to Unix domain sockets to worry about. I think we will be okay
 with the existing code in that case, except we will want to ensure that
 the "one time" (ha) torrc cleanup code runs a second time on the alpha
 channel.

 Why is that an issue? There are no `ControlPort` or `SocksPort` lines
 written to `torrc` anymore thanks to `__ControlPort` and `__SocksPort`
 being used. So, switching back and forth should be no problem anymore. Or
 are you envision some corner cases here due to the bug in the patch for
 #20761?

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