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
F3874930 DB130265 7C9EBBC7
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.torproject.org/pipermail/tor-dev/attachments/20150708/eaf53671/attachment-0001.html
-- next part --
A non-text attachment was scrubbed...
Name
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
I'm trying to use CollecTor data to find out how much bandwidth is
offered by different pluggable transports over time. I.e., I want to be
able to say something like, On July 1, bridges with obfs3 offered X MB/s,
bridges with obfs4 offered Y MB/s, etc. To do this, I'm mapping through
three types
On Wed, Jul 08, 2015 at 07:45:04PM -0700, David Fifield wrote:
I'm trying to use CollecTor data to find out how much bandwidth is
offered by different pluggable transports over time. I.e., I want to be
able to say something like, On July 1, bridges with obfs3 offered X MB/s,
bridges with obfs4
