Differences between revisions 23 and 25 (spanning 2 versions)
Revision 23 as of 2015-01-21 23:27:06
Size: 2706
Editor: UlrikeUhlig
Comment: link to new page about updateing profiles
Revision 25 as of 2015-01-22 22:34:10
Size: 2767
Editor: UlrikeUhlig
Comment: link to debug and bug report doc
Deletions are marked like this. Additions are marked like this.
Line 39: Line 39:
 * '''Test''': [[AppArmor/HowToUse|enable AppArmor]], enforce a bunch of profiles, report bugs and/or happiness.  * '''Test''': [[AppArmor/HowToUse|enable AppArmor]], enforce a bunch of profiles, [[AppArmor/Debug | test]], [[AppArmor/Reportbug | report bugs]] and/or happiness.
Line 43: Line 43:
 * '''Import''' profiles from Ubuntu: [[Contribute/Import|get the latest version, test, prepare Debian patch against apparmor-profiles-extra, submit patch to the BTS or push a branch to collab-maint]].  * '''Import''' profiles from Ubuntu: [[AppArmor/Contribute/Import|get the latest version, test, prepare Debian patch against apparmor-profiles-extra, submit patch to the BTS or push a branch to collab-maint]].


This page explains how to contribute to AppArmor in Debian.

Infrastructure

Interacting with the team

Current status

Goals

For Jessie, we'd like more enforced profiles; specifically (in decreasing order of priority):

  1. some of the Usual Suspects™ on the Desktop: evince, iceweasel, isc-dhcp-client, pidgin;
  2. some software that is particularly important in the context of Tails and other privacy-sensitive contexts: Tor, Vidalia;
  3. 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