Per-package apparmor-profiles

Edit Package smar-apparmor-profiles

This project aims to have per-package AppArmor profiles, so that they can be automatically pulled when relevant package is installed to a system. This allows cluttering AppArmor with unnecessary profiles, and also allows easy blacklisting profiles one does not want.

A profile could still be temporary disabled with a symlink in /etc/apparmor.d/disable directory.

Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000402 402 Bytes
generate_spec.rb 0000015455 15.1 KB
main.yaml 0000000333 333 Bytes
packages-desktop.yaml 0000005359 5.23 KB
packages-devel.yaml 0000002193 2.14 KB
packages-games.yaml 0000000417 417 Bytes
packages-kde.yaml 0000010884 10.6 KB
packages-mail.yaml 0000001166 1.14 KB
packages-packaging.yaml 0000003335 3.26 KB
packages-productivity.yaml 0000001659 1.62 KB
packages-system.yaml 0000017083 16.7 KB
packages-text.yaml 0000000278 278 Bytes
packages.yaml 0000011254 11 KB
rpmlintrc 0000000071 71 Bytes
smar-apparmor-profiles.changes 0000040434 39.5 KB
smar-apparmor-profiles.spec 0000208927 204 KB
smar-apparmor-profiles.spec.in 0000015142 14.8 KB
systemd_override.rb 0000010503 10.3 KB
systemd_overrides.tar.xz 0000001708 1.67 KB
Revision 1420 (latest revision is 1432)
Samu Voutilainen's avatar Samu Voutilainen (Smar) committed (revision 1420)
trigger service run
Comments 0