From: James Morris <jmorris@namei.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, sds@tycho.nsa.gov,
selinux@tycho.nsa.gov, alan@redhat.com, chrisw@redhat.com,
hpa@zytor.com, akpm@linux-foundation.org
Subject: Re: [PATCH 3/3] security: allow capable check to permit mmap or low vm space
Date: Sat, 17 Nov 2007 08:58:01 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0711170856200.22208@us.intercode.com.au> (raw)
In-Reply-To: <1195250009.2924.103.camel@localhost.localdomain>
On Fri, 16 Nov 2007, Eric Paris wrote:
> On Sat, 2007-11-17 at 08:47 +1100, James Morris wrote:
> > On Fri, 16 Nov 2007, Eric Paris wrote:
> >
> > > On a kernel with CONFIG_SECURITY but without an LSM which implements
> > > security_file_mmap it is impossible for an application to mmap addresses
> > > lower than mmap_min_addr.
> >
> > Actually, should we be doing any checking in the dummy module, given that
> > it is not done with !CONFIG_SECURITY ?
>
> I'm not sure I understand the question. We already do a number of
> capable type security checks in dummy functions. See dummy_settime() as
> just one example.
I mean just in this case. If no mmap_min_addr check is done without
CONFIG_SECURITY, then perhaps none should be done in the dummy module,
i.e. preserving existing behavior. LSM is theoretically supposed to be
unnoticable from a behavioral pov unless a non-dummy module is loaded.
>
> If we have !CONFIG_SECURITY we don't have any security protections (how
> could we? we turned them off) so we don't get into dummy hooks. If we
> do checks or not in uncompiled code doesn't seem to me to matter.
>
> Maybe I'm just confused...
>
> -Eric
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2007-11-16 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 20:55 Eric Paris
2007-11-16 21:47 ` James Morris
2007-11-16 21:53 ` Eric Paris
2007-11-16 21:58 ` James Morris [this message]
2007-11-16 22:07 ` Eric Paris
2007-11-16 22:12 ` James Morris
2007-11-20 16:54 ` Eric Paris
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=Xine.LNX.4.64.0711170856200.22208@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=chrisw@redhat.com \
--cc=eparis@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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
Powered by JetHome