9782
Comment: update todo
|
10070
update todo and next meeting
|
Deletions are marked like this. | Additions are marked like this. |
Line 133: | Line 133: |
* Once the usertags are defined, announce workflow on blog and debian-devel [[https://lite5.framapad.org/p/dda| Draft]] | * --(Check udd script with pylint => done but ignored some bits)-- * Host udd.py script on Alioth in a git repository which is editable by the team * Once the usertags are defined, announce workflow on lbog and debian-devel [[https://lite5.framapad.org/p/dda| Draft]] |
Line 157: | Line 159: |
* Next meeting is the AppArmor upstream meeting on march 10th 2015 http://wiki.apparmor.net/index.php/MeetingAgenda 8pm UTC / 9pm CET |
/Contribute /Debug /HowToUse /OutReachyRound9 /Progress /Reportbug /UserStories |
This page tracks progress of adding AppArmor profiles to Debian.
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.
In progress
Profiles being worked on
Pending maintainer upload
Pending upload of apparmor-profiles-extra
Wishlist bug filed
See the bugs tagged "new-profile".
Reportbug should say if AppArmor (or any other LSM) is activated, filed as 773346
bugs.debian.org: Enable push/pull notifications for usertags 776587
702030 - automatically activate AppArmor in the kernel when one installs the apparmor package.
To be done
Supported profiles in Ubuntu main => import into apparmor-profiles-extra, unless the respective maintainers want to take it into their package. Maybe start with the high-profile services like Apache, OpenLDAP, ClamAV and Bind.
iceweasel => adapt Ubuntu's Firefox profile, or start over from intrigeri's current iceweasel profile
isc-dhcp-client => profile needs to be loaded before the network is up => see systemd item below
rsyslog => profile needs to be loaded before the service is started => see systemd item below
libvirt => libvirt 1.2.1-1 is built with AppArmor support (725144), but more work is probably needed. Felix Geyer volunteered to maintain the profiles.
Help get more profiles into good shape, so that they can be integrated upstream or into apparmor-profiles-extra. The Ubuntu security team roadmap tells a bit about their priority, and the current status of profiles under development.
Integrate with systemd by: waiting for systemd v210+, which has a ApparmorProfile= option, or ship upstart's /lib/init/apparmor-profile-load as an apparmor helper script and call it in systemd's ExecPreStart=
Done (for Jessie, at least)
Included in the corresponding package
mysql-5.5
Included in the apparmor-profiles package
The Community supported profiles are included in the apparmor-profiles package in complain mode.
Included in the apparmor-profiles-extra package
OutreachProgram Round 9
During the OutreachProgramForWomen, we will work on improving AppArmor support in Debian. You can follow up on progress here and on the dedicated blog.
TODO
Week1 Dec 9th - Dec 15th, 2014
Set up test environment and test different profiles
Read usertags documentation https://wiki.debian.org/bugs.debian.org/UserTags
Try to fix problematic profiles upstream: worked on Pidgin Blinklight https://code.launchpad.net/~u-d/apparmor-profiles/pidgin-blinklight/+merge/244582
Week2 & 3 Dec 16th - Dec 30th, 2014
re-add an ?AppArmor/HowTo page that redirects to AppArmor/HowToUse, so that old links still work
start writing the documentation: AppArmor/Contribute is for people who want to join us, and ?AppArmor/PackageMaintainers
explain upstream - Debian relationship
File a reportbug wishlist item: reportbug should say if AppArmor (or any other LSM) is activated => filed as 773346
Week4 Dec 31st - Jan 06th, 2015
import my upstream bugfixes on pidgin-blinkight to the apparmor-profiles-extra package through Git
roughly document how to contribute to the upstream profiles
set up user stories in order to define the usertags we need, so Debian users and maintainers know how we (want them to) use tags
Week5 & 6 Jan 07th - Jan 20th, 2015
fix out of sync README.Debian in apparmor-profiles-extra pkg
import How to contribute to Upstream doc to Debian Wiki: ?AppArmor/ContributeUpstream
Finish writing user stories
Ask for review of user stories and usertags on pkg-apparmor-team@l.a.d.o
Wait for review of usertag RFC
Re-elaborate User Stories based on review
fix pidgin profile (see email by intrigeri) about prefs.xml
Add "import profile" documentation to wiki ?AppArmor/Contribute/Import
See Craig's mails (psmisc maintainer) to review the ?process doc 771978
Week7 & 8 Jan 21st - Feb 3rd, 2015
File a wishlist bug against bugs.debian.org for push/pull notifications for usertags, this is now 776587
Move debugging documentation to its own page
Add d.w.o documentation as a link to http://wiki.apparmor.net/index.php/Distro_debian (was there already)
Discuss & document when "Suggests: apparmor" needs to have a version number or Breaks:
move user stories to dedicated page AppArmor/UserStories
link User stories from the Tools section on AA/Contribute
Follow-up on new-profile tagged bugs
Found a small bug in aa-unconfined which has been patched by upstream devs, filed as 777034
Work on AppArmor/Debug and AppArmor/Reportbug
Work on wiki documentation navigation: make pages easy to access and things easy to find
Week9 & 10 Feb 4th - Feb 17th, 2015
implement each userstories-derived solution on the corresponding wiki page
finish wiki navigation and ask for review again
Usertag blog post http://apparmor.451f.org/2015/02/11/user-stories-and-user-tags)--
--(Code usertag email notification via UDD and add it as a cronjob on alioth
Week11 - 13 Feb 18th - Mar 9th, 2015
Document branch name for contributing to upstream bzr repository on blog post / how to contribute to upstream doc
create list of package maintainers who already ship AppArmor profiles.
Contact package maintainers who already ship AppArmor profiles. Tell them how to contact the Debian AppArmor packaging team if they experience problems or have any questions. Draft, maintainer list
Check udd script with pylint => done but ignored some bits
- Host udd.py script on Alioth in a git repository which is editable by the team
Once the usertags are defined, announce workflow on lbog and debian-devel Draft
- import my upstream bugfixes on pidgin-prefs to the apparmor-profiles-extra package through Git
Fix 702030 - automatically activate AppArmor in the kernel when one installs the apparmor package.
- Write a final report
After the internship
- Document "Migrate a profile to the package that ships the confined application" on AppArmor/Contribute/ImportProfileFromExtra
Notes
OPW Coordination meetings
Meetings take place on irc.oftc.net and are recorded by MeetBot.
- dec 12th 2014, 4pm CET (private place)
Next meeting is the AppArmor upstream meeting on march 10th 2015 http://wiki.apparmor.net/index.php/MeetingAgenda 8pm UTC / 9pm CET