(If we decide to move tb-starter/etc/apparmor.d/usr.bin.torbrowser to apparmor-profile-torbrowser package, we should rename the file to /etc/apparmor.d/usr_bin_torbrowser or so to prevent dpkg upgrade issues.)
Please say how likely you find it for this to cause issues. There are various cases to consider.
Only tb-starter/etc/apparmor.d/usr.bin.torbrowser installed, but apparmor-profile-torbrowser package not.
Only tb-starter/etc/apparmor.d/usr.bin.torbrowser installed, and apparmor-profile-torbrowser installed and enforced.
Only tb-starter/etc/apparmor.d/usr.bin.torbrowser installed, and apparmor-profile-torbrowser installed and disabled.
Any others?
In none of these cases tb-starter/etc/apparmor.d/usr.bin.torbrowser should prevent /usr/bin/torbrowser from starting Tor Browser.
I think tb-starter/etc/apparmor.d/usr.bin.torbrowser is just too complex for installing it by default and enabling it by default. Because it interacts with msgcollector. And update-torbrowser. And worst, with software that we do not control, i.e. Tor Browser.
I do aggree with your last post. Iām currently trying to get tb-starter/etc/apparmor.d/usr.bin.torbrowser working, without success so far. Itās getting harder if we want to get it path insensitive, amongst other issues.
it looks like we are shooting our own foot for a minimal if not non-existing security gain. We would be much better off keeping apparmor-profile-torbrowser only, because the profiles relate to TBB only and can be adapted [relatively] easily. We have some experience with Tor browser changesā¦
In both firefox and start-tor-browser. It works too. Perhaps we should change the profile names, because it does not corespond the real path any longer. It could be
torbrower.Browser.firefox
torbrower.Browser.start-tor-browser
[Thatās the convention used in torbrowser-launcher]
I guess we must allow āenvironā. Regarding task, added a ādenyā line above the existing one already denying /proc/task/**.
A minor one: āTB_path/Browser.bakā popped once when updating to 5.0.4 with Tor browser internal updater (had put it aside an forgot it).
Had a look to TBB hardened on the Tor site, looks like there is only a 64 bit version available, for the time being (or forever?).
Was wondering about something elseā¦ Canāt we just declare somehow āTor Browser is free to read/write/anything within the whole Tor Browser folderā for simplified maintained?
Had a look to TBB hardened on the Tor site, looks like there is only a 64 bit version available, for the time being (or forever?).
Was wondering about something else... Can't we just declare somehow "Tor Browser is free to read/write/anything within the whole Tor Browser folder" for simplified maintained?
I have been wondering about that several times before, but did not dare pushing it. We can give all the required permissions (mrlwkix) to all the files in the Tor browser directory. It works (except when we have to run a child profile, but that's not the case here).
https://github.com/troubadoour/apparmor-profile-torbrowser/commit/4acb99d1a653628b4f8454f077df295062ec91e1