[lkml]   [2002]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: extended file permissions based on LSM
On Sat, Aug 31, 2002 at 06:16:04AM +0200, Gabor Kerenyi wrote:
> In this case we could have some very interesting (useful
> or not who knows) features. For example if there are two
> hardlinks for an inode in two different directories, the user
> could get different rights for the file depending on the
> path he reaches it.

I think you can already do this with the existing LSM interface, you can
always get the dentry for a given inode, right? I think there might be
a problem in determining the "real" path structure of the dentry all the
time due to mount locations, but that will be fixed up by the time 2.6
is out.

> To be honest I'd welcome if the whole file permisssion
> part were moved to LSM. It would allow us to override the
> currently implemented default behavior easily.

No! One of the main goals of the LSM design was to not override the
current Linux permission behavior. It can only deny access to things,
not be a permissive system of allowing access to things that the current
system denies. See the many threads on the LSM mailing list for the
reasons behind this.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.086 / U:4.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site