Hello,
On 16/12/17 10:02, Carsten Schoenert wrote:
There is the AppArmor profile not re-enable? What let you came to that
conclusion? As written before two commands are needed.
$ sudo rm /etc/apparmor.d/disable/profile.name
$ sudo apparmor_parser -r /etc/apparmor.d/profile.name
It does work.
Until the next update, where /etc/apparmor.d/disable/profile.name will re-appear
(a deleted file in /etc in not considered a modified file by dpkg; hence the
file will be re-installed from the package and AppArmor disabled again; that's
what I tried to demonstrate with 'apt-get reinstall thunderbird')
Or even better, help to smash down the count of currently open bugs
about AppArmor issues in the Thunderbird profile!
https://github.com/cedric-dufour/custom-conf/blob/master/generic/all/custom-conf-thunderbird/usr/share/custom-conf-thunderbird/config/etc/apparmor.d/usr.bin.thunderbird
But it won't be of much help to most users.
I really don't believe one can come up with a profile that satisfies the entire
Debian users base and in the same time achieve what AppArmor is meant for.
not so typical environment, most the users are not in that category. And
all the big systems I know provide at least a configuration management
and/or create own packages for their users and machines.
I'll repackage thundebird and keep watching security updates closely to know
when I must re-package it.
When I do that for the 2900+ packages that makes our "Desktop" image, I'll
launch my own distribution :-)
But I'd rather stick and suport Debian for the time being (I even convinced my
boss to donate to the Debian Project from time to time). I might not be a
Debian Maintainer (I know I wouldn't be up to the task), but I do try to
contribute constructively (by sending patches or attempting to document the
source of problems as thoroughly as possible):
https://duckduckgo.com/?q=%22cedric.dufour%22+site%3Abugs.debian.org
You can close this bug.
Regards,
Cédric
