Bug#761403: CAP_FOWNER

2015-05-04 Thread intrigeri
nusenu wrote (04 May 2015 14:47:13 GMT) : > (I'm testing with 0.2.5.12) I doubt that this change will make it into the 0.2.5 Debian package => IMO it's more useful to test with 0.2.6 from (currently) experimental. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subj

Bug#761403: CAP_FOWNER

2015-05-04 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Arto Jantunen: > With 0.2.6.7. Did you test both cases where /var/run/tor exists > and doesn't exist? If /var/run/tor doesn't exist + ControlSocket /var/run/tor/control in torrc tor does not start with and without CAP_FOWNER: [warn] Before Tor can

Bug#761403: CAP_FOWNER

2015-05-04 Thread Arto Jantunen
nusenu writes: >>> CapabilityBoundingSet: >>> >>> Since you add CAP_FOWNER (compared to upstream): What use cases >>> require it? >> >> CAP_FOWNER is required by "ControlSocket /var/run/tor/control". >> Tor chowns the control socket on startup (and fails to start if >> this does not succeed). > >

Bug#761403: CAP_FOWNER

2015-05-04 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 >> CapabilityBoundingSet: >> >> Since you add CAP_FOWNER (compared to upstream): What use cases >> require it? > > CAP_FOWNER is required by "ControlSocket /var/run/tor/control". > Tor chowns the control socket on startup (and fails to start if >

Bug#761403: CAP_FOWNER

2015-05-03 Thread Arto Jantunen
Hi, > CapabilityBoundingSet: > > Since you add CAP_FOWNER (compared to upstream): What use cases > require it? CAP_FOWNER is required by "ControlSocket /var/run/tor/control". Tor chowns the control socket on startup (and fails to start if this does not succeed). -- Arto Jantunen -- To UNSUBS