From: "Edwin Zimmerman" <edwin@211mainstreet.net>
To: "'Tetsuo Handa'" <penguin-kernel@i-love.sakura.ne.jp>,
"'James Morris'" <jmorris@namei.org>
Cc: "'Stephen Smalley'" <sds@tycho.nsa.gov>,
<linux-security-module@vger.kernel.org>
Subject: RE: [PATCH] tomoyo: Add a kernel config option for fuzzing testing.
Date: Tue, 12 Mar 2019 17:56:11 -0400 [thread overview]
Message-ID: <000001d4d91e$68837940$398a6bc0$@211mainstreet.net> (raw)
In-Reply-To: <770d8413-bd57-c379-21a0-acbbdf82241e@i-love.sakura.ne.jp>
On March 12, 2019 5:15, Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp> wrote
> On 2019/03/13 2:19, James Morris wrote:
> > On Mon, 11 Mar 2019, Tetsuo Handa wrote:
> >
> >> On 2019/03/05 12:32, James Morris wrote:
> >>> On Tue, 5 Mar 2019, Tetsuo Handa wrote:
> >>>
> >>>> I guess that majority of TOMOYO users are now using the upstream version. But
> >>>> pre-LSM version and/or AKARI will remain there until LKM-based LSMs becomes
> >>>> officially supported
> >>>
> >>> You mean dynamically loadable LSMs?
> >>
> >> Yes. As long as upstream can't accept all LSM modules, and some people cannot afford
> >> utilizing upstream LSM modules, LKM-based LSMs will be needed by such people.
> >
> > What do you mean cannot afford ?
> >
>
> Some people have to set SELINUX=disabled in /etc/selinux/config or pass security=none from
> the kernel command line.
If you specifically don't want in-kernel LSMs, and you specifically do want an out-of-tree LSM,
there are other options. For example, you could just livepatch the security_* hooks you need,
since you already would using an LKM-based LSM. That would give you your
out-of-tree module and would also disable selinux on the hooks that got livepatched.
next prev parent reply other threads:[~2019-03-12 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 14:06 [PATCH] tomoyo: Add a kernel config option for fuzzing testing Tetsuo Handa
2019-03-04 13:35 ` Tetsuo Handa
2019-03-04 14:34 ` Stephen Smalley
2019-03-04 23:59 ` Tetsuo Handa
2019-03-05 3:32 ` James Morris
2019-03-11 13:18 ` Tetsuo Handa
2019-03-12 17:19 ` James Morris
2019-03-12 21:15 ` Tetsuo Handa
2019-03-12 21:19 ` James Morris
2019-03-12 21:56 ` Edwin Zimmerman [this message]
2019-03-13 20:00 ` James Morris
2019-03-12 18:21 ` James Morris
2019-03-12 20:56 ` Tetsuo Handa
2019-03-12 21:24 ` James Morris
2019-03-13 10:29 ` Tetsuo Handa
2019-03-13 13:17 ` Paul Moore
2019-03-25 21:09 ` 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='000001d4d91e$68837940$398a6bc0$@211mainstreet.net' \
--to=edwin@211mainstreet.net \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sds@tycho.nsa.gov \
/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