[apparmor] Enabling AppArmor by default in Debian sprint: Oct. 23-27

intrigeri intrigeri at debian.org
Wed Oct 4 16:53:39 UTC 2017


Hi,

tl;dr: if *you* can put a few hours aside to help $subject happen
around Oct. 23-27, I will be immensely grateful and will gladly offer
$beverage next time we meet + will put aside a Tails t-shirt for you.

Wrt. the "enabling AppArmor by default in Debian" project/experiment,
I'll have a sprint on October 23-27. My focus will be to:

1. identify what still prevents us from starting the proposed
   experiment

2. fix all the problems identified in #1

3. document on the Debian BTS what must be fixed between the time we
   start the experiment and the time Debian decides what to do for the
   Buster release (i.e. keep AppArmor enabled or not by default)

After this we should be in a very good position to go ahead and press
the big red button :)

It's likely that I'll need a little bit of help from you folks for #2.

I do know I can count on cross-distro solidarity and on Debian
downstreams' good will, you folks have proven this countless times
already. But if some of you can put a couple hours aside for this
*during that specific week*, it would be amazing!

Selling point, if needed: I'm convinced this experiment will help
improve AppArmor policy and distro integration in a way that benefits
everyone here :)

I'm sorry I am too busy right now to identify and communicate what
kind of help I may need exactly, but most likely it'll be mostly in
the LTS distro maintenance and policy areas. I'm confident nothing
will be urgently needed kernel-side.

Cheers,
-- 
intrigeri



More information about the AppArmor mailing list