5

In your torrc there is the line ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy --managed Furthermoer the log file states: Jun 08 21:33:05.000 [warn] Could not launch managed proxy executable at '/usr/bin/obfs4proxy' ('Operation not permitted'). According to the manpage of obfs4proxy there is no option --managed. This was used for obfsproxy. So if ...


3

This is a restriction put in place by AppArmor to confine Tor Browser, as such cannot open files in the users home directory or mounted media except where explicitly excepted. For this purpose, there are two folders that can be accessed in the users home directory, defined by these rules in /etc/apparmor.d/torbrowser: owner "@{HOME}/Tor Browser/" rw, ...


3

The "owner" conditional, as per the AppArmor wiki: The owner keyword is used to make the rule conditional on object ownership. Specifically the task must have the same euid/fsuid as the object being referenced by the permission check. The problem seems to be that the user that tor is running as (debian-tor is the default on ubuntu and other debian ...


2

You could fix your problem with apparmor like this: First open /etc/apparmor.d/abstractions/tor with your favorite editor (with root user) sudo gedit /etc/apparmor.d/abstractions/tor Then change the /usr/bin/obfs4proxy PUx, to /usr/bin/obfs4proxy ix, and save it! And after that reboot


Only top voted, non community-wiki answers of a minimum length are eligible