[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c4baf092a11eadfc589ca2a314bcbf689284b0a.camel@linux.ibm.com>
Date: Tue, 27 Apr 2021 12:48:00 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Casey Schaufler <casey@...aufler-ca.com>,
Roberto Sassu <roberto.sassu@...wei.com>,
"mjg59@...gle.com" <mjg59@...gle.com>
Cc: "linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 04/11] ima: Move ima_reset_appraise_flags() call to
post hooks
Hi Casey,
On Tue, 2021-04-27 at 09:39 -0700, Casey Schaufler wrote:
> >> That ship sailed when "security=" was deprecated in favor of "lsm="
> >> support, which dynamically enables/disables LSMs at runtime.
>
> security= is still supported and works the same as ever. lsm= is
> more powerful than security= but also harder to use.
I understand that it still exists, but the documentation says it's been
deprecated.
>From Documentation/admin-guide/kernel-parameters.txt:
security= [SECURITY] Choose a legacy "major" security module to
enable at boot. This has been deprecated by the
"lsm=" parameter.
Mimi
Powered by blists - more mailing lists