From: Chris Wright <chrisw@osdl.org>
To: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-security-module@wirex.com"
<linux-security-module@wirex.com>
Subject: Re: [PATCH] New sys_chmod() hook for the LSM framework
Date: Tue, 8 Feb 2005 16:15:30 -0800 [thread overview]
Message-ID: <20050208161530.F469@build.pdx.osdl.net> (raw)
In-Reply-To: <1107879275.3754.279.camel@localhost.localdomain>; from lorenzo@gnu.org on Tue, Feb 08, 2005 at 05:14:35PM +0100
* Lorenzo Hernández García-Hierro (lorenzo@gnu.org) wrote:
> As commented yesterday, I was going to release a few more hooks for some
> *critical* syscalls, this one adds a hook to sys_chmod(), and makes us
> able to apply checks and logics before releasing the operation to
> sys_chmod().
This is exactly the kind of hook we've tried to avoid. This is really
asking for permission to alter inode attribute data. This type of
hook is incomplete because there are other ways to alter this data,
and this access is already controlled by the inode_setattr hook (as
Tony mentioned). So this is a no go.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-02-09 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 16:14 Lorenzo Hernández García-Hierro
2005-02-09 0:15 ` Chris Wright [this message]
2005-02-09 14:10 ` Lorenzo Hernández García-Hierro
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=20050208161530.F469@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=lorenzo@gnu.org \
/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
all inboxes | Powered by JetHome®