Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1229750
| From | Andreas Gruenbacher <agruenba@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC v7 15/41] richacl: Automatic Inheritance |
| Date | 2015-09-21 23:30 +0200 |
| Message-ID | <qbgOS-1Me-21@gated-at.bofh.it> (permalink) |
| References | <q5iTn-686-5@gated-at.bofh.it> <q5j35-6jH-65@gated-at.bofh.it> <qa8To-2tx-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
2015-09-18 20:40 GMT+02:00 J. Bruce Fields <bfields@fieldses.org>: > On Sat, Sep 05, 2015 at 12:27:10PM +0200, Andreas Gruenbacher wrote: >> Automatic Inheritance (AI) allows changes to the acl of a directory to > In the above "file" sometimes means "any object" and somethings "a > non-directory". I can sort it out, but more consistent terminology > would help. Okay, I'll fix it. >> Linux does not have a way of creating files without setting the file >> permission bits, so all files created inside a directory with >> RICHACL_AUTO_INHERIT set will have the RICHACL_PROTECTED flag set. This >> effectively disables Automatic Inheritance. >> >> Protocols which support creating files without specifying permissions >> can explicitly clear the RICHACL_PROTECTED flag after creating a file >> and reset the file masks to "undo" applying the create mode; see >> richacl_compute_max_masks(). They should set the RICHACL_DEFAULTED >> flag. This is a workaround; a mechanism that would allow a process to >> indicate to the kernel to ignore the create mode when there are >> inherited permissions would fix this problem. > > Also, as you know: current nfsd has no way to create files without > setting permissions. And if we were to implement that it's unclear how > many clients would actually use it (Windows clients are rare). And of > course Samba doesn't have the interfaces it would need. > > I think we should just drop this for now. The rest of the richacl stuff > is still useful without it. Samba will hack around it and adjust the ACL after the create; that's still better than not having Automatic Inheritance. Windows uses AI all the time so AI is more important for Samba than for NFSv4. Thanks, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC v7 15/41] richacl: Automatic Inheritance bfields@fieldses.org (J. Bruce Fields) - 2015-09-18 20:50 +0200
Re: [RFC v7 15/41] richacl: Automatic Inheritance Andreas Gruenbacher <agruenba@redhat.com> - 2015-09-21 23:30 +0200
Re: [RFC v7 15/41] richacl: Automatic Inheritance "J. Bruce Fields" <bfields@fieldses.org> - 2015-09-22 04:00 +0200
Re: [RFC v7 15/41] richacl: Automatic Inheritance "J. Bruce Fields" <bfields@fieldses.org> - 2015-09-23 16:00 +0200
csiph-web