ACLs
From Linux NFS
| Line 12: | Line 12: | ||
* The [http://www.citi.umich.edu/projects/nfsv4/rfc/draft-ietf-nfsv4-acl-mapping-03.txt POSIX<->NFSv4 mapping draft], which explains how we map between POSIX and NFSv4 ACLs. | * The [http://www.citi.umich.edu/projects/nfsv4/rfc/draft-ietf-nfsv4-acl-mapping-03.txt POSIX<->NFSv4 mapping draft], which explains how we map between POSIX and NFSv4 ACLs. | ||
* The [http://www.citi.umich.edu/projects/nfsv4/ CITI NFSv4 project page], which has links to modified linux acl utilities with preliminary NFSv4 support | * The [http://www.citi.umich.edu/projects/nfsv4/ CITI NFSv4 project page], which has links to modified linux acl utilities with preliminary NFSv4 support | ||
| - | * | + | * [http://www.ietf.org/internet-drafts/draft-falkner-nfsv4-acls-00.txt], which suggests some |
= Design of the linux NFSv4 ACL implementation = | = Design of the linux NFSv4 ACL implementation = | ||
| Line 26: | Line 26: | ||
The data in the system.nfs4_acl attribute consists of the raw xdr data which the client receives from the server as the value of the "acl" attribute. It is up to userspace to do xdr decoding and encoding. | The data in the system.nfs4_acl attribute consists of the raw xdr data which the client receives from the server as the value of the "acl" attribute. It is up to userspace to do xdr decoding and encoding. | ||
| + | |||
| + | = The ACL Interoperability Problem = | ||
| + | |||
| + | We now have three ACL models to deal with: NFSv4, Windows, and "POSIX ACLs"/mode bits. And we have to decide what to do with them all in the face of existing users, tools, and system interfaces that assume one or the other. | ||
| + | |||
| + | More specifically: | ||
| + | |||
| + | A server has to store ACL's persistently on its filesystem. There are immense | ||
| + | advantages to storing those ACL's using whatever ACL's the filesystem and | ||
| + | operating system support, because that will ensure that they are automatically | ||
| + | enforced against other applications and protocol services using the same | ||
| + | filesystem. | ||
| + | |||
| + | Some servers are therefore translating to and from their native format. Others | ||
| + | are implementing NFSv4 ACL's in the filesystem. | ||
| + | |||
| + | The client in theory has a simpler problem--it can always provide its own application for manipulating ACLs. However: | ||
| + | |||
| + | * Some applications (Microsoft Word was mentioned as one) manipulate ACL's directly (on temporary files? Examples might be useful here.) | ||
| + | * Users may have experience with existing ACL models and tools, which may be better integrated into important tools (like Microsoft Explorer) | ||
| + | * Administrators may have built up scripts that manipulate or check ACL's. | ||
| + | |||
| + | For this reason client implementers may have to deal with non-NFSv4 ACL's as | ||
| + | well. | ||
| + | |||
| + | == ACL models == | ||
| + | |||
| + | === NFSv4 ACLs === | ||
| + | |||
| + | See above for description. | ||
| + | |||
| + | === Windows ACLs === | ||
| + | |||
| + | Windows ACL's | ||
| + | |||
| + | There are a few minor differences between Windows and NFSv4 ACLs: | ||
| + | |||
| + | * RFC3530 says that if an ACL neither allows nor denies a certain mode bit, then behavior is undefined. But users of Windows ACLs expect them to deny by default. | ||
| + | * Windows documentation suggests that if some but not all requested access bits have been allowed, then DENY aces will still apply even if they only deny bits among those already allowed. This has the somewhat bizarre result that an ACL can allow certain permissions individually but deny them in combination. The NFSv4 ACL algorithm doesn't have this property, thought it is otherwise the same. | ||
Revision as of 20:35, 10 March 2006
Contents |
Introduction to NFSv4 ACLs
Some NFSv2 and v3 implementations support ACLs based on POSIX draft ACLs which depend on a searate rpc program (instead of being part of the NFS protocol itself).
The NFSv4 protocol includes integrated support for ACLs which are similar to those used by Windows. NFSv4 ACLs are richer than POSIX draft ACLs--any POSIX ACL can be represented by an NFSv4 ACL with almost the same semantics, whereas the reverse is not true.
Useful references:
- rfc3530 (especially section 5.11)]
- POSIX draft ACLs: POSIX ACLs aren't really POSIX--they were never accepted--but some variation of them is implemented on many operating systems, including Linux.
- The Linux man pages, specifically, acl(5), setfacl(1), getfacl(1), and setxattr(2).
- The POSIX<->NFSv4 mapping draft, which explains how we map between POSIX and NFSv4 ACLs.
- The CITI NFSv4 project page, which has links to modified linux acl utilities with preliminary NFSv4 support
- [1], which suggests some
Design of the linux NFSv4 ACL implementation
Server
None of the filesystems which the linux server exports support NFSv4 ACLs. However, many of them do support POSIX ACLs. So we map NFSv4 ACLs to POSIX ACLs and store POSIX ACLs in the filesystem. The mapping is imperfect, and prevents the server from accepting the full range of NFSv4 ACLs. We could instead store NFSv4 ACLs somewhere else--say in a separate extended attribute used only by the NFSv4 server. However, this would prevent our ACLs from being enforced against local users of the same filesystem. The code to perform this mapping on the server side is in the kernel, in fs/nfsd/nfs4acl.c.
Client
The client can also map between NFSv4 and POSIX ACLs, to allow it to support existing POSIX ACL interfaces. However it does this mapping in userspace; the kernel deals only in NFSv4 ACLs, which it exposes through a special extended attribute ("system.nfs4_acl"). Applications that use the POSIX ACL interfaces need to use a version of libacl that has been modified to do POSIX<->NFSv4 ACL mapping. But since userspace also has full access to the raw NFSv4 ACL, we can also provide utilities that get and set NFSv4 ACLs directly, without the need for mapping.
The data in the system.nfs4_acl attribute consists of the raw xdr data which the client receives from the server as the value of the "acl" attribute. It is up to userspace to do xdr decoding and encoding.
The ACL Interoperability Problem
We now have three ACL models to deal with: NFSv4, Windows, and "POSIX ACLs"/mode bits. And we have to decide what to do with them all in the face of existing users, tools, and system interfaces that assume one or the other.
More specifically:
A server has to store ACL's persistently on its filesystem. There are immense advantages to storing those ACL's using whatever ACL's the filesystem and operating system support, because that will ensure that they are automatically enforced against other applications and protocol services using the same filesystem.
Some servers are therefore translating to and from their native format. Others are implementing NFSv4 ACL's in the filesystem.
The client in theory has a simpler problem--it can always provide its own application for manipulating ACLs. However:
- Some applications (Microsoft Word was mentioned as one) manipulate ACL's directly (on temporary files? Examples might be useful here.)
- Users may have experience with existing ACL models and tools, which may be better integrated into important tools (like Microsoft Explorer)
- Administrators may have built up scripts that manipulate or check ACL's.
For this reason client implementers may have to deal with non-NFSv4 ACL's as well.
ACL models
NFSv4 ACLs
See above for description.
Windows ACLs
Windows ACL's
There are a few minor differences between Windows and NFSv4 ACLs:
- RFC3530 says that if an ACL neither allows nor denies a certain mode bit, then behavior is undefined. But users of Windows ACLs expect them to deny by default.
- Windows documentation suggests that if some but not all requested access bits have been allowed, then DENY aces will still apply even if they only deny bits among those already allowed. This has the somewhat bizarre result that an ACL can allow certain permissions individually but deny them in combination. The NFSv4 ACL algorithm doesn't have this property, thought it is otherwise the same.
