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, 06 Aug 2017 11:13:19 -0400
Message-id: <[🔎] 857eygsp9s.fsf@boum.org>
In-reply-to: <[🔎] 20170806072808.GD14425@spark.dtdns.net> (Bas Wijnen's message of "Sun, 6 Aug 2017 07:28:08 +0000")
References: <[🔎] 857eyij4fb.fsf@boum.org> <[🔎] 1501949819@msgid.manchmal.in-ulm.de> <[🔎] 20170806072808.GD14425@spark.dtdns.net>

Dr. Bas Wijnen:
> Enabling it by default doesn't mean it can't be switched off, right?

Yes, passing apparmor=0 on the kernel command line will turn it off.

Cheers,
-- 
intrigeri

Reply to:

References:
- Let's enable AppArmor by default (why not?)
  - From: intrigeri <intrigeri@debian.org>
- Re: Let's enable AppArmor by default (why not?)
  - From: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
- Re: Let's enable AppArmor by default (why not?)
  - From: "Dr. Bas Wijnen" <wijnen@debian.org>

Prev by Date: Bug#870913: marked as done (general: IPv6 tunnel on host machine and container)
Next by Date: Re: sse{2,3,4.2}, altivec, neon, ...
Previous by thread: Re: Let's enable AppArmor by default (why not?)
Next by thread: Re: Let's enable AppArmor by default (why not?)
Index(es):
- Date
- Thread