-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission Access Control List on unix system #7106
Comments
https://serverfault.com/questions/227852/what-does-a-mean-at-the-end-of-the-permissions-from-ls-l I have found a relative discussion from serverfault From arch wiki and the relatived crate https://docs.rs/xattr/latest/xattr/ |
Maybe ls can also use an extra table to show these information |
But there are not much popular crates about ACLS..and exa also just know the folder is ACLS folder, and people do not always need to enter to the ACLS folder, they just need to enter into the mounted folder of device in it , and in the mounted folders, it will have the known permission. So I think maybe an other solution is to add I don't know if show the message for ACLS is needed,but now exa and origin |
Hey @Decodetalkers 🙂 I prepared a PR for a generic approach to read xattrs in ls, could you maybe have a look at it for feedback? #7158 |
In addition to ACLs ( |
Describe the bug
As you have seen , except 9 bits of permission, sometimes there are an extra permission , it is called extended permissions, and seems with the permission, every program will have the access to the folder, although they do not have any permission under the folder. and maybe it can be the enhancement of ls command
How to reproduce
Expected behavior
the xattrs should be handled, related code of exa is in https://github.com/ogham/exa/blob/master/src/fs/fields.rs#L92
Screenshots
No response
Configuration
Additional context
No response
The text was updated successfully, but these errors were encountered: