* [PATCH V2 RESEND] Docs: Update LSM/apparmor.rst
@ 2024-10-02 9:49 Siddharth Menon
2024-11-09 20:36 ` John Johansen
0 siblings, 1 reply; 3+ messages in thread
From: Siddharth Menon @ 2024-10-02 9:49 UTC (permalink / raw)
To: linux-doc, john.johansen, corbet; +Cc: shuah, Siddharth Menon, apparmor
After the deprecation of CONFIG_DEFAULT_SECURITY, it is no longer used
to enable and configure 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.5
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH V2 RESEND] Docs: Update LSM/apparmor.rst
2024-10-02 9:49 [PATCH V2 RESEND] Docs: Update LSM/apparmor.rst Siddharth Menon
@ 2024-11-09 20:36 ` John Johansen
2024-11-26 16:37 ` Sid
0 siblings, 1 reply; 3+ messages in thread
From: John Johansen @ 2024-11-09 20:36 UTC (permalink / raw)
To: Siddharth Menon, linux-doc, corbet; +Cc: shuah, apparmor
On 10/2/24 02:49, Siddharth Menon wrote:
> After the deprecation of CONFIG_DEFAULT_SECURITY, it is no longer used
> to enable and configure 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>
Acked-by: John Johansen <john.johansen@canonical.com>
I have pulled this into my tree
> ---
> 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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH V2 RESEND] Docs: Update LSM/apparmor.rst
2024-11-09 20:36 ` John Johansen
@ 2024-11-26 16:37 ` Sid
0 siblings, 0 replies; 3+ messages in thread
From: Sid @ 2024-11-26 16:37 UTC (permalink / raw)
To: John Johansen; +Cc: linux-doc, corbet, shuah, apparmor
On Sun, 10 Nov 2024 at 02:06, John Johansen <john.johansen@canonical.com> wrote:
> I have pulled this into my tree
Thanks for accepting my patch
Regards,
Siddharth Menon
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-11-26 16:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-02 9:49 [PATCH V2 RESEND] Docs: Update LSM/apparmor.rst Siddharth Menon
2024-11-09 20:36 ` John Johansen
2024-11-26 16:37 ` Sid
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).