Network Working Group Marius Aamodt Eriksen Internet Draft October 2002 Document: draft-eriksen-nfsv4-acl-01.txt Mapping Between NFSv4 and Posix Draft ACLs Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. "Copyright (C) The Internet Society (2002). All Rights Reserved." Abstract The NFS (Network File System) version 4[rfc3010bis] (NFSv4) specifies a flavor of Access Control Lists (ACLs) that resembles that of Windows NT's. ACLs are used to specify fine grained control of access to file system objects. An ACL consists of a number of Access Control Entries (ACEs), each specify some level of access for an entity; an entity can be a a user, group or a special entity. The access level is described using an access mask, which is a bitmask where each bit describes a level of access, for example read, write and execute permissions on the file system object. Expires: April 2003 [Page 1] Mapping NFSv4 ACLs October 2002 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. NFSv4 ACLs . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. POSIX ACLs . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Mapping Posix ACLs to NFSv4 ACLs . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . 7 6. Bibliography . . . . . . . . . . . . . . . . . . . . . . . . 8 7. Author's Address . . . . . . . . . . . . . . . . . . . . . . 9 8. Copyright . . . . . . . . . . . . . . . . . . . . . . . . . 9 Expires: April 2003 [Page 2] Mapping NFSv4 ACLs October 2002 1. Introduction The NFS (Network File System) version 4 [rfc3010bis] (NFSv4) specifies a flavor of Access Control Lists (ACLs) that resembles that of Windows NT's. ACLs are used to specify fine grained control of access to file system objects. An ACL consists of a number of Access Control Entries (ACEs), each specify some level of access for an entity; an entity can be a a user, group or a special entity. The access level is described using an access mask, which is a bitmask where each bit describes a level of access, for example read, write and execute permissions on the file system object. 2. NFSv4 ACLs NFSv4 ACLs are rich in nature and expands upon the traditional idea of ACLs. An NFSv4 ACE can be of type ALLOW, DENY, LOG or ALARM; each specifies a different action to take should the ACE match a current request. NFSv4 ACLs also have a rich set of access types that complements the traditional types. These include appending data to the file object, deleting children of the file object and deleting the file object, etc [rfc3010bis]. NFSv4 ACLs are interpreted in a straight forward manner. 1) Walk through the list of ACEs from the ACL in order 2) If the "who" (entity) field in the ACE does not match that of the requester, the particular ACE is not processed. 3) Process all ACEs until all the bits in the requested access mask have been ALLOWed; once a particular bit has been ALLOWed by an ACE, it is no longer considered in further processing. 4) If a particular access is DENYed (while that bit is still under consideration), the request is denied. 5) If all bits have been ALLOWed, the access is granted, or else the access is denied NFSv4 ACLs also specify a number of special entities such as OWNER, GROUP and EVERYONE. These refer to the traditional UNIX mode bits. Others include DIALUP, BATCH and AUTHENTICATED, which have specialized uses. Additionally the NFSv4 ACLs specify a number of flags that can be applied to an ACL. These include a specification on how an ACL on a directory may be propagated to newly created files or directories Expires: April 2003 [Page 3] Mapping NFSv4 ACLs October 2002 inside of said directory. It is clear that the granularity of access control that NFSv4 ACLs specify is well beyond the standard UNIX capability of expressing file system object permissions. 3. POSIX ACLs POSIX ACLs refer to POSIX 1003.1e/1003.2c Draft Standard 17 [posixacl]. They were meant to specify a POSIX standard for ACLs, but unfortunately never materialized. However, many systems still use it, both in the form of it's latest draft as well as earlier drafts. POSIX ACLs are simpler than its NFSv4 equivalent. Each ACE an has an entity and the traditional UNIX mode bits that are assigned to the particular entity. The entity may be an arbitrary UID or GID or one of a few special entities, the most notable of which is the ACL_MASK entity. POSIX ACLs are also interepreted differently than their NFSv4 equivalents. POSIX ACLs are interpreted as follows: 1) Process the ACL_USER_OBJ (equivalent to UNIX file owner) ACE first; if the UID of the requester does not match that of the ACL_USER_OBJ, then the ACE is ignored. Else, if the requester's access mask is allowed by the access mask of the ACE, the request is granted, else the request is denied. 2) Process all of the ACL_USER ACEs; the entity of these ACEs specify a user on the system. If the UID of the requester does not match that of the ACE, then the ACE is ignored. Else, if the requester's access mask is allowed by the access mask of the ACE, the request is granted, else the request is denied. 3) Process the ACL_GROUP_OBJ ACE and all of the ACL_GROUP ACEs; the entity of these ACEs specify a group on the system. If none of the GIDs of the requester match the current ACE, the particular ACE is ignored. For any matching ACE, if the the requester's access mask is allowed by the ACEs access mask, then access is permitted. If there are matching ACEs, but none allow access, then access is denied. 4) If the requester's access mask is allowed by the ACL_OTHER ACE, then grant access. Expires: April 2003 [Page 4] Mapping NFSv4 ACLs October 2002 5) Deny access. Steps (2) and (3) have an additional criteria; in addition to checking whether the requested access mask is allowed by the access mask in the ACE, the requested bits also have to be in the access mask of the special ACE with the ACL_MASK entity. This allows file owners to specify a maximum level of access allowed by any other user or group that has any access to the file system object. In addition to a regular POSIX ACL, a directory in the file system may also have associated with it a default ACL. This default ACL governs the ACL a file system object will be assigned initially when it is created as a child of the particular directory. 4. Mapping Posix ACLs to NFSv4 ACLs Given the difference in both extensiveness and interpretation of POSIX and NFSv4 ACLs, any conversion between the two is prone to non-inclusive, and often times impossible. However, POSIX ACLs are a subset of NFSv4 ACLs. Any POSIX ACL can be emulated with an NFSv4 ACL. The difference in the format of POSIX ACEs and NFSv4 ACEs can be compensated for by a direct mapping. The ACE entities is translated as follows. The non-special entities in form of UIDs and GIDs is translated to equivalent strings (a system dependent process, typically done by lookups to /etc/passwd in UNIX). The POSIX ACL_USER_OBJ entity is translated to the "OWNER" NFSv4 entity. Similary, the POSIX ACL_GROUP_OBJ is translated to the "GROUP" NFSv4 entity. The ACL_OTHER entity is translated to the "EVERYONE" NFSv4 entity. The ACE access mask is translated as follows. The read bit of the POSIX access mask is translated to the "ACE4_READ_DATA" NFSv4 access mask field. The write bit of the POSIX access mask is translted to "ACE4_WRITE_DATA" NFSv4 access mask field. In the case of a directory object, the execute bit of the POSIX access mask is translated into the "ACE4_LIST_DIRECTORY" NFSv4 access mask field. In the case of any other file system object, the execute bit of the POSIX access mask is translated into the "ACE4_EXECUTE" NFSv4 access mask field. The ACE flag field also has a simple translation. If the file system object is a directory, and the POSIX ACE belongs to a default ACL, Expires: April 2003 [Page 5] Mapping NFSv4 ACLs October 2002 the "ACE4_INHERIT_ONLY_ACE" flag is set in the NFSv4 ACE. If the entity in the POSIX ACE refers to a group, the "ACE4_IDENTIFIER_GROUP" flag is set in the NFSv4 ACE. Completing the mapping reduces to being able to emulate an ACL_MASK and compensate for the difference in interpretation between to two ACL implementations. The difference in interpretation of the two ACL types call for a translation scheme. The scheme follows: Every user ACE in the POSIX ACL maps into 2 NFSv4 ACEs; one ALLOW ACE which is translated as specified by the above scheme, then a complementing DENY ACE which is also translated as specified by the above scheme, with the exception that the access mask is inversed. Note that the ACL_USER_OBJ ACE is placed first in this list. Every group ACE in the POSIX ACL produces a similar pair, but instead of being in sequence, all of the ALLOW ACEs are all in sequence, followed by all the DENY ACEs. The ACL_GROUP_OBJ ACE is placed first. Lastly, the POSIX ACL_OTHER ACE translates directly into one NFSv4 ACE at the end of the group ACEs. This is an allow ACE which is translated as specified by the above scheme. This translation strategy allows us to emulate POSIX ACL interpretation in an NFSv4 ACL. To handle the special POSIX entity ACL_MASK, we slightly modify the above translation: With the exception of the "OWNER," "GROUP," and "EVERYONE" ACEs, another ACE is prepended to the ACE. The prepended ACE is a DENY ACE with the same entity as the following ALLOW ACE, but with a permission mask set to the complement of the POSIX ACL_MASK. This method allows us to preserve the real permission bits of each ACE should the ACL_MASK be changed. Expires: April 2003 [Page 6] Mapping NFSv4 ACLs October 2002 5. Security Considerations Since this draft deals with the mapping of Access Control Lists, it is deeply involved with security. The body of this document needs to address the issue of mapping ACLs in a way as to not disobey the intent of or mislead the user. Expires: April 2003 [Page 7] Mapping NFSv4 ACLs October 2002 6. Bibliography [rfc3010bis] Shepler, S. et. al., "NFS version 4 Protocol", draft-ietf-nfsv4- rfc3010bis-03.txt, September 2002. http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-rfc3010bis- 03.txt [posixacl] IEEE, "IEEE Draft P1003.1e", October 1997 (last draft). http://wt.xpilot.org/publications/posix.1e/download.html Expires: April 2003 [Page 8] Mapping NFSv4 ACLs October 2002 7. Author's Address Address comments related to this memorandum to: marius@umich.edu Marius Aamodt Eriksen University of Michigan / CITI 535 West William Ann Arbor, Michigan E-mail: marius@umich.edu 8. Copyright Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expires: April 2003 [Page 9]