[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081020193428.8k6ottvjfc1woscw@webmail8.dotsterhost.com>
Date: Mon, 20 Oct 2008 19:34:28 +0000
From: crispin@...spincowan.com
To: Shaya Potter <spotter@...columbia.edu>
Cc: Kentaro Takeda <takedakn@...data.co.jp>,
Stephen Smalley <sds@...ho.nsa.gov>,
James Morris <jmorris@...ei.org>,
Chris Wright <chrisw@...s-sol.org>,
"Serge E. Hallyn" <serue@...ibm.com>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org,
Toshiharu Harada <haradats@...data.co.jp>,
Andrew Morton <akpm@...ux-foundation.org>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Al Viro <viro@...iv.linux.org.uk>,
Christoph Hellwig <hch@....de>,
Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [TOMOYO #11 (linux-next) 01/11] Introduce new LSM hooks where
vfsmount is available.
Quoting Shaya Potter <spotter@...columbia.edu>:
> I know I'm late to the game in this, but as I recently asked about this
> and didn't get an answer, I'll re-ask my approach.
>
> Why can't you do this
>
> in lookup()
>
> - resolve rules (not for single process, but for all processes) for
> said path and tag dentry (seem to already have a hook)
>
> in permission()
Because it doesn't work
http://kerneltrap.org/mailarchive/linux-fsdevel/2007/6/8/319446
Quick summary: The difference between the pathname model and the label
model is dynamism. The accessi really is determined by the pathname to
the file that you used to access the file. If you try to compute
access based on attributes tagged onto the file, then you have to
re-compute those attributes every time someone renames a file.
Crispin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists