Differences between revisions 22 and 24 (spanning 2 versions)
Revision 22 as of 2015-01-21 23:20:14
Size: 2800
Editor: UlrikeUhlig
Comment:
Revision 24 as of 2015-01-22 16:39:57
Size: 2715
Editor: UlrikeUhlig
Comment: correct link
Deletions are marked like this. Additions are marked like this.
Line 43: Line 43:
 * '''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. [[https://apparmor.451f.org/2015/01/10/updating-a-profile-in-debians-apparmor-profiles-extra-package/|Quick howto]]  * '''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