[tor-bugs] #18305 [Tor Browser]: Tor fails to start with setgid

[Tor Bug Tracker & Wiki]

#18305: Tor fails to start with setgid
-------------------------+-----------------------------------
 Reporter:  commoc       |          Owner:
     Type:  defect       |         Status:  needs_information
 Priority:  Medium       |      Milestone:
Component:  Tor Browser  |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
  Sponsor:               |
-------------------------+-----------------------------------
Changes (by gk):

 * component:  Tor => Tor Browser


Comment:

 Replying to [comment:6 commoc]:
 > I don't have AppArmor.
 >
 > Using an out-of-the-box TorBrowser 5.0.7, I don't need to set
 LD_LIBRARY_PATH to start Tor directly, as seen below:
 >
 > user at debian:~/tor-browser_en-US-5.0.7/Browser/TorBrowser/Tor$ ./tor
 > Feb 12 19:02:46.557 [notice] Tor v0.2.7.6 (git-7a489a6389110120) running
 on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1k and Zlib 1.2.8.
 > Feb 12 19:02:46.557 [notice] Tor can't help you if you use it wrong!
 Learn how to be safe at
 https://www.torproject.org/download/download#warning
 > Feb 12 19:02:46.557 [notice] Configuration file
 "/home/ubuntu/install/etc/tor/torrc" not present, using reasonable
 defaults.
 > Feb 12 19:02:46.563 [notice] Opening Socks listener on 127.0.0.1:9050
 > Feb 12 19:02:46.000 [notice] Bootstrapped 0%: Starting
 > Feb 12 19:02:47.000 [notice] Bootstrapped 5%: Connecting to directory
 server
 >
 > It also works after performing my steps.
 >
 > But with an out-of-the-box TorBrowser 5.5, I need to set LD_LIBRARY_PATH
 before starting Tor directly (as seen in my comment:3).
 >
 > Since the Tor versions remained the same, I think the issue is caused by
 some change between Libevent 2.0.21 and 2.0.22. With this last version,
 apparently LD_LIBRARY_PATH is needed, and that's why Tor won't start with
 setgid.

 Well, I guess you have libevent (and other libs tor requires) installed on
 your computer (e.g. because of having a system tor running, too). And what
 happened so far was that Tor Browser silently fell back to that one which
 worked fine as this is 2.0.21. But that fallback does not work anymore as
 we now require 2.0.22. Could you test that theory?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18305#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online