On Thu, Jul 9, 2015 at 11:44 AM, intrigeri intrig...@boum.org wrote:
Moritz Bartl wrote (09 Jul 2015 14:21:26 GMT) :
Just copy the /lib/systemd/system/tor.service file to
/etc/systemd/system and edit it there -- it will take precedence over
the one in /lib . You don't want to edit the one in
On 07/09/2015 03:24 PM, aexlfowley at web.de wrote:
Correct. I edited /lib/systemd/system/tor.service and added
ReadWriteDirectories=-/media/cRAID/Tor
and now 0.2.6.9 is running.
I'm not entirely sure how to create my own
/etc/systemd/system/tor.service so I leave it at that.
(Trying out
On Tue, 07 Jul 2015, aexlfowley at web.de wrote:
After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
(git-145b2587d1269af4) an error occured.
I'm on Debian Jessie (stable) on an AMD Athlon 64 X2. Tor won't start
and these are the last lines in log:
[warn] Couldn't open
Moritz Bartl wrote (09 Jul 2015 14:21:26 GMT) :
Just copy the /lib/systemd/system/tor.service file to
/etc/systemd/system and edit it there -- it will take precedence over
the one in /lib . You don't want to edit the one in /lib directly, since
it is meant to be for distribution files that
aexlfow...@web.de wrote (08 Jul 2015 17:57:24 GMT) :
(Both packages for 0.2.5.12 and 0.2.6.9 contain an apparmor profile.
Only change and new line is
/usr/bin/obfs4proxy PUx,
in /etc/apparmor.d/abstracions/tor)
FTR, the systemd unit file in Debian sid's 0.2.6.9-1 doesn't enable
the AppArmor
On 8 Jul 2015, at 08:06 , l.m ter.one.leeboi at hush.com wrote:
Sounds like access control gone wrong. An older version works but a newer
version fails. Permissions on the filesystem look fine from mount output. So
do you use access control, apparmor, selinux, grsecurity, fsprotect,
Sounds like access control gone wrong. An older version works but a
newer version fails. Permissions on the filesystem look fine from
mount output. So do you use access control, apparmor, selinux,
grsecurity, fsprotect, bilibop, etc? In particular the tor package
which is mentioned in your
Even for read-only filesystem, tor will attempt to fix folder
permission using chmod. I find it unusual that I don't see this in
your logs.
--leeroy
___
tor-dev mailing list
tor-dev@lists.torproject.org
On Tue, 07 Jul 2015, aexlfow...@web.de wrote:
After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
(git-145b2587d1269af4) an error occured.
I'm on Debian Jessie (stable) on an AMD Athlon 64 X2. Tor won't start
and these are the last lines in log:
[warn] Couldn't open
Hi devs,
User here. teor send me over from IRC. It's regarding to this
trac-ticket https://trac.torproject.org/projects/tor/ticket/16518
After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
(git-145b2587d1269af4) an error occured.
I'm on Debian Jessie (stable) on an AMD Athlon 64 X2.
Sounds like access control gone wrong. An older version works but a
newer version fails. Permissions on the filesystem look fine from
mount output. So do you use access control, apparmor, selinux,
grsecurity, fsprotect, bilibop, etc? In particular the tor package
which is mentioned in your ticket
On 8 Jul 2015, at 08:06 , l.m ter.one.lee...@hush.com wrote:
Sounds like access control gone wrong. An older version works but a newer
version fails. Permissions on the filesystem look fine from mount output. So
do you use access control, apparmor, selinux, grsecurity, fsprotect, bilibop,
12 matches
Mail list logo
