Differences between revisions 7 and 8
Revision 7 as of 2014-02-22 16:09:05
Size: 2291
Editor: ?IntRigeri
Comment: More links.
Revision 8 as of 2014-02-22 16:14:31
Size: 2393
Editor: ?IntRigeri
Comment: Actually link to the usertagged bugs.
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
 * '''Fix bugs''' tagged "new-profile".  * '''Fix bugs''' [[https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-aa-profiles-team@lists.alioth.debian.org|tagged "new-profile"]].

Infrastructure

Interacting with the team

Current status

Next 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

  • Test: ?enable AppArmor, enforce a bunch of profiles, report bugs and/or happiness.

  • Fix bugs tagged "new-profile".

  • 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.

  • 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.