Each permission is returned as a row of these values:
Tachyon uses the same terms as Windows Explorer such as
Tachyon follows the Windows Explorer example and distinguishes between
GetFilePermissions has been restricted to only search the local computer for the translation of SIDs into "domain\user". If the Owner/Group SID identifies a user on a domain that is not the local machine, then the SID will be stringized into the "S-1-5-21-xxx-yyy" format. The reason for this local lookup only is that the Agents involved will all be running the instruction at roughly the same time and thus this could be interpreted as a denial of service attack on the domain controllers.
For non-Windows endpoints, file mode permissions such as
ACL support was added in the Linux 2.6 kernel and is available on a filesystem basis (ext2, ext3, ext, IBM JFS, XFS, reiserfs). Linux distributions typically offer ACL as an optional install feature, for example 'yum install acl' on Centos/Red Hat. Also the file system will need to be mounted with the acl option. Linux ACL support is POSIX 1003.1e DS 17 compliant. This solution only offers read, write, execute permissions on a per user or per group basis, plus directory ACL attribute inheritance. The Linux solution is inferior to either MacOSX ACLs or Windows ACLs. Typically ACLS are set using setfacl and displayed using getfacl.
ACL support is enabled by default for MacOSX Leopard onwards and the support is much richer than the Linux ACL solution, it is quite similar to Windows ACL solution. Typically ACLs are set using chmod and displayed using ls -le. A good description of MacOSX ACL support is here.
ACL support for Windows is rich and comparable to MacOSX ACL support. A good description is here.
A good table of operating system/file system support for ACLs is here.