From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@namei.org>, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] tomoyo: Add a kernel config option for fuzzing testing.
Date: Tue, 05 Mar 2019 08:59:19 +0900 [thread overview]
Message-ID: <201903042359.x24NxJwx065719@www262.sakura.ne.jp> (raw)
In-Reply-To: <05b05166-d24a-3c50-6556-472f50a239b9@tycho.nsa.gov>
Stephen Smalley wrote:
> On 3/4/19 8:35 AM, Tetsuo Handa wrote:
> > James, please include this patch for 5.1-rc1, for failing to include
> > this patch will prevent various trees (SELinux/Smack/AppArmor) from
> > proper testing due to this problem because syzbot is enabling both
> > TOMOYO and one of SELinux/Smack/AppArmor via lsm= boot parameter.
> >
> > By including this patch and building kernels with this config option
> > enabled, syzbot will be able to continue proper testing.
>
> Could you clarify the status of upstream TOMOYO? Is its MAINTAINERS
> entry still accurate? Is it still actively maintained?
Mainly bugfixes and Q&A phase like
https://osdn.net/projects/tomoyo/lists/archive/users-en/2017-July/000685.html .
Now that TOMOYO can coexist with one of SELinux/Smack/AppArmor, TOMOYO users
can borrow ready-made rules from them and utilize TOMOYO's ability to generate
custom-made rules for things like
https://tomoyo.osdn.jp/1.8/ssh-protection-using-environment.html .
> Its existing
> documentation (in-tree and the tomoyo.osdn.jp site) seem to suggest that
> using the pre-LSM version and/or AKARI are preferred to using the
> upstream version. Is that still true, and do you envision it changing?
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, for e.g. Fedora/RHEL users will need to use AKARI because
TOMOYO is not available ( https://bugzilla.redhat.com/show_bug.cgi?id=542986 ).
next prev parent reply other threads:[~2019-03-04 23:59 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 [this message]
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
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=201903042359.x24NxJwx065719@www262.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).