I have found three possibilities for what is calls an "ACL owner" in the wild:
- The owner is the protected resource. That's the way EAz goes.
- The ACL owner is the user whow owns and edits the ACL. (like in java.security.acl.Acl or POSIX ACL)
- The user owns the protected resource and the protected resource owns the ACL. So the user owns the ACL indirectly and is allowed to edit it.
Are there significant shortcomings of the one or other?
Addendum: In most implementations the owner of an ACL is the user who has the right to change the permissions of this ACL and owns the corresponding object.