From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Chris Wright <chrisw@osdl.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: Wed, 09 Feb 2005 15:10:54 +0100 [thread overview]
Message-ID: <1107958254.3754.292.camel@localhost.localdomain> (raw)
In-Reply-To: <20050208161530.F469@build.pdx.osdl.net>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
El mar, 08-02-2005 a las 16:15 -0800, Chris Wright escribió:
> * 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.
Right, the patch is no longer available as notify_change grabs the
inode_setattr hook returned data.
Did you checked the other one on sys_chroot()? (I've updated it a day or
so ago).
Cheers, thanks for commenting on it.
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-02-09 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 16:14 [PATCH] New sys_chmod() hook for the LSM framework Lorenzo Hernández García-Hierro
2005-02-09 0:15 ` Chris Wright
2005-02-09 14:10 ` Lorenzo Hernández García-Hierro [this message]
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=1107958254.3754.292.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
/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