On Thu, Dec 04, 2014 at 09:56:18AM +0100, intrigeri wrote: > If I remove that line, then the system Tor daemon fails to start here > with: > > [notice] Tor v0.2.5.10 (git-43a5f3d91e726291) running on Linux with Libevent > 2.0.21-stable, OpenSSL 1.0.1j and Zlib 1. > [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc". > [notice] Read configuration file "/etc/tor/torrc". > [warn] Error setting configured user: debian-tor not found > [warn] Failed to parse/validate config: Problem with User value. See logs for > details.
You're absolutely right, it now does that for me, too. I think I somehow failed to properly reload the new policy when I was testing, and it seemed to work (with the old policy still in place). Also, I should have dig into the Tor source code; it is obvious that Tor calls at least getpwnam(3). I think this bug can be closed; clearly nameservice is needed after all. Henrik BTW, thanks intrigeri for your work on AppArmor, it is much appreciated, and very important. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
