POSIX ownership and permissions
For items stored through NFS, HCP maintains these POSIX metadata values:
- A user ID (UID), which represents the owner, and a group ID (GID), which represents the owning group. UIDs and GIDs are integers greater than or equal to zero.
UIDs are not related to HCP-specific object ownership.
- A POSIX permissions value, which is made up of three sets of POSIX permissions — one for the user identified by the POSIX user ID, one for the group identified by the POSIX group ID, and one for all others. A set of permissions is any combination of read, write, or execute, including none.
POSIX permission values determine the actions users can perform on an item when accessing it on a CIFS or NFS client:
- For an object:
- Read permission lets users view and retrieve the object content.
- Write permission has no effect.NoteEven if an object has write permission, its data is secure because WORM semantics prevent it from being modified.
- Execute permission, which applies only to objects created for executable files, lets users execute the object.
- For a directory:
- Read permission lets users see which objects are in the directory.
- Write permission lets users add and delete objects in the directory or rename empty subdirectories.
- Execute permission lets users traverse the directory to get to known objects in it, but it does not let users read the directory.
- For an object: