Hi,

On Sat, Feb 17, 2001 at 04:42:32PM +0100, Andreas Gruenbacher wrote:
> Hello everybody,
> 
> this is my third push towards evolving the extended attributes system call
> interface to something that is acceptable for inclusion into the standard
> kernel :-) I've tried to write things up as a manual page. The source and
> a pdf version can be found at <http://acl.bestbits.at/pre/>.
> 
> A mostly finished implementation for ext2 of the EA interface documented
> here, and of ACLs on top of it, is almost finished. I'm planning to solve
> the remaining quircks this weekend, so perhaps I can post a link tomorrow.

This still seems to offer no way of solving the big problem I've been
trying to stress for months now: you have namespace problems *inside*
an ACL namespace.  

As a user using your POSIX acls, how can I set an ACL for some remote
user coming in over NFS from a different Kerberos realm?  It might
even be a user using NFSv2: we don't have to consider only NFSv4 ACLs
here.  And we already have code to map remote kerberos tokens to
local, temporary "process authentication groups": that's how AFS
works.  

In other words, local ACL granting might be done in terms of these
temporary unix gids, but (a) the permanent on-disk encoding of the
username and (b) the username passed in over the ACL API both need to
be expressed in terms of user@realm names.  

Not only NFS is affected by this: you might well allow remote kerberos
users to login to the local node using an anonymous account, with the
login process creating an appropriate authentication group for the
remote user.  You still want that user to be able to access files on
the local filesystem with the appropriate ACL enforcement.

Cheers,
 Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]

Reply via email to