From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
Matthew Garrett <mjg59@google.com>,
Ard Biesheuvel <ardb@kernel.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 1/1] kernel_lockdown.7: new file
Date: Fri, 16 Oct 2020 18:11:23 +0200 [thread overview]
Message-ID: <1df01114-402c-43dd-8f69-ce35594c15ff@gmail.com> (raw)
In-Reply-To: <b8f4fef7-514c-0ac0-e6b7-a3c31763b052@gmx.de>
> We should explain in this context:
>
> * string "lockdown" in CONFIG_LSM
> * CONFIG_SECURITY_LOCKDOWN_LSM
> * CONFIG_SECURITY_LOCKDOWN_LSM_EARLY
> * CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE
> * CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY
> * CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY
>
> The relationship between CONFIG_LSM and CONFIG_SECURITY_LOCKDOWN_LSM is
> not obvious in the Kconfig menu as CONFIG_LSM does not mention which
> modules are available and CONFIG_SECURITY_LOCKDOWN_LSM does not mention
> that it depends on CONFIG_LSM.
I'm kind of hoping that you might make a chance to work
on this. What are the chances?
Thanks,
Michaek
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-10-16 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 16:51 man kernel_lockdown.7 Heinrich Schuchardt
2020-10-16 6:43 ` Michael Kerrisk (man-pages)
2020-10-16 11:28 ` [PATCH 1/1] kernel_lockdown.7: new file Heinrich Schuchardt
2020-10-16 11:40 ` Heinrich Schuchardt
2020-10-16 16:11 ` Michael Kerrisk (man-pages) [this message]
2020-10-16 16:09 ` Michael Kerrisk (man-pages)
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=1df01114-402c-43dd-8f69-ce35594c15ff@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=ardb@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=mjg59@google.com \
--cc=xypron.glpk@gmx.de \
/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).