Per-package 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.
-
Checkout Package
osc checkout AppArmor/smar-apparmor-profiles && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_service | 0000000402 402 Bytes | |
_service:obs_scm:smar-apparmor-profiles-1690275321 |
0001195020 1.14 MB | |
_service:obs_scm:smar-apparmor-profiles.obsinfo | 0000000124 124 Bytes | |
generate_spec.rb | 0000014123 13.8 KB | |
main.yaml | 0000000231 231 Bytes | |
packages-kde.yaml | 0000008338 8.14 KB | |
packages-mail.yaml | 0000001166 1.14 KB | |
packages-productivity.yaml | 0000000609 609 Bytes | |
packages-system.yaml | 0000010643 10.4 KB | |
packages-text.yaml | 0000000278 278 Bytes | |
packages.yaml | 0000015673 15.3 KB | |
rpmlintrc | 0000000071 71 Bytes | |
smar-apparmor-profiles.changes | 0000008061 7.87 KB | |
smar-apparmor-profiles.spec | 0000148449 145 KB | |
smar-apparmor-profiles.spec.in | 0000010712 10.5 KB | |
systemd_overrides.tar.xz | 0000001196 1.17 KB |
Revision 128 (latest revision is 1432)
Samu Voutilainen (Smar)
committed
(revision 128)
trigger service run
Comments 0