2495
Comment:
|
2498
|
Deletions are marked like this. | Additions are marked like this. |
Line 37: | Line 37: |
* '''Test''': [[AppArmor/HowTo|enable AppArmor]], enforce a bunch of profiles, report bugs and/or happiness. | * '''Test''': [[AppArmor/HowToUse|enable AppArmor]], enforce a bunch of profiles, report bugs and/or happiness. |
/Contribute /Contribute/FirstTimeProfileImport /Contribute/MergeProfileFromUpstream /Contribute/Upstream /Debug /HowToUse /OutReachyRound9 /Progress /Reportbug /UserStories |
Infrastructure
Interacting with the team
IRC: #apparmor on irc.oftc.net (general AppArmor discussion channel)
Current status
Debian Wheezy supports AppArmor.
See the progress tracking page.
Goals
For Jessie, we'd like more enforced profiles; specifically (in decreasing order of priority):
- some of the Usual Suspects™ on the Desktop: evince, iceweasel, isc-dhcp-client, pidgin;
- some software that is particularly important in the context of Tails and other privacy-sensitive contexts: Tor, Vidalia;
some low-hanging fruits from Ubuntu's Supported profiles in main list: apache2, libvirt, ntp...
The general workflow wrt. profiles is to find existing profiles, test them in the context of Debian sid, adapt them if needed, and either include them into apparmor-profiles-extra, or propose them to Debian package maintainers.
At some point, it would be great to share the profiles maintenance e.g. with Ubuntu.
How to help
Test: enable AppArmor, enforce a bunch of profiles, report bugs and/or happiness.
Fix usertagged bugs.
Fix bugs in the packages we maintain
Fix bugs in the apparmor package.
Import profiles from Ubuntu: get the latest version, test, prepare Debian patch against apparmor-profiles-extra, submit patch to the BTS or push a branch to collab-maint.
Documentation: write documentation about the user side of things.
Convince Ubuntu to upstream their AppArmor profiles to Debian.
Organize by keeping the progress tracking page up-to-date.