From: Paul Moore <paul@paul-moore.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
jmorris@namei.org, serge@hallyn.com, mic@digikod.net,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, keescook@chromium.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH v3 3/3] security: Remove integrity from the LSM list in Kconfig
Date: Thu, 9 Mar 2023 18:45:12 -0500 [thread overview]
Message-ID: <CAHC9VhSuXxpS_eae0gi4zGFYWEXrxFZD7joaV-qhNmmvf_tcMg@mail.gmail.com> (raw)
In-Reply-To: <20230309085433.1810314-4-roberto.sassu@huaweicloud.com>
On Thu, Mar 9, 2023 at 3:55 AM Roberto Sassu
<roberto.sassu@huaweicloud.com> wrote:
>
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> Remove 'integrity' from the list of LSMs in Kconfig, as it is no longer
> necessary. Since the recent change (set order to LSM_ORDER_LAST), the
> 'integrity' LSM is always enabled.
See my comment in 1/3 about "always enabled".
> Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
> ---
> security/Kconfig | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
--
paul-moore.com
prev parent reply other threads:[~2023-03-09 23:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 8:54 [PATCH v3 0/3] security: Always enable integrity LSM Roberto Sassu
2023-03-09 8:54 ` [PATCH v3 1/3] security: Introduce LSM_ORDER_LAST and set it for the " Roberto Sassu
2023-03-09 13:20 ` Mimi Zohar
2023-03-09 22:04 ` Paul Moore
2023-03-10 13:38 ` Mimi Zohar
2023-03-10 16:22 ` Paul Moore
2023-03-10 16:33 ` Roberto Sassu
2023-03-10 19:59 ` Mimi Zohar
2023-03-09 23:44 ` Paul Moore
2023-03-10 7:57 ` Roberto Sassu
2023-03-09 8:54 ` [PATCH v3 2/3] Revert "integrity: double check iint_cache was initialized" Roberto Sassu
2023-03-09 13:20 ` Mimi Zohar
2023-03-09 8:54 ` [PATCH v3 3/3] security: Remove integrity from the LSM list in Kconfig Roberto Sassu
2023-03-09 13:20 ` Mimi Zohar
2023-03-09 13:29 ` Roberto Sassu
2023-03-09 23:45 ` Paul Moore [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHC9VhSuXxpS_eae0gi4zGFYWEXrxFZD7joaV-qhNmmvf_tcMg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=bpf@vger.kernel.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.