From: James Morris <jmorris@namei.org>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Linux Security Module list
<linux-security-module@vger.kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Casey Schaufler <casey@schaufler-ca.com>,
SElinux list <selinux@vger.kernel.org>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
John Johansen <john.johansen@canonical.com>,
Kees Cook <keescook@chromium.org>,
Micah Morton <mortonm@chromium.org>
Subject: Re: [PATCH] LSM: allow an LSM to disable all hooks at once
Date: Sat, 14 Dec 2019 05:48:46 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1912140547490.9693@namei.org> (raw)
In-Reply-To: <CAFqZXNv=AnPxHuQCusoJQGEJ8Q+yF7_TPBCRyAcE5OPzoYFc9w@mail.gmail.com>
On Thu, 12 Dec 2019, Ondrej Mosnacek wrote:
> I'd say the burden of implementing this would lie on the arms of
> whoever prepares the patches for dynamic load/unload.
Correct, and I don't see any such patches being accepted.
Go and look at some exploits, where LSM is used as a rootkit API...
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-12-13 20:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 14:08 [PATCH] LSM: allow an LSM to disable all hooks at once Ondrej Mosnacek
2019-12-11 14:13 ` Ondrej Mosnacek
2019-12-11 14:29 ` Stephen Smalley
2019-12-11 16:42 ` Kees Cook
2019-12-11 18:35 ` Casey Schaufler
2019-12-11 19:12 ` Stephen Smalley
2019-12-12 11:49 ` Ondrej Mosnacek
2019-12-12 13:14 ` Stephen Smalley
2019-12-12 16:03 ` Ondrej Mosnacek
2019-12-12 16:51 ` Casey Schaufler
2019-12-12 17:39 ` Stephen Smalley
2019-12-12 17:54 ` Paul Moore
2019-12-12 17:57 ` Stephen Smalley
2019-12-12 18:09 ` Paul Moore
2019-12-12 18:11 ` Stephen Smalley
2019-12-12 18:18 ` Paul Moore
2019-12-12 18:48 ` Stephen Smalley
2019-12-12 19:01 ` Paul Moore
2019-12-13 14:06 ` Ondrej Mosnacek
2019-12-13 23:23 ` Paul Moore
2019-12-16 18:55 ` James Morris
2019-12-13 13:54 ` Ondrej Mosnacek
2019-12-12 18:28 ` Casey Schaufler
2019-12-12 11:48 ` Ondrej Mosnacek
2019-12-12 10:30 ` Tetsuo Handa
2019-12-12 11:58 ` Ondrej Mosnacek
2019-12-13 18:48 ` James Morris [this message]
2019-12-14 0:32 ` Tetsuo Handa
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=alpine.LRH.2.21.1912140547490.9693@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mortonm@chromium.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=serge@hallyn.com \
/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