mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Chris Wright <chris@wirex.com>,
	Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
	Greg KH <greg@kroah.com>, Gabor Kerenyi <wom@tateyama.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: extended file permissions based on LSM
Date: Sun, 1 Sep 2002 16:08:05 -0700	[thread overview]
Message-ID: <20020901160805.F11165@figure1.int.wirex.com> (raw)
In-Reply-To: <E17lX4d-0004a1-00@starship>; from phillips@arcor.de on Sun, Sep 01, 2002 at 05:55:39PM +0200

* Daniel Phillips (phillips@arcor.de) wrote:
> On Sunday 01 September 2002 02:26, Chris Wright wrote:
> > * Ingo Oeser (ingo.oeser@informatik.tu-chemnitz.de) wrote:
> > > 
> > > So this is a correctly pointed out design weakness: The way the
> > > user took to reach the inode cannot be taken into account.
> > 
> > Yes, this is known, and there are anticipated VFS changes to remedy
> > this.
> 
> Could you describe them, please?

For example, passing vfsmount/dentry pair to i_op->permission().
getattr() is already done, and last I heard I Al intends to do
setattr() as well.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2002-09-01 23:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31  4:16 Gabor Kerenyi
2002-08-31  5:21 ` Greg KH
2002-08-31  7:09   ` Gabor Kerenyi
2002-09-01  0:23     ` Chris Wright
2002-08-31  7:57   ` Ingo Oeser
2002-09-01  0:26     ` Chris Wright
2002-09-01 15:55       ` Daniel Phillips
2002-09-01 23:08         ` Chris Wright [this message]
2002-09-02  0:20           ` Gabor Kerenyi
2002-08-31 23:50 ` Chris Wright

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=20020901160805.F11165@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=greg@kroah.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    --cc=wom@tateyama.hu \
    /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®