[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201706062336.CFE35913.OFFLQOHMtSJFVO@I-love.SAKURA.ne.jp>
Date: Tue, 6 Jun 2017 23:36:07 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: igor.stoppa@...wei.com, casey@...aufler-ca.com, keescook@...omium.org,
mhocko@...nel.org, jmorris@...ei.org
Cc: paul@...l-moore.com, sds@...ho.nsa.gov, hch@...radead.org,
labbott@...hat.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH 4/5] Make LSM Writable Hooks a command line option
Igor Stoppa wrote:
> For the case at hand, would it work if there was a non-API call that you
> could use until the API is properly expanded?
Kernel command line switching (i.e. this patch) is fine for my use cases.
SELinux folks might want
-static int security_debug;
+static int security_debug = IS_ENABLED(CONFIG_SECURITY_SELINUX_DISABLE);
so that those who are using SELINUX=disabled in /etc/selinux/config won't
get oops upon boot by default. If "unlock the pool" were available,
SELINUX=enforcing users would be happy. Maybe two modes for rw/ro transition helps.
oneway rw -> ro transition mode: can't be made rw again by calling "unlock the pool" API
twoway rw <-> ro transition mode: can be made rw again by calling "unlock the pool" API
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
