intrigeri

Debian 10 (Buster) ships with AppArmor enabled by default. AppArmor is a Mandatory Access Control framework. When enabled, AppArmor confines programs according to a set of rules that specify what files a given program can access. This proactive approach helps protect the system against both known and unknown vulnerabilities. As any security measure that can block operations that would otherwise be allowed, this change has potential to occasionally break stuff and cause headaches. During this workshop, we will share skills about: * using Debian with AppArmor * identifying issues caused by incomplete AppArmor policy and reporting them * improving existing AppArmor policy * shipping AppArmor policy in Debian packages

Since November 2017, [AppArmor](https://wiki.debian.org/AppArmor) is enabled by default in Debian testing and sid. This [experiment]((https://lists.debian.org/debian-devel/2017/08/msg00090.html)) aims to gather data, so that we can decide whether we should enable AppArmor by default in Buster. # Share feedback We will share feedback about our experience with AppArmor, be it as users or contributors. I'm interested in hearing about: * General feelings. If you feel like it, we will try to understand where these feelings come from. * Technical issues. It's OK not to have filed a bug report yet :) * Raw data: did you disable AppArmor on your systems? When? # Share skills We will share AppArmor skills, tips and tricks we've learned along the way. Let's help each other! The notes of this session can be used later to: * Fix underlying technical issues we're working around with tips and tricks. * Fill holes in our documentation.

Other people: Clément Hermann