* [PATCH v2 1/1] Docs: Update LSM/apparmor.rst
@ 2024-08-01 10:23 Siddharth Menon
2024-08-01 11:01 ` Siddharth Menon
0 siblings, 1 reply; 2+ messages in thread
From: Siddharth Menon @ 2024-08-01 10:23 UTC (permalink / raw)
To: =corbet; +Cc: =linux-doc, apparmor, linux-kernel-mentees, Siddharth Menon
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
--
2.39.2
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2 1/1] Docs: Update LSM/apparmor.rst
2024-08-01 10:23 [PATCH v2 1/1] Docs: Update LSM/apparmor.rst Siddharth Menon
@ 2024-08-01 11:01 ` Siddharth Menon
0 siblings, 0 replies; 2+ messages in thread
From: Siddharth Menon @ 2024-08-01 11:01 UTC (permalink / raw)
To: corbet; +Cc: linux-doc, linux-kernel-mentees
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-08-01 11:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-01 10:23 [PATCH v2 1/1] Docs: Update LSM/apparmor.rst Siddharth Menon
2024-08-01 11:01 ` Siddharth Menon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox