diff options
author | 2018-02-14 16:01:22 +0000 | |
---|---|---|
committer | 2018-02-19 15:56:11 +0000 | |
commit | 7b76763298ccb9e3f9bb58cf1741e55e802f75b7 (patch) | |
tree | d93013419d3ef978f0e92486f17f45755f75240b /mkdeb.sh | |
parent | enable apparmor for tranamission-gtk and transmission-qt (diff) | |
download | firejail-7b76763298ccb9e3f9bb58cf1741e55e802f75b7.tar.gz firejail-7b76763298ccb9e3f9bb58cf1741e55e802f75b7.tar.zst firejail-7b76763298ccb9e3f9bb58cf1741e55e802f75b7.zip |
Apparmor: don't duplicate userspace /run/user restrictions
Currently userspace firejail do blacklist approach to /run/user/ directory. By default it blacklist /run/user/**/systemd and /run/user/**/gnupg. Additional restrictions can be enabled in profiles like blacklisting /run/user/**/bus , etc. The blacklist can be extended or degraded by profile which allows for fine grained hardening.
In apparmor we do whitelist approach instead. It means we have to explicitly enable access to every file which firejail already allow access. This duplicates functionality and amount of work to do. Moreover we end up with same list of allowed files as every one of them is used by some app and appamror profile is global. It's even worse as firejail blacklist can be disabled with "writable-run-user" command which means we have to whitelist literally everything under /run/user/ to not cause breakages when using apparmor.
The solution for all above is to leave handling of /run/user to userspace firejail which is better tool to do this. In apparmor we should only handle things which firejail can't do.
Diffstat (limited to 'mkdeb.sh')
0 files changed, 0 insertions, 0 deletions