[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4b0c9925-d163-46a2-bbcb-74deb7446540@infradead.org>
Date: Fri, 17 Jul 2020 16:16:43 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Deven Bowers <deven.desai@...ux.microsoft.com>, agk@...hat.com,
axboe@...nel.dk, snitzer@...hat.com, jmorris@...ei.org,
serge@...lyn.com, zohar@...ux.ibm.com, viro@...iv.linux.org.uk,
paul@...l-moore.com, eparis@...hat.com, jannh@...gle.com,
dm-devel@...hat.com, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-block@...r.kernel.org,
linux-audit@...hat.com
Cc: tyhicks@...ux.microsoft.com, linux-kernel@...r.kernel.org,
corbet@....net, sashal@...nel.org,
jaskarankhurana@...ux.microsoft.com, mdsakib@...rosoft.com,
nramas@...ux.microsoft.com, pasha.tatshin@...een.com
Subject: Re: [RFC PATCH v4 02/12] security: add ipe lsm evaluation loop and
audit system
On 7/17/20 4:09 PM, Deven Bowers wrote:
> +config SECURITY_IPE_PERMISSIVE_SWITCH
> + bool "Enable the ability to switch IPE to permissive mode"
> + default y
> + help
> + This option enables two ways of switching IPE to permissive mode,
> + a sysctl (if enabled), `ipe.enforce`, or a kernel command line
> + parameter, `ipe.enforce`. If either of these are set to 0, files
is set
> + will be subject to IPE's policy, audit messages will be logged, but
> + the policy will not be enforced.
> +
> + If unsure, answer Y.
--
~Randy
Powered by blists - more mailing lists