From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
James Morris <james.l.morris@oracle.com>,
Eric Paris <eparis@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
John Johansen <john.johansen@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] security: unconditionally call Yama
Date: Fri, 31 Aug 2012 22:39:08 +0100 [thread overview]
Message-ID: <20120831223908.4aa5574d@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20120831213126.GA19688@www.outflux.net>
On Fri, 31 Aug 2012 14:31:26 -0700
Kees Cook <keescook@chromium.org> wrote:
> Unconditionally call Yama, no matter what LSM module is selected.
>
> Ubuntu and Chrome OS already carry patches to do this, and Fedora has
> voiced interest in doing this as well. Instead of having everyone carry
> these patches, just switch Yama to being unconditional when compiled
> into the kernel.
Not a good plan. What happens when everyone decides to stack every module
by ifdeffing in the kernel - mayhem. I'm all for it being possible but
done right - espeicall as I believe a proper proposal now for stacking
modules, and it should be done as part of that.
Alan
next prev parent reply other threads:[~2012-08-31 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 21:31 Kees Cook
2012-08-31 21:39 ` Alan Cox [this message]
2012-08-31 22:49 ` Eric Paris
2012-08-31 23:59 ` Eric W. Biederman
2012-09-01 3:03 ` Eric Paris
2012-09-01 3:31 ` Eric W. Biederman
2012-09-01 3:42 ` Kees Cook
2012-09-01 4:05 ` Eric W. Biederman
2012-09-02 7:37 ` Jiri Kosina
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=20120831223908.4aa5574d@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dan.carpenter@oracle.com \
--cc=eparis@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=jkosina@suse.cz \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome