From: Kees Cook <keescook@chromium.org>
To: Jiele zhao <unclexiaole@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, zhaojiele@qianxin.com
Subject: Re: [PATCH] security/loadpin: Update the changing interface in the source code.
Date: Mon, 15 Mar 2021 13:44:43 -0700 [thread overview]
Message-ID: <202103151344.0F55C431@keescook> (raw)
In-Reply-To: <20210308020358.102836-1-unclexiaole@gmail.com>
On Mon, Mar 08, 2021 at 02:03:58AM +0000, Jiele zhao wrote:
> Loadpin cmdline interface "enabled" has been renamed to "enforce"
> for a long time, but the User Description Document was not updated.
> (Meaning unchanged)
>
> And kernel_read_file* were moved from linux/fs.h to its own
> linux/kernel_read_file.h include file. So update that change here.
>
> Signed-off-by: Jiele zhao <unclexiaole@gmail.com>
Thanks for the catch!
Acked-by: Kees Cook <keescook@chromium.org>
-Kees
> ---
> Documentation/admin-guide/LSM/LoadPin.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/admin-guide/LSM/LoadPin.rst b/Documentation/admin-guide/LSM/LoadPin.rst
> index 716ad9b23c9a..dd3ca68b5df1 100644
> --- a/Documentation/admin-guide/LSM/LoadPin.rst
> +++ b/Documentation/admin-guide/LSM/LoadPin.rst
> @@ -11,8 +11,8 @@ restrictions without needing to sign the files individually.
>
> The LSM is selectable at build-time with ``CONFIG_SECURITY_LOADPIN``, and
> can be controlled at boot-time with the kernel command line option
> -"``loadpin.enabled``". By default, it is enabled, but can be disabled at
> -boot ("``loadpin.enabled=0``").
> +"``loadpin.enforce``". By default, it is enabled, but can be disabled at
> +boot ("``loadpin.enforce=0``").
>
> LoadPin starts pinning when it sees the first file loaded. If the
> block device backing the filesystem is not read-only, a sysctl is
> @@ -28,4 +28,4 @@ different mechanisms such as ``CONFIG_MODULE_SIG`` and
> ``CONFIG_KEXEC_VERIFY_SIG`` to verify kernel module and kernel image while
> still use LoadPin to protect the integrity of other files kernel loads. The
> full list of valid file types can be found in ``kernel_read_file_str``
> -defined in ``include/linux/fs.h``.
> +defined in ``include/linux/kernel_read_file.h``.
> --
> 2.25.1
>
--
Kees Cook
prev parent reply other threads:[~2021-03-15 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 2:03 [PATCH] security/loadpin: Update the changing interface in the source code Jiele zhao
2021-03-15 6:22 ` Jiele Zhao
2021-03-15 19:32 ` Jonathan Corbet
2021-03-15 20:44 ` Kees Cook [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=202103151344.0F55C431@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=unclexiaole@gmail.com \
--cc=zhaojiele@qianxin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).