From: Randy Dunlap <rdunlap@infradead.org>
To: Salvatore Mesoraca <s.mesoraca16@gmail.com>,
linux-kernel@vger.kernel.org
Cc: kernel-hardening@lists.openwall.com, linux-mm@kvack.org,
linux-security-module@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Brad Spengler <spender@grsecurity.net>,
Casey Schaufler <casey@schaufler-ca.com>,
Christoph Hellwig <hch@infradead.org>,
James Morris <james.l.morris@oracle.com>,
Jann Horn <jannh@google.com>, Kees Cook <keescook@chromium.org>,
PaX Team <pageexec@freemail.hu>,
"Serge E. Hallyn" <serge@hallyn.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5 02/12] S.A.R.A.: create framework
Date: Sat, 6 Jul 2019 08:29:22 -0700 [thread overview]
Message-ID: <4d85d8f3-b6be-04fe-ea5e-de47c9441f11@infradead.org> (raw)
In-Reply-To: <1562410493-8661-3-git-send-email-s.mesoraca16@gmail.com>
Hi,
On 7/6/19 3:54 AM, Salvatore Mesoraca wrote:
> diff --git a/security/sara/Kconfig b/security/sara/Kconfig
> new file mode 100644
> index 0000000..0456220
> --- /dev/null
> +++ b/security/sara/Kconfig
> @@ -0,0 +1,40 @@
> +menuconfig SECURITY_SARA
> + bool "S.A.R.A."
> + depends on SECURITY
> + select SECURITYFS
> + default n
No need for "default n". Drop it, please.
> + help
> + This selects S.A.R.A. LSM which aims to collect heterogeneous
> + security measures providing a common interface to manage them.
> + This LSM will always be stacked with the selected primary LSM and
> + other stacked LSMs.
> + Further information can be found in
> + Documentation/admin-guide/LSM/SARA.rst.
> +
> + If unsure, answer N.
> +
> +config SECURITY_SARA_DEFAULT_DISABLED
> + bool "S.A.R.A. will be disabled at boot."
> + depends on SECURITY_SARA
> + default n
> + help
> + If you say Y here, S.A.R.A. will not be enabled at startup. You can
> + override this option at boot time via "sara.enabled=[1|0]" kernel
> + parameter or via user-space utilities.
> + This option is useful for distro kernels.
> +
> + If unsure, answer N.
> +
> +config SECURITY_SARA_NO_RUNTIME_ENABLE
> + bool "S.A.R.A. can be turn on only at boot time."
can be turned on
> + depends on SECURITY_SARA_DEFAULT_DISABLED
> + default y
> + help
> + By enabling this option it won't be possible to turn on S.A.R.A.
> + at runtime via user-space utilities. However it can still be
> + turned on at boot time via the "sara.enabled=1" kernel parameter.
> + This option is functionally equivalent to "sara.enabled=0" kernel
> + parameter. This option is useful for distro kernels.
> +
> + If unsure, answer Y.
> +
--
~Randy
next prev parent reply other threads:[~2019-07-06 15:30 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 10:54 [PATCH v5 00/12] S.A.R.A. a new stacked LSM Salvatore Mesoraca
2019-07-06 10:54 ` [PATCH v5 01/12] S.A.R.A.: add documentation Salvatore Mesoraca
2019-07-06 17:14 ` Randy Dunlap
2019-07-06 17:32 ` Salvatore Mesoraca
2019-07-06 17:32 ` Salvatore Mesoraca
2019-07-13 0:14 ` James Morris
2019-07-06 10:54 ` [PATCH v5 02/12] S.A.R.A.: create framework Salvatore Mesoraca
2019-07-06 15:29 ` Randy Dunlap [this message]
2019-07-06 10:54 ` [PATCH v5 03/12] S.A.R.A.: cred blob management Salvatore Mesoraca
2019-07-12 23:35 ` James Morris
2019-07-06 10:54 ` [PATCH v5 04/12] S.A.R.A.: generic DFA for string matching Salvatore Mesoraca
2019-07-06 18:32 ` Jann Horn
2019-07-06 18:32 ` Jann Horn
2019-07-07 16:01 ` Salvatore Mesoraca
2019-07-07 16:01 ` Salvatore Mesoraca
2019-07-08 17:37 ` Jann Horn
2019-07-08 17:37 ` Jann Horn
2019-10-06 16:49 ` Salvatore Mesoraca
2019-10-06 16:49 ` Salvatore Mesoraca
2019-10-07 12:40 ` Jann Horn
2019-10-07 12:40 ` Jann Horn
2019-07-06 10:54 ` [PATCH v5 05/12] LSM: creation of "check_vmflags" LSM hook Salvatore Mesoraca
2019-07-06 10:54 ` [PATCH v5 06/12] S.A.R.A.: WX protection Salvatore Mesoraca
2019-07-06 15:38 ` Randy Dunlap
2019-07-06 19:28 ` Al Viro
2019-07-07 15:49 ` Salvatore Mesoraca
2019-07-07 15:49 ` Salvatore Mesoraca
2019-07-09 4:51 ` Kees Cook
2019-07-08 12:42 ` David Laight
2019-07-08 12:42 ` David Laight
2019-07-06 10:54 ` [PATCH v5 07/12] LSM: creation of "pagefault_handler" LSM hook Salvatore Mesoraca
2019-07-06 10:54 ` [PATCH v5 08/12] S.A.R.A.: trampoline emulation Salvatore Mesoraca
2019-07-06 15:31 ` Randy Dunlap
2019-07-06 10:54 ` [PATCH v5 09/12] S.A.R.A.: WX protection procattr interface Salvatore Mesoraca
2019-07-06 10:54 ` [PATCH v5 10/12] S.A.R.A.: XATTRs support Salvatore Mesoraca
2019-07-06 10:54 ` [PATCH v5 11/12] S.A.R.A.: /proc/*/mem write limitation Salvatore Mesoraca
2019-07-06 18:20 ` Jann Horn
2019-07-06 18:20 ` Jann Horn
2019-07-07 16:15 ` Salvatore Mesoraca
2019-07-07 16:15 ` Salvatore Mesoraca
2019-07-06 10:54 ` [PATCH v5 12/12] MAINTAINERS: take maintainership for S.A.R.A Salvatore Mesoraca
2019-07-06 14:33 ` [PATCH v5 00/12] S.A.R.A. a new stacked LSM Jordan Glover
2019-07-06 14:33 ` Jordan Glover
2019-07-06 15:02 ` Salvatore Mesoraca
2019-07-06 15:02 ` Salvatore Mesoraca
2019-07-07 1:16 ` James Morris
2019-07-07 15:40 ` Salvatore Mesoraca
2019-07-07 15:40 ` Salvatore Mesoraca
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=4d85d8f3-b6be-04fe-ea5e-de47c9441f11@infradead.org \
--to=rdunlap@infradead.org \
--cc=casey@schaufler-ca.com \
--cc=hch@infradead.org \
--cc=james.l.morris@oracle.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=s.mesoraca16@gmail.com \
--cc=serge@hallyn.com \
--cc=spender@grsecurity.net \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/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.