Re: Let's enable AppArmor by default (why not?)
- To: debian-devel@lists.debian.org
- Subject: Re: Let's enable AppArmor by default (why not?)
- From: intrigeri <intrigeri@debian.org>
- Date: Sun, 05 Nov 2017 17:16:14 +0100
- Message-id: <[🔎] 85lgjkvgz5.fsf@boum.org>
- In-reply-to: <ff7330ca-d813-5497-84fb-dff0e709bd32@t-online.de> (Carsten Schoenert's message of "Tue, 31 Oct 2017 07:54:54 +0100")
- References: <857eyij4fb.fsf@boum.org> <fbb325ce-c21a-84f8-bece-d3e1696b66c7@debian.org> <ff7330ca-d813-5497-84fb-dff0e709bd32@t-online.de>
Hi,
Carsten Schoenert:
> Starting with this thread and by some talking to various people I
> changed my mind about this. For better flexibility and customizing,
> thinking about various releases (like *-security, *-backports e.g.) that
> need to be supported, I believe apparmor profiles for the applications
> should stay in the belonging source packages in most cases.
Fully agreed.
> Ubuntu is doing the opposite as far as I know [1], the time will show
> which way is batter.
FYI we're doing just like Ubuntu. I understand why you've been mislead
— you're definitely not the first one — and Ulrike has documented
where things are:
https://wiki.debian.org/AppArmor/Contribute/Upstream#Debian_.2F_Upstream_relationship
Cheers,
--
intrigeri
Reply to: