From: Siddharth Menon <simeddon@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v2 1/1] Docs: Update LSM/apparmor.rst
Date: Thu, 1 Aug 2024 16:31:34 +0530 [thread overview]
Message-ID: <ec6e3d88-b98e-4fce-9f7a-73c8ff82f8dc@gmail.com> (raw)
In-Reply-To: <20240801102356.93591-1-simeddon@gmail.com>
> Docs: Update LSM/apparmor.rst
>
> After the deprecation of CONFIG_DEFAULT_SECURITY, it is no longer used
> to enable and configuring AppArmor.
> Since kernel 5.0, `CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE` is not
> used either. Instead, the CONFIG_LSM parameter manages the order and
> selection of LSMs.
>
> Signed-off-by: Siddharth Menon<simeddon@gmail.com>
> ---
> V1 -> V2: Removed historical information and addressed review comments
>
> Documentation/admin-guide/LSM/apparmor.rst | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/LSM/apparmor.rst b/Documentation/admin-guide/LSM/apparmor.rst
> index 6cf81bbd7ce8..47939ee89d74 100644
> --- a/Documentation/admin-guide/LSM/apparmor.rst
> +++ b/Documentation/admin-guide/LSM/apparmor.rst
> @@ -18,8 +18,11 @@ set ``CONFIG_SECURITY_APPARMOR=y``
>
> If AppArmor should be selected as the default security module then set::
>
> - CONFIG_DEFAULT_SECURITY="apparmor"
> - CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
> + CONFIG_DEFAULT_SECURITY_APPARMOR=y
> +
> +The CONFIG_LSM parameter manages the order and selection of LSMs.
> +Specify apparmor as the first "major" module (e.g. AppArmor, SELinux, Smack)
> +in the list.
>
> Build the kernel
>
I had accidentally added an extra '=' before the recipient mail
and linux-doc@vger.kernel.org while using git send-email.
Really sorry about this.
Thanks,
Siddharth
prev parent reply other threads:[~2024-08-01 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 10:23 [PATCH v2 1/1] Docs: Update LSM/apparmor.rst Siddharth Menon
2024-08-01 11:01 ` Siddharth Menon [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=ec6e3d88-b98e-4fce-9f7a-73c8ff82f8dc@gmail.com \
--to=simeddon@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
/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