Allowing inheritable NFSv4 ACLs to override the umask
draft-bfields-nfsv4-umask-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | J. Bruce Fields , Andreas Gruenbacher | ||
| Last updated | 2016-08-25 (Latest revision 2016-02-22) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In some environments, inheritable NFSv4 ACLs can be rendered ineffective by the application of the per-process umask. This is easily worked around by transmitting the umask and create mode separately to allow servers to make more intelligent decisions about the new mode on a file.
Authors
J. Bruce Fields
Andreas Gruenbacher
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)