Hi,
Those AppArmor policy changes fixed the issue. If you still want to see
the kernel message anyway, here it is:
Sep 15 13:20:05 bolin kernel: [15363.513255] audit: type=1400
audit(1410805205.021:326): apparmor="DENIED" operation="file_mprotect"
profile="/home/*/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/{Browser/,}start-tor-browser"
name="/bin/dash" pid=7495 comm="start-tor-brows" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=0
Thanks for the quick response, this should be fixed once these changes
make their way into the next package update.
--
Alex Griffin
On 2014-09-15 16:59, intrigeri wrote:
Hi again,
intrigeri wrote (15 Sep 2014 16:29:58 GMT) :
I've locally updated the profiles a bit yesterday, and will propose an
update upstream shortly; I suspect this is the culprit. May you please
send us the kernel logs you get about AppArmor denials, in order to
allow me to confirm this?
Also, it would be great if you could (please) test the updated
AppArmor profiles I've just submitted upstream:
https://github.com/micahflee/torbrowser-launcher/pull/133
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
